You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Dominik Riemer <do...@bytefabrik.ai> on 2022/11/09 21:52:34 UTC

[DISCUSS] Migrate from Jira to Github Issues?

Hi everyone,

submitting bugs and feature requests are types of community contributions with a very low entry barrier for first-time contributors. To submit bug reports, users currently need to register in our Jira, which is not so straightforward for non-Apache-folks.
By using Github issues, I'd expect that users find a more convenient way to submit issues and we would foster community engagement.

There are more and more ASF projects which are moving to Github issues, e.g., our friends from PLC4X have just recently migrated and also Apache Airflow [1] and Apache Pulsar [2] are two great examples. I also like the Github discussion feature Airflow and Pulsar are using.

For some background information, people from Apache Beam have written a feature comparison [3], a migration guide [4] and even a migration tool [5] which we could also use to transfer our issues from Jira to Github.

What do you think?

Cheers
Dominik


[1] https://github.com/apache/airflow/issues
[2] https://github.com/apache/pulsar/discussions
[3] https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
[4] https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv

[5] https://github.com/google/jira-to-issues





Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Christofer Dutz <ch...@c-ware.de>.
In the PLC4X project, we did the same,

We did see a petty noticeable uptake on activity since then.


Chris

From: Dominik Riemer <ri...@apache.org>
Date: Friday, 25. November 2022 at 06:37
To: dev@streampipes.apache.org <de...@streampipes.apache.org>
Subject: RE: [DISCUSS] Migrate from Jira to Github Issues?
Hi everyone,

just to let you know that we will activate Github issues and try to migrate the existing issues from Jira to Github later today.

We will use a modified version of Apache Beam's migration tool where we can add a mapping from Jira users to Github users [1] so that we can keep all assignee info. It seems that this will only work for users with write access to the StreamPipes repo due to Github's spam protection. If you have any feedback, please feel free to create a PR!

Cheers
Dominik

[1] https://github.com/dominikriemer/jira-to-issues/blob/main/shared/translate.ts

On 2022/11/17 21:40:37 Dominik Riemer wrote:
> Hi,
> together with Tim, I plan to work during the next week to migrate our issues to Github and we'll send a proposal for a migration plan to the list within the next days. The goal is to move all issues from Jira to Github while keeping all relevant issue metadata where possible.
> There won't be any changes to the wiki right now, so it's totally fine to continue updating the Confluence wiki!
>
> Cheers
> Dominik
>
>
>
> -----Original Message-----
> From: Philipp Zehnder <ph...@bytefabrik.ai>
> Sent: Thursday, November 17, 2022 9:30 PM
> To: dev@streampipes.apache.org
> Subject: Re: [DISCUSS] Migrate from Jira to Github Issues?
>
> Hi,
>
> @Lukas thanks. We thought it might be helpful to have a single point for all the information relevant for developers on GitHub. I hope this will further lower the entry barrier for new developers. What do you think?
> And you are right, since the wiki is unrelated to the issues, we can also migrate them separately.
>
> @Florian, there is no timeline yet. If that is something you are interested to work on we can also discuss how the migration can be done.
>
> Cheers,
> Philipp
>
> ________________________________
> Von: Lukas Ott <ot...@gmail.com>
> Gesendet: Donnerstag, November 17, 2022 7:38 PM
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?
>
> Hi Florian,
>
> As your wiki is on Confluence:
> https://cwiki.apache.org/confluence/display/STREAMPIPES
>
> Like ours btw.
> https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver
>
> It is not impacted by moving the JIRA issues to Github.
>
> So Issue Tracking and Wiki are two separate parts. At least at PLC4X.
>
> Greetings,
> Lukas
>
> Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
> micklich@apache.org>:
>
> > Hi all,
> >
> > is there a timeline for when we want to start moving?
> > ALso what happens with the wiki.
> > I write on the wiki atm and before butting it into conf maybe it is
> > easier to start it on github?
> >
> > Greetings
> > Florian
> >
> > Am Freitag, dem 11.11.2022 um 12:49 +0100 schrieb Florian Micklich:
> > > Hi,<br>
> > >
> > > definitely agree.<br>
> > > I think there are a lot of benefits.<br> Big + for moving the wiki
> > > into github and put it into git as well.<br>
> > >
> > > 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.<br>
> > > But I think, if we write down the git "rules" and what to do in what
> > situation, we are on the right side.<br>
> > >
> > > I am happy to write the introduction after getting a short one
> > > :-)<br>
> > >
> > > Greetings<br>
> > > Florian<br>
> > >
> > >
> > >
> > > Am Donnerstag, dem 10.11.2022 um 16:51 +0000 schrieb Tim:<br>
> > > > Hi all,<br><br>
> > > >
> > > > I would also like to see us move our issues from JIRA to
> > Github.<br><br>
> > > > Beyond that, I fully agree with Philipp and would also bring the
> > <br><br>
> > > > "discussion" and "wiki" features.<br><br> It's nice to have
> > > > everything in one central place. This lowers the
> > <br><br>
> > > > barrier to entry in my opinion. Github provides great interaction
> > <br><br>
> > > > between these modules.<br><br>
> > > > Another advantage is that the wiki is then also versioned via Git
> > > > and
> > <br><br>
> > > > simply consists of Markdown files that you can edit with an editor
> > > > of
> > <br><br>
> > > > your choice.<br><br>
> > > > Last but not least, GitHub is the central entry point for open
> > > > source
> > <br><br>
> > > > projects, so we should make the best use of this entry
> > > > point.<br><br>
> > > >
> > > > Best<br><br>
> > > > Tim<br><br>
> > > >
> > > > Am 10.11.2022 08:50 schrieb Philipp Zehnder:<br><br>>
> > > > > Hi Dominik,<br><br>
> > > > >
> > > > > I am also in favor of migrating to GitHub issues.<br><br> I
> > > > > think it will ease the management of open issues and lower the
> > entry<br><br>
> > > > > barrier for new developers.<br><br>
> > > > >
> > > > > Further, I am in favor of using GitHub discussions, this is a
> > > > > good
> > way<br><br>
> > > > > to answer to common questions.<br><br> I think we should also
> > > > > move the wiki to GitHub, because then we
> > have<br><br>
> > > > > all the information for developers in one location.<br><br>
> > > > >
> > > > > Cheers,<br><br>
> > > > > Philipp<br><br>
> > > > >
> > > > >
> > > > > ________________________________<br><br>
> > > > > Von: Dominik Riemer <[[dominik.riemer@bytefabrik.ai](mailto:
> > dominik.riemer@bytefabrik.ai)](mailto:[dominik.riemer@bytefabrik.ai
> > ](mailto:dominik.riemer@bytefabrik.ai))><br><br<mailto:dominik.riemer@bytefabrik.ai))%3e%3cbr%3e%3cbr>>
> > > > > Gesendet: Mittwoch, November 9, 2022 10:52 PM<br><br>
> > > > > An:
> > > > > [[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> > )](mailto:[dev@streampipes.apache.org](mailto:dev@streampipes.apache.o
> > rg
> > )) <[[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> > )](mailto:[dev@streampipes.apache.org](mailto:dev@streampipes.apache.o
> > rg
> > ))><br><br>
> > > > > Betreff: [DISCUSS] Migrate from Jira to Github Issues?<br><br>
> > > > >
> > > > > Hi everyone,<br><br>
> > > > >
> > > > > submitting bugs and feature requests are types of
> > > > > community<br><br> contributions with a very low entry barrier
> > > > > for first-time<br><br> contributors. To submit bug reports,
> > > > > users currently need to
> > register<br><br>
> > > > > in our Jira, which is not so straightforward for
> > non-Apache-folks.<br><br>
> > > > > By using Github issues, I'd expect that users find a more
> > convenient<br><br>
> > > > > way to submit issues and we would foster community
> > engagement.<br><br>
> > > > >
> > > > > There are more and more ASF projects which are moving to
> > Github<br><br>
> > > > > issues, e.g., our friends from PLC4X have just recently migrated
> > and<br><br>
> > > > > also Apache Airflow [1] and Apache Pulsar [2] are two great
> > examples.<br><br>
> > > > > I also like the Github discussion feature Airflow and Pulsar
> > are<br><br>
> > > > > using.<br><br>
> > > > >
> > > > > For some background information, people from Apache Beam have
> > written<br><br>
> > > > > a feature comparison [3], a migration guide [4] and even a
> > migration<br><br>
> > > > > tool [5] which we could also use to transfer our issues from
> > > > > Jira
> > to<br><br>
> > > > > Github.<br><br>
> > > > >
> > > > > What do you think?<br><br>
> > > > >
> > > > > Cheers<br><br>
> > > > > Dominik<br><br>
> > > > >
> > > > >
> > > > > [1] [[
> > https://github.com/apache/airflow/issues](https://github.com/apache/ai<https://github.com/apache/airflow/issues%5d(https:/github.com/apache/ai>
> > rflow/issues)](https://github.com/apache/airflow/issues](https://githu
> > b.com/apache/airflow/issues))
> > <br><br>
> > > > > [2] [[
> > https://github.com/apache/pulsar/discussions](https://github.com/apach<https://github.com/apache/pulsar/discussions%5d(https:/github.com/apach>
> > e/pulsar/discussions)](https://github.com/apache/pulsar/discussions](h
> > ttps://github.com/apache/pulsar/discussions))
> > <br><br>
> > > > > [3]<br><br>
> > > > > [[
> > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqU
> > PCmiOslf0/edit#heading=h.r8qwrrbs8odn](https://docs.google.com/documen
> > t/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrr
> > bs8odn)](https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qp
> > NL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn](https://docs.google.co
> > m/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading
> > =h.r8qwrrbs8odn))
> > <br><br>
> > > > > [4]<br><br>
> > > > > [[
> > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy
> > 5MZu75Q5E/edit#heading=h.wskna8eurvjv](https://docs.google.com/documen
> > t/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8
> > eurvjv)](https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5H
> > M_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv](https://docs.google.co
> > m/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading
> > =h.wskna8eurvjv))
> > <br><br>
> > > > >
> > > > > [5] [[
> > https://github.com/google/jira-to-issues](https://github.com/google/ji<https://github.com/google/jira-to-issues%5d(https:/github.com/google/ji>
> > ra-to-issues)](https://github.com/google/jira-to-issues](https://githu
> > b.com/google/jira-to-issues))
> > <br><br>
> >
>

RE: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Dominik Riemer <ri...@apache.org>.
Hi everyone,

just to let you know that we will activate Github issues and try to migrate the existing issues from Jira to Github later today.

We will use a modified version of Apache Beam's migration tool where we can add a mapping from Jira users to Github users [1] so that we can keep all assignee info. It seems that this will only work for users with write access to the StreamPipes repo due to Github's spam protection. If you have any feedback, please feel free to create a PR! 

Cheers
Dominik

[1] https://github.com/dominikriemer/jira-to-issues/blob/main/shared/translate.ts

On 2022/11/17 21:40:37 Dominik Riemer wrote:
> Hi,
> together with Tim, I plan to work during the next week to migrate our issues to Github and we'll send a proposal for a migration plan to the list within the next days. The goal is to move all issues from Jira to Github while keeping all relevant issue metadata where possible.
> There won't be any changes to the wiki right now, so it's totally fine to continue updating the Confluence wiki!
> 
> Cheers
> Dominik
> 
> 
> 
> -----Original Message-----
> From: Philipp Zehnder <ph...@bytefabrik.ai> 
> Sent: Thursday, November 17, 2022 9:30 PM
> To: dev@streampipes.apache.org
> Subject: Re: [DISCUSS] Migrate from Jira to Github Issues?
> 
> Hi,
> 
> @Lukas thanks. We thought it might be helpful to have a single point for all the information relevant for developers on GitHub. I hope this will further lower the entry barrier for new developers. What do you think?
> And you are right, since the wiki is unrelated to the issues, we can also migrate them separately.
> 
> @Florian, there is no timeline yet. If that is something you are interested to work on we can also discuss how the migration can be done.
> 
> Cheers,
> Philipp
> 
> ________________________________
> Von: Lukas Ott <ot...@gmail.com>
> Gesendet: Donnerstag, November 17, 2022 7:38 PM
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?
> 
> Hi Florian,
> 
> As your wiki is on Confluence:
> https://cwiki.apache.org/confluence/display/STREAMPIPES
> 
> Like ours btw.
> https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver
> 
> It is not impacted by moving the JIRA issues to Github.
> 
> So Issue Tracking and Wiki are two separate parts. At least at PLC4X.
> 
> Greetings,
> Lukas
> 
> Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
> micklich@apache.org>:
> 
> > Hi all,
> >
> > is there a timeline for when we want to start moving?
> > ALso what happens with the wiki.
> > I write on the wiki atm and before butting it into conf maybe it is 
> > easier to start it on github?
> >
> > Greetings
> > Florian
> >
> > Am Freitag, dem 11.11.2022 um 12:49 +0100 schrieb Florian Micklich:
> > > Hi,<br>
> > >
> > > definitely agree.<br>
> > > I think there are a lot of benefits.<br> Big + for moving the wiki 
> > > into github and put it into git as well.<br>
> > >
> > > 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.<br>
> > > But I think, if we write down the git "rules" and what to do in what
> > situation, we are on the right side.<br>
> > >
> > > I am happy to write the introduction after getting a short one 
> > > :-)<br>
> > >
> > > Greetings<br>
> > > Florian<br>
> > >
> > >
> > >
> > > Am Donnerstag, dem 10.11.2022 um 16:51 +0000 schrieb Tim:<br>
> > > > Hi all,<br><br>
> > > >
> > > > I would also like to see us move our issues from JIRA to
> > Github.<br><br>
> > > > Beyond that, I fully agree with Philipp and would also bring the
> > <br><br>
> > > > "discussion" and "wiki" features.<br><br> It's nice to have 
> > > > everything in one central place. This lowers the
> > <br><br>
> > > > barrier to entry in my opinion. Github provides great interaction
> > <br><br>
> > > > between these modules.<br><br>
> > > > Another advantage is that the wiki is then also versioned via Git 
> > > > and
> > <br><br>
> > > > simply consists of Markdown files that you can edit with an editor 
> > > > of
> > <br><br>
> > > > your choice.<br><br>
> > > > Last but not least, GitHub is the central entry point for open 
> > > > source
> > <br><br>
> > > > projects, so we should make the best use of this entry 
> > > > point.<br><br>
> > > >
> > > > Best<br><br>
> > > > Tim<br><br>
> > > >
> > > > Am 10.11.2022 08:50 schrieb Philipp Zehnder:<br><br>>
> > > > > Hi Dominik,<br><br>
> > > > >
> > > > > I am also in favor of migrating to GitHub issues.<br><br> I 
> > > > > think it will ease the management of open issues and lower the
> > entry<br><br>
> > > > > barrier for new developers.<br><br>
> > > > >
> > > > > Further, I am in favor of using GitHub discussions, this is a 
> > > > > good
> > way<br><br>
> > > > > to answer to common questions.<br><br> I think we should also 
> > > > > move the wiki to GitHub, because then we
> > have<br><br>
> > > > > all the information for developers in one location.<br><br>
> > > > >
> > > > > Cheers,<br><br>
> > > > > Philipp<br><br>
> > > > >
> > > > >
> > > > > ________________________________<br><br>
> > > > > Von: Dominik Riemer <[[dominik.riemer@bytefabrik.ai](mailto:
> > dominik.riemer@bytefabrik.ai)](mailto:[dominik.riemer@bytefabrik.ai
> > ](mailto:dominik.riemer@bytefabrik.ai))><br><br>
> > > > > Gesendet: Mittwoch, November 9, 2022 10:52 PM<br><br>
> > > > > An: 
> > > > > [[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> > )](mailto:[dev@streampipes.apache.org](mailto:dev@streampipes.apache.o
> > rg
> > )) <[[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> > )](mailto:[dev@streampipes.apache.org](mailto:dev@streampipes.apache.o
> > rg
> > ))><br><br>
> > > > > Betreff: [DISCUSS] Migrate from Jira to Github Issues?<br><br>
> > > > >
> > > > > Hi everyone,<br><br>
> > > > >
> > > > > submitting bugs and feature requests are types of 
> > > > > community<br><br> contributions with a very low entry barrier 
> > > > > for first-time<br><br> contributors. To submit bug reports, 
> > > > > users currently need to
> > register<br><br>
> > > > > in our Jira, which is not so straightforward for
> > non-Apache-folks.<br><br>
> > > > > By using Github issues, I'd expect that users find a more
> > convenient<br><br>
> > > > > way to submit issues and we would foster community
> > engagement.<br><br>
> > > > >
> > > > > There are more and more ASF projects which are moving to
> > Github<br><br>
> > > > > issues, e.g., our friends from PLC4X have just recently migrated
> > and<br><br>
> > > > > also Apache Airflow [1] and Apache Pulsar [2] are two great
> > examples.<br><br>
> > > > > I also like the Github discussion feature Airflow and Pulsar
> > are<br><br>
> > > > > using.<br><br>
> > > > >
> > > > > For some background information, people from Apache Beam have
> > written<br><br>
> > > > > a feature comparison [3], a migration guide [4] and even a
> > migration<br><br>
> > > > > tool [5] which we could also use to transfer our issues from 
> > > > > Jira
> > to<br><br>
> > > > > Github.<br><br>
> > > > >
> > > > > What do you think?<br><br>
> > > > >
> > > > > Cheers<br><br>
> > > > > Dominik<br><br>
> > > > >
> > > > >
> > > > > [1] [[
> > https://github.com/apache/airflow/issues](https://github.com/apache/ai
> > rflow/issues)](https://github.com/apache/airflow/issues](https://githu
> > b.com/apache/airflow/issues))
> > <br><br>
> > > > > [2] [[
> > https://github.com/apache/pulsar/discussions](https://github.com/apach
> > e/pulsar/discussions)](https://github.com/apache/pulsar/discussions](h
> > ttps://github.com/apache/pulsar/discussions))
> > <br><br>
> > > > > [3]<br><br>
> > > > > [[
> > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqU
> > PCmiOslf0/edit#heading=h.r8qwrrbs8odn](https://docs.google.com/documen
> > t/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrr
> > bs8odn)](https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qp
> > NL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn](https://docs.google.co
> > m/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading
> > =h.r8qwrrbs8odn))
> > <br><br>
> > > > > [4]<br><br>
> > > > > [[
> > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy
> > 5MZu75Q5E/edit#heading=h.wskna8eurvjv](https://docs.google.com/documen
> > t/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8
> > eurvjv)](https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5H
> > M_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv](https://docs.google.co
> > m/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading
> > =h.wskna8eurvjv))
> > <br><br>
> > > > >
> > > > > [5] [[
> > https://github.com/google/jira-to-issues](https://github.com/google/ji
> > ra-to-issues)](https://github.com/google/jira-to-issues](https://githu
> > b.com/google/jira-to-issues))
> > <br><br>
> >
> 

RE: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Dominik Riemer <do...@bytefabrik.ai>.
Hi,
together with Tim, I plan to work during the next week to migrate our issues to Github and we'll send a proposal for a migration plan to the list within the next days. The goal is to move all issues from Jira to Github while keeping all relevant issue metadata where possible.
There won't be any changes to the wiki right now, so it's totally fine to continue updating the Confluence wiki!

Cheers
Dominik



-----Original Message-----
From: Philipp Zehnder <ph...@bytefabrik.ai> 
Sent: Thursday, November 17, 2022 9:30 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Migrate from Jira to Github Issues?

Hi,

@Lukas thanks. We thought it might be helpful to have a single point for all the information relevant for developers on GitHub. I hope this will further lower the entry barrier for new developers. What do you think?
And you are right, since the wiki is unrelated to the issues, we can also migrate them separately.

@Florian, there is no timeline yet. If that is something you are interested to work on we can also discuss how the migration can be done.

Cheers,
Philipp

________________________________
Von: Lukas Ott <ot...@gmail.com>
Gesendet: Donnerstag, November 17, 2022 7:38 PM
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?

Hi Florian,

As your wiki is on Confluence:
https://cwiki.apache.org/confluence/display/STREAMPIPES

Like ours btw.
https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver

It is not impacted by moving the JIRA issues to Github.

So Issue Tracking and Wiki are two separate parts. At least at PLC4X.

Greetings,
Lukas

Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
micklich@apache.org>:

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

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
Hi,

@Lukas thanks. We thought it might be helpful to have a single point for all the information relevant for developers on GitHub. I hope this will further lower the entry barrier for new developers. What do you think?
And you are right, since the wiki is unrelated to the issues, we can also migrate them separately.

@Florian, there is no timeline yet. If that is something you are interested to work on we can also discuss how the migration can be done.

Cheers,
Philipp

________________________________
Von: Lukas Ott <ot...@gmail.com>
Gesendet: Donnerstag, November 17, 2022 7:38 PM
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?

Hi Florian,

As your wiki is on Confluence:
https://cwiki.apache.org/confluence/display/STREAMPIPES

Like ours btw.
https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver

It is not impacted by moving the JIRA issues to Github.

So Issue Tracking and Wiki are two separate parts. At least at PLC4X.

Greetings,
Lukas

Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
micklich@apache.org>:

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

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Lukas Ott <ot...@gmail.com>.
Hi Florian,

As your wiki is on Confluence:
https://cwiki.apache.org/confluence/display/STREAMPIPES

Like ours btw.
https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver

It is not impacted by moving the JIRA issues to Github.

So Issue Tracking and Wiki are two separate parts. At least at PLC4X.

Greetings,
Lukas

Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
micklich@apache.org>:

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

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Florian Micklich <mi...@apache.org>.
Hi all,

is there a timeline for when we want to start moving?
ALso what happens with the wiki.
I write on the wiki atm and before butting it into conf maybe it is easier to start it on github?

Greetings
Florian

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

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Florian Micklich <mi...@apache.org>.
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 <[dominik.riemer@bytefabrik.ai](mailto:dominik.riemer@bytefabrik.ai)><br>
> > Gesendet: Mittwoch, November 9, 2022 10:52 PM<br>
> > An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)><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>

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Tim <bo...@posteo.de>.
Hi all,

I would also like to see us move our issues from JIRA to Github.
Beyond that, I fully agree with Philipp and would also bring the 
"discussion" and "wiki" features.
It's nice to have everything in one central place. This lowers the 
barrier to entry in my opinion. Github provides great interaction 
between these modules.
Another advantage is that the wiki is then also versioned via Git and 
simply consists of Markdown files that you can edit with an editor of 
your choice.
Last but not least, GitHub is the central entry point for open source 
projects, so we should make the best use of this entry point.

Best
Tim

Am 10.11.2022 08:50 schrieb Philipp Zehnder:
> Hi Dominik,
> 
> I am also in favor of migrating to GitHub issues.
> I think it will ease the management of open issues and lower the entry
> barrier for new developers.
> 
> Further, I am in favor of using GitHub discussions, this is a good way
> to answer to common questions.
> I think we should also move the wiki to GitHub, because then we have
> all the information for developers in one location.
> 
> Cheers,
> Philipp
> 
> 
> ________________________________
> Von: Dominik Riemer <do...@bytefabrik.ai>
> Gesendet: Mittwoch, November 9, 2022 10:52 PM
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: [DISCUSS] Migrate from Jira to Github Issues?
> 
> Hi everyone,
> 
> submitting bugs and feature requests are types of community
> contributions with a very low entry barrier for first-time
> contributors. To submit bug reports, users currently need to register
> in our Jira, which is not so straightforward for non-Apache-folks.
> By using Github issues, I'd expect that users find a more convenient
> way to submit issues and we would foster community engagement.
> 
> There are more and more ASF projects which are moving to Github
> issues, e.g., our friends from PLC4X have just recently migrated and
> also Apache Airflow [1] and Apache Pulsar [2] are two great examples.
> I also like the Github discussion feature Airflow and Pulsar are
> using.
> 
> For some background information, people from Apache Beam have written
> a feature comparison [3], a migration guide [4] and even a migration
> tool [5] which we could also use to transfer our issues from Jira to
> Github.
> 
> What do you think?
> 
> Cheers
> Dominik
> 
> 
> [1] https://github.com/apache/airflow/issues
> [2] https://github.com/apache/pulsar/discussions
> [3]
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> [4]
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> 
> [5] https://github.com/google/jira-to-issues

Re: [DISCUSS] Migrate from Jira to Github Issues?

Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
Hi Dominik,

I am also in favor of migrating to GitHub issues.
I think it will ease the management of open issues and lower the entry barrier for new developers.

Further, I am in favor of using GitHub discussions, this is a good way to answer to common questions.
I think we should also move the wiki to GitHub, because then we have all the information for developers in one location.

Cheers,
Philipp


________________________________
Von: Dominik Riemer <do...@bytefabrik.ai>
Gesendet: Mittwoch, November 9, 2022 10:52 PM
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: [DISCUSS] Migrate from Jira to Github Issues?

Hi everyone,

submitting bugs and feature requests are types of community contributions with a very low entry barrier for first-time contributors. To submit bug reports, users currently need to register in our Jira, which is not so straightforward for non-Apache-folks.
By using Github issues, I'd expect that users find a more convenient way to submit issues and we would foster community engagement.

There are more and more ASF projects which are moving to Github issues, e.g., our friends from PLC4X have just recently migrated and also Apache Airflow [1] and Apache Pulsar [2] are two great examples. I also like the Github discussion feature Airflow and Pulsar are using.

For some background information, people from Apache Beam have written a feature comparison [3], a migration guide [4] and even a migration tool [5] which we could also use to transfer our issues from Jira to Github.

What do you think?

Cheers
Dominik


[1] https://github.com/apache/airflow/issues
[2] https://github.com/apache/pulsar/discussions
[3] https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
[4] https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv

[5] https://github.com/google/jira-to-issues