Continuation of forgejo/forgejo#6184
What's the relevant answer for issues?
tl;dr: The answer is the same. We might want to replace "pull requests" with "contributions" in the FAQ entry.
If I open an issue at Forgejo that might also apply to Gitea, should I duplicate the issue there? (Not only for Gitea's sake, but might that also help Forgejo... it still seems that if we want something fixed, potentially getting attention from the Gitea community and then pulling in a fix from there to Forgejo is a feasible path to get more attention from potential coders)
Even if an issue is fixed at Gitea, there is zero guarantee it will make its way to Forgejo. This has several reasons:
- The codebases diverge and not all changes can be ported easily
- There are different values in both communities. Forgejo pays special attention to test coverage, and many changes from Gitea are not picked due to lack of testing.
- Forgejo has a different approach to feature requests: We classify them by gain, apply design work where applicable, focusing on a consistent and tested user experience. We perform user research to understand the actual needs of our users. Gitea does little such things, and we are also not porting contributions that would introduce usability regressions, because certain things were not considered over at Gitea.
- The needs of the community are different. I believe that the Gitea and Forgejo communities are mostly disjoint subsets. It's a question of whether you believe in a for-profit doing the right thing and quickly evolving the software due to money vs the community having the strength and momentum, doing the right thing without access to venture capital. It's a matter of ethics, vendor lock-in and what to charge for. Open core vs actually free/libre software. And as such, the needs of the community diverge as well. It's legitimate that Gitea users, who might use the software in startups have different needs than community members that use Forgejo for free/libre software development. While Forgejo works well within startups and we know it is used there, Forgejo is unlikely to prioritize features that only benefit development in closed teams over features that benefit free/libre software development, for instance.
Also relevant: #99
Continuation of https://codeberg.org/forgejo/forgejo/issues/6184
@wolftune
> What's the relevant answer for issues?
tl;dr: The answer is the same. We might want to replace "pull requests" with "contributions" in the FAQ entry.
> If I open an issue at Forgejo that might also apply to Gitea, should I duplicate the issue there? (Not only for Gitea's sake, but might that also help Forgejo... it still seems that if we want something fixed, potentially getting attention from the Gitea community and then pulling in a fix from there to Forgejo is a feasible path to get more attention from potential coders)
Even if an issue is fixed at Gitea, there is zero guarantee it will make its way to Forgejo. This has several reasons:
- The codebases diverge and not all changes can be ported easily
- There are different values in both communities. Forgejo pays special attention to test coverage, and many changes from Gitea are not picked due to lack of testing.
- Forgejo has a different approach to feature requests: We classify them by gain, apply design work where applicable, focusing on a consistent and tested user experience. We perform user research to understand the actual needs of our users. Gitea does little such things, and we are also not porting contributions that would introduce usability regressions, because certain things were not considered over at Gitea.
- The needs of the community are different. I believe that the Gitea and Forgejo communities are mostly disjoint subsets. It's a question of whether you believe in a for-profit doing the right thing and quickly evolving the software due to money vs the community having the strength and momentum, doing the right thing without access to venture capital. It's a matter of ethics, vendor lock-in and what to charge for. Open core vs actually free/libre software. And as such, the needs of the community diverge as well. It's legitimate that Gitea users, who might use the software in startups have different needs than community members that use Forgejo for free/libre software development. While Forgejo works well within startups and we know it is used there, Forgejo is unlikely to prioritize features that only benefit development in closed teams over features that benefit free/libre software development, for instance.
Also relevant: https://codeberg.org/forgejo/discussions/issues/99