You are all invited to our Discord hangout.
Please leave a comment here or on Discord to add things to the agenda.
This topic will be updated after the call with notes.
About
FreeSewing’s Discord hangout is an informal hangout/chat/meeting that is open to everyone.
The call is organized/hosted by @tangerineshark.
The call does not have a fixed structure or agenda items. Everyone is free to suggest agenda items, ask questions, or bring ideas.
Details
Location: https://discord.freesewing.eu/ (meeting room: voice chat)
Date: May 10th, 2025 4pm UTC, which can be found in your local time zone here.
Or check the Events tab in Discord!
The meetings will always be at 6pm, Antwerp time.
There were a number of PRs waiting to merge, before the release of v4 and the switch to Codeberg. What’s happening with them? What’s our plan to accept merge PRs?
I could try to make it, but I also have a million things on my plate. And often the call doesn’t veer into anything where I feel like me presence makes much of a difference, so then I feel it’s not a great use of my time (The “let’s hang out and chat” aspect of it is also valuable, but it’s just not for me).
As for the PR question by @Benjamin_F they were migrated to issues on codeberg. So we need to go through them and decide whether we want to revive them and port them to a merge request on Codeberg, or whether they are no longer relevant now in v4.
Okay, thanks. I had been wondering what I need to do about my still-open GitHub-PRs-migrated-to-Codeberg-Issues, whether it is I who needs to do the work and what work was needed. (For example, do I need to re-file a PR in Codeberg? It was previously said these PRs would be handled via “cross-repository merges”, so perhaps I don’t have to do anything?) And, I was wondering also about the rest of the orphaned GitHub PRs, what we were going to do with them, what the plan and timeline was, etc.
Edit: added: I’m just concerned that we have a plan to address these PRs. We seem to lose momentum and PRs seem to get stuck and lost between our v2-to-v3 and v3-to-v4 migrations. It’s difficult trying to work on FreeSewing when you see your efforts and PRs get stalled.
The cross-repository merges remark is indeed about how to handle those PRs. As in: how do we make sure we get access to the original PR code, since it’s now and issue and that code is not part if it.
But that’s more of an implementation detail of how to get it done, and does not say much about when to get it done.
There’s a bunch of stuff still to do, I am working on the documentation for @freesewing/react as it is also a good way to go through all the of the components and address any issues in them (including styling issues).
I keep an eye on any new PRs that are submitted as well as any issues that are impacting a lot of users. In absence of that, I use the time available to update the documentation.
But sooner or later, we’re going to start chasing down all the open issues.
We don’t have a good answer yet. To upload image, need to use API, not directly to Cloudflare, though theoretically it could be done. Our previous implementation no longer works, and we need to re-implement it. Also needed to upload blog images.
A Forum-to-website pipeline for Showcase posts also needs to be developed.
Joost will work on it. What workflow do we want? Write markdown and request upload?
Can a template be created for the forum? So people can give permission to have their photos showcased? GDPR? Have an opt-out public showcase forum category?
We would just link to the already-posted images on the forum, not upload them again to Cloudflare, so permission wouldn’t be needed.
Start with having an automated reply sent to forum posters, letting them know their photos may be used for a showcase, letting them opt out if desired.
Forum and website names are the same, so we can just use that. We don’t need to ask them for the name to use. And, people can change/edit their names themselves.
Joost will work on it.
Migration of previous GitHub PRs?
We will be going through these PRs to see if these are relevant.
People can advocate for specific PRs if you want them addressed sooner.
FreeSewing project updates:
Joost is working on documentation for the new v4 @freesewing/react components.
We ran out of backend disk space which caused a temporary overnight issue.
2 freesewing.social Mastodon account requests were received from Iran, with no “please tell us about yourself” information and likely from the same person. Denied.
Repository Studio login isn’t working? Login page crashes?
It should be working. Logins should work.
Try logging into the .org development environment to see if that works.
Rendertest design is no longer there? It was useful.
It’s not gone, but it isn’t part of the “Collection” so it doesn’t show up and can’t be selected.
Can a workaround be developed, to allow people to view it?
Joost previously had a workaround. He will try to retrieve and make it available.
Pattern Inspector no longer gives an overview of all the paths, making it difficult to determine path names, for hidden/covered paths.
Joost will note it as something to work on.
What’s going on with folk:
Internet issues. The internet intermittently drops.
Started doing localization work and now understand FreeSewing’s pain previously supporting translations.
Hemming wash/dish cloths.
Finished bridesmaid dresses, possibly going to make a curtain.
The green Hobbitcore dress. The bodice was one of bobgeorgethe3rd’s secret patterns.
Making embroidery patches. Is there a Skully SVG file?
voice chat)