I agree that JIRA is one extra step that is not adding a lot of value. Github issues are definitely better
On Fri, Oct 14, 2022 at 3:04 PM David Smiley <dsmi...@apache.org> wrote: > Sharing for visibility. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > ---------- Forwarded message --------- > From: Jeb Nix (Jira) <j...@apache.org> > Date: Mon, Oct 10, 2022 at 7:11 PM > Subject: [jira] [Created] (SOLR-16455) Migrate Jira to Github Issues and > Github Projects, and migrate mailing lists to Github Discussions > To: <iss...@solr.apache.org> > > > Jeb Nix created SOLR-16455: > ------------------------------ > > Summary: Migrate Jira to Github Issues and Github Projects, > and migrate mailing lists to Github Discussions > Key: SOLR-16455 > URL: https://issues.apache.org/jira/browse/SOLR-16455 > Project: Solr > Issue Type: Wish > Security Level: Public (Default Security Level. Issues are Public) > Components: github > Reporter: Jeb Nix > > > GitHub is where people are at when they lookup for Solr (or basically any > project). Most of the modern projects that have been started with Jira and > mailing lists have migrated to Github in the last few years. Lucene did > that just now for the Issues which has allowed me to explore much more of > their issues. GitHub works great and many think that it works even better > (I think that there is no doubt that it is working better for the > Discussions vs. Mailing lists). > > I suggest here a pretty heavy move, that personally will allow me to start > anticipating within Solr's community (since I really don't like the mailing > lists nor Jira), and I think that there are much more like me out there. In > my opinion, when the issues are managed on Github, it is much simpler to > collaborate and they will get wider exposure since developers are spending > time on Github anyway (whether if it's for their projects or for looking at > the actual source code). It is also important to mention that it is pretty > cumbersome for a new contributor that wants to add stuff to Solr, to talk > about this via mail, then translate them to Jira of the issues, and just > after that submit a PR on Github. e.g. 3 different systems for each > process. > > Actually, I thought such a great move (for me at least) would never happen > in Solr in the next years since I didn't think that the community sees & > understands the many advantages yet. But now that the Lucene guys did this, > I believe that it is possible for Solr too. > > > > -- > This message was sent by Atlassian Jira > (v8.20.10#820010) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org > For additional commands, e-mail: issues-h...@solr.apache.org > -- ----------------------------------------------------- Noble Paul
