I'd like to see some discussion of pros/cons. Personally I don't have a lot of experience working with github's issue system, while I have grown comfortable with JIRA over the years, in spite of its warts. Here are a few things I like and *don't* like about both systems (mostly JIRA), but I don't know how github would compare:
1. non-standard text markup is forever confusing me (am I in "markup" mode or "visual" mode?) 2. search is cumbersome and difficult to use (but Mike M made https://jirasearch.mikemccandless.com/ which counters this problem) 3. setup is highly configurable, in terms of workflow, statuses, permissions and so on. Not sure if we need this though? 4. something in our current setup creates a lot of noise on the mailing list -- every comment seems to appear at least three times, sometimes formatted nicely, and other times buried in a mountain of code text. I don't know if this is JIRA, Github, or some unholy union of the two? 5. I find the Github commenting UI confusing -- what is the difference between conversation and review comments? How can I reply to a comment? What if I want to batch up a bunch of replies and send one email with all of them? Maybe it's just me, but I haven't found comfort with this yet. 6. Github is owned by a corporation. I assume we'd have enough legal protections to take our data with us if we need to, but it is possibly an extra hurdle to be concerned about. Would we need to / want to maintain a separate copy of the issue history? 7. What would happen with the JIRA history? Would we import it to Github issues? Leave it archived in JIRA? On Wed, May 4, 2022 at 10:24 PM Tomoko Uchida <tomoko.uchida.1...@gmail.com> wrote: > > Hello everyone! > > Recently, we relaxed the requirement for creating a Jira issue when opening a > pull request (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 > > 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 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
