Hi, definitely agree. I think there are a lot of benefits. Big + for moving the wiki into github and put it into git as well.
I come from the gitlab and jira world. So I want to keep in mind that there still could occur a "barrier" for new developer. But I think, if we write down the git "rules" and what to do in what situation, we are on the right side. I am happy to write the introduction after getting a short one :-) Greetings Florian Am Donnerstag, dem 10.11.2022 um 16:51 +0000 schrieb Tim: > Hi all,<br> > > I would also like to see us move our issues from JIRA to Github.<br> > Beyond that, I fully agree with Philipp and would also bring the <br> > "discussion" and "wiki" features.<br> > It's nice to have everything in one central place. This lowers the <br> > barrier to entry in my opinion. Github provides great interaction <br> > between these modules.<br> > Another advantage is that the wiki is then also versioned via Git and <br> > simply consists of Markdown files that you can edit with an editor of <br> > your choice.<br> > Last but not least, GitHub is the central entry point for open source <br> > projects, so we should make the best use of this entry point.<br> > > Best<br> > Tim<br> > > Am 10.11.2022 08:50 schrieb Philipp Zehnder:<br> > > Hi Dominik,<br> > > > > I am also in favor of migrating to GitHub issues.<br> > > I think it will ease the management of open issues and lower the entry<br> > > barrier for new developers.<br> > > > > Further, I am in favor of using GitHub discussions, this is a good way<br> > > to answer to common questions.<br> > > I think we should also move the wiki to GitHub, because then we have<br> > > all the information for developers in one location.<br> > > > > Cheers,<br> > > Philipp<br> > > > > > > ________________________________<br> > > Von: Dominik Riemer > > <[[email protected]](mailto:[email protected])><br> > > Gesendet: Mittwoch, November 9, 2022 10:52 PM<br> > > An: [[email protected]](mailto:[email protected]) > > <[[email protected]](mailto:[email protected])><br> > > Betreff: [DISCUSS] Migrate from Jira to Github Issues?<br> > > > > Hi everyone,<br> > > > > submitting bugs and feature requests are types of community<br> > > contributions with a very low entry barrier for first-time<br> > > contributors. To submit bug reports, users currently need to register<br> > > in our Jira, which is not so straightforward for non-Apache-folks.<br> > > By using Github issues, I'd expect that users find a more convenient<br> > > way to submit issues and we would foster community engagement.<br> > > > > There are more and more ASF projects which are moving to Github<br> > > issues, e.g., our friends from PLC4X have just recently migrated and<br> > > also Apache Airflow [1] and Apache Pulsar [2] are two great examples.<br> > > I also like the Github discussion feature Airflow and Pulsar are<br> > > using.<br> > > > > For some background information, people from Apache Beam have written<br> > > a feature comparison [3], a migration guide [4] and even a migration<br> > > tool [5] which we could also use to transfer our issues from Jira to<br> > > Github.<br> > > > > What do you think?<br> > > > > Cheers<br> > > Dominik<br> > > > > > > [1] > > [https://github.com/apache/airflow/issues](https://github.com/apache/airflow/issues)<br> > > [2] > > [https://github.com/apache/pulsar/discussions](https://github.com/apache/pulsar/discussions)<br> > > [3]<br> > > [https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn](https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn)<br> > > [4]<br> > > [https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv](https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv)<br> > > > > [5] > > [https://github.com/google/jira-to-issues](https://github.com/google/jira-to-issues)<br>
