We already have a very low barrier, as everyone can contribute by just
creating a pull request or if you have an issue write an email. I agree
that creating a jira issue is a little bit more painful as you need an
account - but I would argue that 97% of people interested in OSGi have
that account by now.
Allowing to create github issues does not lower this - and again, we
have a very low number of contributions, even if these would be 5x of
what we get now, it is still low.
I do not think that it is as easy as just making jira read-only. What
about the already existing open issues? What about all documentation and
links that point people to jira?
More importantly, how do we manage versions?
It might not be that much work, but certainly it does not come for free.
Just to be clear, I am a fan of github issues but in this case I fail to
see the benefit and I am worried that we make one thing easier while
complicating another. And then we just wasted effort.
Regards
Carsten
On 8/20/2025 6:49 PM, Christoph Läubrich wrote:
I found that the lower the barrier, the higher likely someone likes to
contribute.
Also the "effort" would be just to enable Github Issues (and
discussions!) and make the JIRA project readonly.
We did this a while back with Bugzilla at Eclipse and it worked out
quite well, if needed one can simply link to the old discussion so no
need to really migrate all the old stuff.
Am 20.08.25 um 17:17 schrieb Carsten Ziegeler:
I do not really care - but I am wondering if the effort involved to
migrate is really worth it? Especially given the low value of
contributions we are facing.
Just creating (or asking for) a Jira issue when PRs are done without
it, seems to be way less work.
And I doubt that we get more contributions (being it issues or PRs) if
we move from Jira to github issues.
Regards
Carsten
--
Carsten Ziegeler
Adobe
cziege...@apache.org
