We just closed six issues at once for a feature. Guess what's live now!?

@gitea :red_heart: :gitea: :red_heart:

@werwolf @arh
Do you have suggestions to the https://docs.codeberg.org/getting-started/licensing/#copyleft paragraph and the suggestions below? Feel free to submit a contribution.

Also see https://codeberg.org/Codeberg/Documentation/issues/174

Our license reminders have been revised and are working great so far.
It's nice to see that most of you add FLOSS licenses as a very first step, and our reminders have led to some more content now being free.

Sorry for being annoying with these reminders, but it's very important, even for tiny projects, so others can safely improve or build upon. Thank you for caring 💙

Content without a license is not free content!
We'll now pop-up license reminders in case you forgot to add one and to warn users about legal uncertainty.

Also see https://docs.codeberg.org/getting-started/licensing/

The reminders might look like this:

Friendly Reminder: We don't expect the @gitea maintainers to magically solve all issues tagged as "gitea related" or "upstream" for us. Please help in addressing them, too. We're happy about every contribution.

https://codeberg.org/Codeberg/Community/issues?labels=338

@jgoerzen
If you want to read about an interesting perspective of ours, have a look at our recent blog article. https://blog.codeberg.org/community-maintenance-matters.html

We agree that having another centralized options does no better, but having several federated instances sounds like the way to go. Work in Progress, as already mentioned 😉
@eludom

@jgoerzen
BTW, Gitea is working on federation between instances. It already supports seamless migration including all metadata, so hopping between instances is fine.

We always encourage maintainers to prominently state they are accepting patches via email, too.
@F1RUM

Friendly reminder: While #Codeberg is for everyone, not everyone is on Codeberg.

Tying collaboration to your projects to a platform raises the barrier for fly-by contributors. Whether you are on Codeberg, #GitHub, some #GitLab or #Gitea instances, we always recommend to prominently state multiple contact information, so people can also send bug reports and patches, e.g. via E-Mail.

Did you already try #WoodpeckerCI on #Codeberg, or your own #Gitea instance? What do you think?

@james
The hosted service at gitlab dot com does not run the Community Edition, but rather a custom subset of the proprietary enterprise edition. Also, it uses e.g. #Cloudflare, another proprietary platform.

For more backgrounds on the company itself, I only have https://git.sdf.org/humanacollaborator/humanacollabora/src/branch/master/gitlab-dot-com.md at hand ad-hoc. Not sure if it helps.
@derek

@adnan360
We can't fully answer this, but we've once taken down leaked, proprietary Cloudflare code from our platform, and their blog article only says which free components they use, not that all they develop and deploy is free.

About GitLab, the flagship instance is of course equipped with the EE version and some features are limited if you don't pay for it. The code it runs is still nonfree obviously, and IIRC some features do differ a little, but I don't have proof at hand currently.
@james @derek

@owzim We have #WoodpeckerCI in testing, you can apply for early access at https://codeberg.org/Codeberg-CI/request-access/issues.

Integrating self-hosted CI services is easily possible.

@tychosoft @loziniak @civodul @be let's rebuild our trust in the free minded communities that created (and often still maintain!) the foundations and backbone of the modern internet as we know it. Corporations were late to the game

@be
... probably still better than certain other "modern" languages, which use a centralized package manager instead and only allow fur some services (this system is at least universal Git).

But that's probably the reason why so many Go apps vendor all their dependencies.
@tychosoft @civodul