[
https://issues.apache.org/jira/browse/SOLR-16455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeb Nix updated SOLR-16455:
---------------------------
Description:
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.
Other advantages are in the area of integrating code with issues. Take a look
at a new issue that has been submitted to Lucene, in which one can point to a
specific line:
!image-2022-10-11-02-25-04-799.png|width=886,height=288!
This is just a simple example, but I can easily dive into all of the minor and
major advantages of writing issues and discussions on Github rather than in
different places. I'll only mention now that the ability to write MD files is
much more convenient to a user that writing MD on PRs, and using two different
text editors for mail and Jira.
As for Apache Pony Mail, I think it is much better than actually using Gmail.
But I don't think it suits new users and it is not as close to being as modern
as GitHub Discussions (take a look at
https://github.com/facebook/docusaurus/discussions or
[https://github.com/apache/superset/discussions] for some examples).
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.
was:
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.
Other advantages are in the area of integrating code with issues. Take a look
at a new issue that has been submitted to Lucene, in which one can point to a
specific line:
!image-2022-10-11-02-25-04-799.png|width=886,height=288!
This is just a simple example, but I can easily dive into all of the minor and
major advantages of writing issues and discussions on Github rather than in
different places. I'll only mention now that the ability to write MD files is
much more convenient to a user that writing MD on PRs, and using two different
text editors for mail and Jira.
As for Apache Pony Mail, I think it is much better than actually using Gmail.
But I don't think it suits new users and it is not as close to being as modern
as GitHub Discussions.
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.
> 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
> Attachments: image-2022-10-11-02-25-04-799.png
>
>
> 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.
> Other advantages are in the area of integrating code with issues. Take a look
> at a new issue that has been submitted to Lucene, in which one can point to a
> specific line:
> !image-2022-10-11-02-25-04-799.png|width=886,height=288!
> This is just a simple example, but I can easily dive into all of the minor
> and major advantages of writing issues and discussions on Github rather than
> in different places. I'll only mention now that the ability to write MD files
> is much more convenient to a user that writing MD on PRs, and using two
> different text editors for mail and Jira.
> As for Apache Pony Mail, I think it is much better than actually using Gmail.
> But I don't think it suits new users and it is not as close to being as
> modern as GitHub Discussions (take a look at
> https://github.com/facebook/docusaurus/discussions or
> [https://github.com/apache/superset/discussions] for some examples).
> 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]
