Well, gitlab supports merge requests created by email, but it has its own constraints. docs.gitlab.com/ee/user/projec…
Also it's not implemented in gitea:
- issue: github.com/go-gitea/gitea/issu…
nor in forgejo:
- email docs: forgejo.org/docs/latest/user/e…
- related issue: codeberg.org/forgejo/forgejo/i…
Efforts at federation at @forgefed are great, but actually, #sourcehut is already federated in some way, via its email-based interaction:
- lists.sr.ht/~sircmpwn/sr.ht-di…
They do accept PR via email. It's their way to go, actually
- git-send-email.io/

Anyway, you can send us attached git-patches via email if you want 😀

[FEAT] Allow nologin "pull requests"

### Needs and benefits I want to have certain repositories be editable by anonymous actors, preferably through the git interface, would that be possible to configure? ### Feature Description Essentially instead of forcing users to fork repository,…

^Codeberg.org

Actually, @liaizon , we are talking about our next steps on Friday. We won't change the web upside down, but maybe we take away some part, or decide on modifying some parst, depending on the route we want to take.

So you may want to wait until Saturday?

Well ! We decided to yes, easy up translations, but prioritize local physical work, on site. We didn't decide any big change in the web content, so it should be good to translate already.

For the translation, we'd like to try using some existing @weblate instance, but don't know how to integrate the sources (they are not po files) nor how to make weblate commit to a repo branch or notify us.

We could use some help on that 😀

It doesn't need to be a PO, many other formats are supported: docs.weblate.org/en/latest/for…

For pushing and pulling, use webhooks docs.weblate.org/en/latest/adm… and docs.weblate.org/en/latest/adm…

Basically, search the docs and ask via the links in our profile for anything you can't figure out with the docs. We will advise and improve them as well if needed 😊 Same applies to features.

Continuous localization

There is infrastructure in place so that your translation closely follows development. This way translators can work on translations the entire time, instead of working through huge amount of new t...

^Weblate

So, we’ve read the terms for asking for free hosting at hosted.weblate.org. Thing is, we licensed everything under feminist peer produciton license. Based on “peer production license”, which none of those are software licenses nor OSI/FSF approved licenses. In reality, it’s a Creatvie Commons license equivalent to cc-by-nc-sa with exceptions to feminist-led groups, that can use the content as cc-by-sa. Is this a problem? Should we note it somehow?

labekka.red/licencia-f2f/#f2f-…

Hosted Weblate

Hosted Weblate, the place to localize your software project.

^{Hosted Weblate}

We rely on spdx.org/licenses/ at #HostedWeblate mainly for two reasons:
- Keep it easy for all contributors; translators shouldn’t be learning plenty of new licenses with new projects they contribute to.
- We don’t have a team of lawyers dedicated to reading special licenses.

NC licenses are not considered free software as they are prohibitive.

With that, we can’t provide you free hosting plan that we offer for #LibreSoftware and #OpenSource projects, sorry.

@liaizon @Codeberg

We generally do not encourage license proliferation either, and also rely on a list of licenses approved by the FSF and OSI. Therefore, our official stance is also that the CC BY-NC-SA is not free.

Based on the description of the license, I have to ask (rhetorically) whether anyone would even attempt to sell feminist content in the first place, so as to justify the more restrictive content licensing and the resulting confusion. ~n