[
https://issues.apache.org/jira/browse/SOLR-16455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615388#comment-17615388
]
Jeb Nix commented on SOLR-16455:
--------------------------------
It is important to mention in this context the importing Gist, and as well some
input from Lucene PMC will be great.
[https://gist.github.com/jonmagic/5282384165e0f86ef105]
Adding some articles on why Spring migrated to Github (which I think was very
successful):
[https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues]
And an interesting project at the subject -
[https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github]
> 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
> Priority: Trivial
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
