It would be great if Codeberg asked up to 300 k€ from https://sovereigntechfund.de/en/challenges/ . "Improve FOSS Developer Tooling" seems to be our core business!
Grants from the Sovereign Tech Fund - Deadline: 6 July 2023 #1035
I escalated this issue to a private repository of the Codeberg e.V. (the association behind Codeberg) for some further discussion and as it is effective and appropriate so as to alert fellow members and elected representatives while being 100% certain that the message has reached them.
For members, the thread can be found here: Codeberg-e.V./Discussion#97
As I believe that Forgejo and Codeberg are focusing on separate things, even if they are still close to one another, I decided to share create an issue under https://codeberg.org/forgejo/sustainability as well: forgejo/sustainability#13
If any of the issues seem redundant, feel free to close them without further discussion on my end.
FWIW Codeberg is a beneficiary of the grant awarded last month by NLnet (50K€).
I think this call for application is very relevant to Codeberg now because it is the umbrella organization for Forgejo. Before Forgejo it was just using a technology and not making it. Now that Forgejo is distributed and created within Codeberg, it is in scope for the first two challenges required to apply:
- Improve FOSS Developer Tooling
- Securing FOSS Software Production
It took me a while to figure out where the link to the application platform is (suprisingly hidden):
FWIW Codeberg is a beneficiary of the grant awarded last month by NLnet (50K€).
Keep in mind:
Prohibition of duplicate funding: Funding by the Sovereign Tech Fund is prohibited if other public entities are already paying or have paid for grants or investments for the identical activities.
It stands to reason that a grant application for the exact same workplan would not be legitimate. I'm sure some organizations do that anyway and expect they won't be discovered. But since the Forgejo workplan and application for NLnet is publicly readable by anyone, there is no risk of that happening 😄
Probably too late for this round, but... see e.g. Codeberg-CI/feedback#116
- There is a clear codeberg task
- There is a clear forgejo task
- There is a clear task that could be taken up by either, or a third party.
In other words, "the same thing" from a user perspective can include multiple entities with non-overlapping work plans.
@jfinkhaeuser Someone has to actually find this (✅), talk about it with the people that run the non-profit and discuss a way forward regarding a proposal.
It's indeed way too late, unfortunately.
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?