On Thu, 5 May 2022, Jan Høydahl wrote:
ASF has officially blessed use of github issues as alternative to Jira.
They are not going to setup a private GitLab or tool X. While GitLab is
nice, I don't think the main intention with the proposal was to inroduce
yet another platform where contributors need to register an account and
learn the UI :)
That's precisely the crux of the disagreement: I want to be able to register
an account at Apache and *not* GitHub and still be able to contribute. So
yes, registering accounts in various places makes one's participation in
them more resilient to auto-banning-without-due-process-nor-recourse.
As for learning the new UI, GitLab and GitHub are very alike.
Is the original Jira -> GitHub move just a change of defaults or are we,
once moved to GitHub, not letting people use Jira at all anymore ?
Andi..
GitHub issues versions are tracked in "Milestones" -
https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones
<https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones>
See example from solr-operator. These issues or PRs were released in v0.5.1:
https://github.com/apache/solr-operator/milestone/8?closed=1
<https://github.com/apache/solr-operator/milestone/8?closed=1>
Labels are also very flexibl.
Jan
5. mai 2022 kl. 22:18 skrev David Smiley <[email protected]>:
Is anyone familiar with using GitHub (or maybe GitLab I suppose) for tracking metadata
about the issue -- something JIRA excels at? For example the version of our project that
a given PR is released in -- aka the JIRA "Fix Version"?
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
<http://www.linkedin.com/in/davidwsmiley>
On Wed, May 4, 2022 at 10:24 PM Tomoko Uchida <[email protected]
<mailto:[email protected]>> wrote:
Hello everyone!
Recently, we relaxed the requirement for creating a Jira issue when opening a pull
request (LUCENE-10545 <https://issues.apache.org/jira/browse/LUCENE-10545>).
As the next and bigger (perhaps ambitious) step, I opened a rough proposal for
migration to GitHub issue from Jira.
https://issues.apache.org/jira/browse/LUCENE-10557
<https://issues.apache.org/jira/browse/LUCENE-10557>
According to the INFRA issue for the RocketMQ project (Michael McCandless gave
the pointer in a comment on the issue; thanks!), a PMC agreement or Vote result
is needed for the decision.
https://issues.apache.org/jira/browse/INFRA-15702
<https://issues.apache.org/jira/browse/INFRA-15702>
Eventually, we'd need a formal vote, but before that, I'd like to hear general
opinions/thoughts (or feelings) on this topic from developers.
In brief, I think it'd be technically possible and also be good for the project
- not only for welcoming new developers who are not familiar with Jira, but
also for improving the experiences of long-term contributors by consolidating
the conversation platform.
It'll need some administrative work though, I'm willing to work for it if we
reach an agreement.
Please note that:
* This is not a VOTE. Simple vote-style feedback (+/- 1) is welcome, but we
don't aim to reach a conclusion in this thread.
* Let's not discuss "how to migrate existing Jira issues" for now. Once we
decide the migration will be good for us, then we can try to figure out a reasonable
solution for technical/administrative matters.
I may be too optimistic about it; but - a bit of stupidness will be needed to
start such a move, and I'm serious about this proposal :)
Thanks and regards,
Tomoko
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
