Archaeologist from Italy.
@fnetX that's great! My suggestion is to create one issue for each blog post, possibly at https://codeberg.org/Codeberg/blog/issues so we can keep track and submit pull requests with the content before it's published. Each issue could link to an Etherpad, be assigned to someone etc. @hw does that look OK?
4 months ago
I see this proposal has some support, fantastic! Perhaps for the time being the best thing is to keep track of the proposed blog posts here. There seem to be two ways to "measure" popularity of repositories: stars ("favorites") and forks. For both criteria the most popular repository is [Gadgetbridge](https://codeberg.org/Freeyourgadget/Gadgetbridge). So it would seem appropriate to start with the most popular repository for the first blog post.
4 months ago
Replying to @makkusu above > Nevertheless, I cannot really think of any project like GSoC right from my head. Maybe that's what we would call an absolute dependency on Big Tech... I don't see how GSOC can be defined an "absolute dependency". FOSS organizations can decide to participate in GSOC or not. Right now it's mostly seen as a win-win situation: Google can show how much they care about thriving FOSS projects and in return there's a number of people that are paid to work on implementing new features and/or getting more familiar with FOSS development in general. I think it would be more accurate to add a third element to the equation, that is, a strong incentive for the communities of those projects to not criticize Google, to avoid discussing surveillance capitalism, to act as if Google is acting for the public good and not for their own profit.
5 months ago