Maybe you should have a look in Kotlin Multiplaform or Compose Multiplatform. However they rely on low-level layers, so you won’t be able to use SwiftUI maybe. Such cross-platform frameworks won’t be able to use directly system UI frameworks at least for iOS due to compilation limitations.

Title yes, but not tag.

You can delete a release. But you can’t change the associated tag and the attached artefacts.

Do you have some comparison documentation or benchmark to share comparing for example GitHub, GitLab, SourceHut and Codeberg?

I did not succeed in finding something comparing these forges about: -CI/CD

• runners
• issues
• project management
• wiki
• releases management
• third-party tools

I am used to GirHub and GitLab but not Codebeg 🤔

That’s vibe coding.

For example:

• blog

For example:

• codeberg (even if is target of some DDoS by alt-right)
• GitLab (but also American so under conditions of export compliance laws)
• forgejo
• gitea

Yup, I meant Mozilla Public License

Yes indeed the Apple App Store is not compatible with GNU GPL v3 licence. Maybe MOL MPLcan suits your needs.

However plenty of open source apps under GPL v3 or AGPL v3 are available on the App Store and Apple does not care.

For example:

• https://github.com/Dimillian/IceCubesApp (Mastodon client)
• https://github.com/mlemgroup/mlem (Lemmy client)
• https://github.com/CovidTrackerFr/vitemadose-ios (COVID vaccines app)

We should support our fediverse admins and instances 💪 Support by sending money (for people who can), moderating content, submitting issues or helping the team and project ✌️

Did you have a look on ethical licenses? For example, Coraline Ada Hemke who created the Contributor Covenant (famous code of conduct) started few years ago the Organisation for Ethical Source promoting “ethical” licenses defined by seven principles.

So in fact this third family of licenses is not open source nor free (as defined by OSI and FSF), nevertheless I feel some needs or willings in your side to go, let’s say, “one step further”.

In ethical licenses you can find for example 999 ICU, ACAB, Anti-Capitalist, Peer Production, Hippocratic or some BSD 3-Clause variants about nuclear topics.

You can also have a look on that slidedeck (in French, sorry).

An app? Nope. For notifications, there is open source alternatives to Google and Apple services but it is used in the apps side, not users side. Have a look on microG and Open GApps to flash in your Android device; it might help you.

It seems the “radical” organisations like the FSF or the OES were right and more legitimate in the end.

Enshitification made third-party apps disappeared. Prefer true open source project instead like Pixelfed for example.

Be sure also the issues you have in your project have the suitable labels to help future contributors to pick easily some of them, i.e. labels like “help wanted” or “good first issue”.

You can also refer to best practices listed and explained for example in Advent of Open Source so as to have a nice and user-friendly repo: https://adventofopensource.com/

BTW I hope any project won’t increase the Z version only by including Dependabot commits, it would be insane. Release must be documented, tested, with CHANGELOG updated. If some maintainers just accept Dependabot commits without checking, move away. That’s just simple crappy auto-merge.

Nice idea 👍

Whatever the solution behind is, if you have the resources, move to something self-hosted. Open core or not, if that topic matters to you, you might need something you can own and control. BTW, have a look on Forgejo, Codeberg and Gitea: these are the solutions I see when people look for something FLOSS, not open core, and maybe self-hostable.

It depends of the project in fact. You should reach the community and maintainers by joining them in their Discord / Slack / Matrix / whatever. They may be able to help you.

You can create first an issue, asking for improvements and create a discussion airy the maintainers so as to know which languages are not managed yet and if they are interested in new support. Explains also why you can bring good translations (e.g. native speaker, teacher, etc). It sill help to bring confidence.

Then create a pull / merge request with the updated files. For example, strings.xml ob Android, .strings in iOS, etc. But beware, localisation is not only a matter of translations. You may have also to support new languages and formats for figures, currencies, or dates for example.

Do not use translations services. Project maintainers are able to use them, and in plenty of cases the translations are not good at all or loose details.

I would have said in fact Matrix or XMPP-based solutions but it seems you already have spotted them. Maybe Mattermost?