You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by jl hong <my...@gmail.com> on 2022/11/04 09:55:44 UTC
Re: [DISCUSS] Enable GitHub issues?
Hello Lukas,
- Driver-Profinet
- Driver-ADS
- API
- Driver-S7
- Core
- Util-Pool
- newbie
- Code-Generation
- Driver-Modbus
- Integration-NiFi
- feature-request
- Driver-OPC-UA
- documentation
- Scraper
- Driver-Fatek
- Testing
- Integration-Camel
- Driver-Ethernet/IP
- beginner
- feature
- low-hanging-fruit
- easy-fix
- PLC4C
- documentation-update
- docker
- Integration-Kafka-Connect
- examples
- Build
- Driver-CANopen
- PLC4J
The list which I got by jira-to-issues is current labels in our Jira.
Some of them are not on your list, such as "driver".
Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
> I started cleaning up the Issues on JIRA.
> Current status is 84 Issues.
>
> On Github I added a few labels.
> Current list of labels (17):
>
> - test
> - task
> - wish
> - new feature
> - bug
> - dependencies
> - duplicate
> - enhancement
> - go
> - good first issue
> - help wanted
> - invalid
> - java
> - python
> - question
> - wontfix
> - github_actions
>
> Open tasks:
> - Turn off new Jiras
> This can be done by turning off the create issue permission for all
> non-admins and adding an announcement in Portal Settings redirecting people
> to GitHub.
> - Migrating Existing Issues
> - Create / Add Issue Template
>
> Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> ben.hutche@gmail.com>:
>
> > +1
> >
> > This will make the issues more visible, which is probably a good thing.
> >
> > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott <ot...@gmail.com>
> wrote:
> >
> > > Thank you Dominik! This
> > >
> > > It seems we have less of the Cons they are mentioning :-)
> > > -> Google Summer of Code was not yet part of PLC4X
> > > -> We only need to migrate around 100 Jira issues
> > > -> I am not aware of any Milestones in our project that we track in
> Jira.
> > >
> > > Concerning preparation:
> > > - We already have list of labels
> > > List to be added:
> > >
> > > Category
> > >
> > > Values
> > >
> > > Priority
> > >
> > > "P0", "P1", "P2", "P3"
> > >
> > > Type
> > >
> > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> > >
> > > Component
> > >
> > > One label per JIRA component, formatted "Component: <JIRA component>"
> > (e.g.
> > > "Component: sdk-go")
> > >
> > > Status
> > >
> > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > >
> > >
> > > - Yes we should add a issue template
> > > This can be done by turning off the create issue permission for all
> > > non-admins and adding an announcement in Portal Settings redirecting
> > people
> > > to GitHub.
> > > - Update documentation after migration
> > >
> > > Next steps
> > > - Turn on Github Issues Tab
> > > - Turn off Jira Tickets (How do we do that?)
> > >
> > >
> > >
> > >
> > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> riemer@fzi.de
> > >:
> > >
> > > > I've recently looked at other ASF projects which discussed migration
> > from
> > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > >
> > > > Feature Comparison:
> > > >
> > >
> >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > Migration Plan:
> > > >
> > >
> >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > >
> > > > And Beam also open-sourced the migration tool they used:
> > > > https://github.com/google/jira-to-issues
> > > >
> > > > I've not yet tried it, but looks quite good 😉
> > > >
> > > > Cheers
> > > > Dominik
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Lukas Ott <ot...@gmail.com>
> > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > To: dev@plc4x.apache.org
> > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > >
> > > > I will look into that.
> > > >
> > > > Currently we have 103 open jira issues. Oldest one is more than 2
> years
> > > > ago.
> > > >
> > > >
> > > >
> > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > christofer.dutz@c-ware.de>:
> > > >
> > > > > I’m also fine with that.
> > > > > So anyone willing to work on the migration?
> > > > >
> > > > > Chris
> > > > >
> > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > Hi Chris,
> > > > >
> > > > > In my humble opinion we should not run parallel.
> > > > >
> > > > > Our Jira has already a lot of issues that are outdated.
> > > > >
> > > > > So i opt for enabling GitHub Issues and migrating the few Jira
> Issues
> > > > > that are still worked on.
> > > > >
> > > > > This helps us also for cleaning up and having one public issue
> > > > > tracker, where everyone can easily see what is worked on and what
> is
> > > > open.
> > > > >
> > > > > Luk
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > > christofer.dutz@c-ware.de>:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > for those of you that haven’t heard of it, Apache will be
> disabling
> > > > > signup
> > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > So, for people outside of the project, wanting to submit issues,
> > > > > > there will be no simple way to do so.
> > > > > >
> > > > > > How about we turn on GitHub Issues and simply run both in
> parallel.
> > > > > >
> > > > > > Chris
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Enable GitHub issues?
Posted by Lukas Ott <ot...@gmail.com>.
Hi Dominik,
It was straight foward and easy to use. :-)
KR
Lukas
Am Mi., 9. Nov. 2022 um 11:36 Uhr schrieb Dominik Riemer <ri...@fzi.de>:
> Hi Lukas,
>
> great work!
> Just out of interest, how was your experience when using the migration
> tool? Are there any pitfalls/things one should be aware of when configuring
> the migration?
>
> Cheers
> Dominik
>
> -----Original Message-----
> From: Lukas Ott <ot...@gmail.com>
> Sent: Wednesday, November 9, 2022 11:33 AM
> To: dev@plc4x.apache.org
> Subject: Re: [DISCUSS] Enable GitHub issues?
>
> successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately
> it seems i do not have the rights to close down our JIRA:
> "This can be done by turning off the create issue permission for all
> non-admins and adding an announcement in Portal Settings redirecting people
> to GitHub."
>
> Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott <ot...@apache.org>:
>
> > Updated:
> > - Driver-Profinet -> Profinet
> > - Driver-ADS -> ADS
> > - API -> API
> > - Driver-S7 -> S7
> > - Core -> ???
> > - Util-Pool -> ???
> > - newbie -> good first issue
> > - Code-Generation
> > - Driver-Modbus -> Modbus
> > - Integration-NiFi
> > - feature-request -> new feature
> > - Driver-OPC-UA -> OPC-UA
> > - documentation -> documentation
> > - Scraper -> ???
> > - Driver-Fatek -> Fatek
> > - Testing -> test
> > - Integration-Camel -> we have donated this to Apache Camel
> > - Driver-Ethernet/IP -> Ethernet/IP
> > - beginnerv -> good first issue
> > - feature -> new feature
> > - low-hanging-fruit -> good first issue
> > - easy-fix -> good first issue
> > - PLC4C -> c
> > - documentation-update -> documentation
> > - docker -> ???
> > - Integration-Kafka-Connect
> > - examples -> ??
> > - Build -> release
> > - Driver-CANopen -> CANopen
> > - PLC4J - > java
> >
> > On 2022/11/04 09:55:44 jl hong wrote:
> > > Hello Lukas,
> > >
> > > - Driver-Profinet
> > > - Driver-ADS
> > > - API
> > > - Driver-S7
> > > - Core
> > > - Util-Pool
> > > - newbie
> > > - Code-Generation
> > > - Driver-Modbus
> > > - Integration-NiFi
> > > - feature-request
> > > - Driver-OPC-UA
> > > - documentation
> > > - Scraper
> > > - Driver-Fatek
> > > - Testing
> > > - Integration-Camel
> > > - Driver-Ethernet/IP
> > > - beginner
> > > - feature
> > > - low-hanging-fruit
> > > - easy-fix
> > > - PLC4C
> > > - documentation-update
> > > - docker
> > > - Integration-Kafka-Connect
> > > - examples
> > > - Build
> > > - Driver-CANopen
> > > - PLC4J
> > >
> > > The list which I got by jira-to-issues is current labels in our Jira.
> > > Some of them are not on your list, such as "driver".
> > >
> > > Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
> > >
> > > > I started cleaning up the Issues on JIRA.
> > > > Current status is 84 Issues.
> > > >
> > > > On Github I added a few labels.
> > > > Current list of labels (17):
> > > >
> > > > - test
> > > > - task
> > > > - wish
> > > > - new feature
> > > > - bug
> > > > - dependencies
> > > > - duplicate
> > > > - enhancement
> > > > - go
> > > > - good first issue
> > > > - help wanted
> > > > - invalid
> > > > - java
> > > > - python
> > > > - question
> > > > - wontfix
> > > > - github_actions
> > > >
> > > > Open tasks:
> > > > - Turn off new Jiras
> > > > This can be done by turning off the create issue permission for
> > > > all non-admins and adding an announcement in Portal Settings
> > > > redirecting
> > people
> > > > to GitHub.
> > > > - Migrating Existing Issues
> > > > - Create / Add Issue Template
> > > >
> > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > > ben.hutche@gmail.com>:
> > > >
> > > > > +1
> > > > >
> > > > > This will make the issues more visible, which is probably a good
> > thing.
> > > > >
> > > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott
> > > > > <ot...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > Thank you Dominik! This
> > > > > >
> > > > > > It seems we have less of the Cons they are mentioning :-)
> > > > > > -> Google Summer of Code was not yet part of PLC4X We only
> > > > > > -> need to migrate around 100 Jira issues I am not aware of
> > > > > > -> any Milestones in our project that we track in
> > > > Jira.
> > > > > >
> > > > > > Concerning preparation:
> > > > > > - We already have list of labels List to be added:
> > > > > >
> > > > > > Category
> > > > > >
> > > > > > Values
> > > > > >
> > > > > > Priority
> > > > > >
> > > > > > "P0", "P1", "P2", "P3"
> > > > > >
> > > > > > Type
> > > > > >
> > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish",
> > "Outage"
> > > > > >
> > > > > > Component
> > > > > >
> > > > > > One label per JIRA component, formatted "Component: <JIRA
> > component>"
> > > > > (e.g.
> > > > > > "Component: sdk-go")
> > > > > >
> > > > > > Status
> > > > > >
> > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > > > >
> > > > > >
> > > > > > - Yes we should add a issue template This can be done by
> > > > > > turning off the create issue permission for all non-admins and
> > > > > > adding an announcement in Portal Settings
> > redirecting
> > > > > people
> > > > > > to GitHub.
> > > > > > - Update documentation after migration
> > > > > >
> > > > > > Next steps
> > > > > > - Turn on Github Issues Tab
> > > > > > - Turn off Jira Tickets (How do we do that?)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > > > riemer@fzi.de
> > > > > >:
> > > > > >
> > > > > > > I've recently looked at other ASF projects which discussed
> > migration
> > > > > from
> > > > > > > Jira to Github, e.g., here are some discussions from Apache
> Beam:
> > > > > > >
> > > > > > > Feature Comparison:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqU
> > PCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > > > Migration Plan:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy
> > 5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > > > >
> > > > > > > And Beam also open-sourced the migration tool they used:
> > > > > > > https://github.com/google/jira-to-issues
> > > > > > >
> > > > > > > I've not yet tried it, but looks quite good 😉
> > > > > > >
> > > > > > > Cheers
> > > > > > > Dominik
> > > > > > >
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > > > To: dev@plc4x.apache.org
> > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > >
> > > > > > > I will look into that.
> > > > > > >
> > > > > > > Currently we have 103 open jira issues. Oldest one is more
> > > > > > > than 2
> > > > years
> > > > > > > ago.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > > > christofer.dutz@c-ware.de>:
> > > > > > >
> > > > > > > > I’m also fine with that.
> > > > > > > > So anyone willing to work on the migration?
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > > > Hi Chris,
> > > > > > > >
> > > > > > > > In my humble opinion we should not run parallel.
> > > > > > > >
> > > > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > > > >
> > > > > > > > So i opt for enabling GitHub Issues and migrating the few
> > > > > > > > Jira
> > > > Issues
> > > > > > > > that are still worked on.
> > > > > > > >
> > > > > > > > This helps us also for cleaning up and having one public
> > > > > > > > issue tracker, where everyone can easily see what is
> > > > > > > > worked on and
> > what
> > > > is
> > > > > > > open.
> > > > > > > >
> > > > > > > > Luk
> > > > > > > >
> > > > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz
> > > > > > > > <
> > > > > > > > christofer.dutz@c-ware.de>:
> > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > for those of you that haven’t heard of it, Apache will
> > > > > > > > > be
> > > > disabling
> > > > > > > > signup
> > > > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > > > So, for people outside of the project, wanting to submit
> > issues,
> > > > > > > > > there will be no simple way to do so.
> > > > > > > > >
> > > > > > > > > How about we turn on GitHub Issues and simply run both
> > > > > > > > > in
> > > > parallel.
> > > > > > > > >
> > > > > > > > > Chris
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
RE: [DISCUSS] Enable GitHub issues?
Posted by Dominik Riemer <ri...@fzi.de>.
Hi Lukas,
great work!
Just out of interest, how was your experience when using the migration tool? Are there any pitfalls/things one should be aware of when configuring the migration?
Cheers
Dominik
-----Original Message-----
From: Lukas Ott <ot...@gmail.com>
Sent: Wednesday, November 9, 2022 11:33 AM
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Enable GitHub issues?
successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately it seems i do not have the rights to close down our JIRA:
"This can be done by turning off the create issue permission for all non-admins and adding an announcement in Portal Settings redirecting people to GitHub."
Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott <ot...@apache.org>:
> Updated:
> - Driver-Profinet -> Profinet
> - Driver-ADS -> ADS
> - API -> API
> - Driver-S7 -> S7
> - Core -> ???
> - Util-Pool -> ???
> - newbie -> good first issue
> - Code-Generation
> - Driver-Modbus -> Modbus
> - Integration-NiFi
> - feature-request -> new feature
> - Driver-OPC-UA -> OPC-UA
> - documentation -> documentation
> - Scraper -> ???
> - Driver-Fatek -> Fatek
> - Testing -> test
> - Integration-Camel -> we have donated this to Apache Camel
> - Driver-Ethernet/IP -> Ethernet/IP
> - beginnerv -> good first issue
> - feature -> new feature
> - low-hanging-fruit -> good first issue
> - easy-fix -> good first issue
> - PLC4C -> c
> - documentation-update -> documentation
> - docker -> ???
> - Integration-Kafka-Connect
> - examples -> ??
> - Build -> release
> - Driver-CANopen -> CANopen
> - PLC4J - > java
>
> On 2022/11/04 09:55:44 jl hong wrote:
> > Hello Lukas,
> >
> > - Driver-Profinet
> > - Driver-ADS
> > - API
> > - Driver-S7
> > - Core
> > - Util-Pool
> > - newbie
> > - Code-Generation
> > - Driver-Modbus
> > - Integration-NiFi
> > - feature-request
> > - Driver-OPC-UA
> > - documentation
> > - Scraper
> > - Driver-Fatek
> > - Testing
> > - Integration-Camel
> > - Driver-Ethernet/IP
> > - beginner
> > - feature
> > - low-hanging-fruit
> > - easy-fix
> > - PLC4C
> > - documentation-update
> > - docker
> > - Integration-Kafka-Connect
> > - examples
> > - Build
> > - Driver-CANopen
> > - PLC4J
> >
> > The list which I got by jira-to-issues is current labels in our Jira.
> > Some of them are not on your list, such as "driver".
> >
> > Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
> >
> > > I started cleaning up the Issues on JIRA.
> > > Current status is 84 Issues.
> > >
> > > On Github I added a few labels.
> > > Current list of labels (17):
> > >
> > > - test
> > > - task
> > > - wish
> > > - new feature
> > > - bug
> > > - dependencies
> > > - duplicate
> > > - enhancement
> > > - go
> > > - good first issue
> > > - help wanted
> > > - invalid
> > > - java
> > > - python
> > > - question
> > > - wontfix
> > > - github_actions
> > >
> > > Open tasks:
> > > - Turn off new Jiras
> > > This can be done by turning off the create issue permission for
> > > all non-admins and adding an announcement in Portal Settings
> > > redirecting
> people
> > > to GitHub.
> > > - Migrating Existing Issues
> > > - Create / Add Issue Template
> > >
> > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > ben.hutche@gmail.com>:
> > >
> > > > +1
> > > >
> > > > This will make the issues more visible, which is probably a good
> thing.
> > > >
> > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott
> > > > <ot...@gmail.com>
> > > wrote:
> > > >
> > > > > Thank you Dominik! This
> > > > >
> > > > > It seems we have less of the Cons they are mentioning :-)
> > > > > -> Google Summer of Code was not yet part of PLC4X We only
> > > > > -> need to migrate around 100 Jira issues I am not aware of
> > > > > -> any Milestones in our project that we track in
> > > Jira.
> > > > >
> > > > > Concerning preparation:
> > > > > - We already have list of labels List to be added:
> > > > >
> > > > > Category
> > > > >
> > > > > Values
> > > > >
> > > > > Priority
> > > > >
> > > > > "P0", "P1", "P2", "P3"
> > > > >
> > > > > Type
> > > > >
> > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish",
> "Outage"
> > > > >
> > > > > Component
> > > > >
> > > > > One label per JIRA component, formatted "Component: <JIRA
> component>"
> > > > (e.g.
> > > > > "Component: sdk-go")
> > > > >
> > > > > Status
> > > > >
> > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > > >
> > > > >
> > > > > - Yes we should add a issue template This can be done by
> > > > > turning off the create issue permission for all non-admins and
> > > > > adding an announcement in Portal Settings
> redirecting
> > > > people
> > > > > to GitHub.
> > > > > - Update documentation after migration
> > > > >
> > > > > Next steps
> > > > > - Turn on Github Issues Tab
> > > > > - Turn off Jira Tickets (How do we do that?)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > > riemer@fzi.de
> > > > >:
> > > > >
> > > > > > I've recently looked at other ASF projects which discussed
> migration
> > > > from
> > > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > > >
> > > > > > Feature Comparison:
> > > > > >
> > > > >
> > > >
> > >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqU
> PCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > > Migration Plan:
> > > > > >
> > > > >
> > > >
> > >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy
> 5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > > >
> > > > > > And Beam also open-sourced the migration tool they used:
> > > > > > https://github.com/google/jira-to-issues
> > > > > >
> > > > > > I've not yet tried it, but looks quite good 😉
> > > > > >
> > > > > > Cheers
> > > > > > Dominik
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > > To: dev@plc4x.apache.org
> > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > >
> > > > > > I will look into that.
> > > > > >
> > > > > > Currently we have 103 open jira issues. Oldest one is more
> > > > > > than 2
> > > years
> > > > > > ago.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > > christofer.dutz@c-ware.de>:
> > > > > >
> > > > > > > I’m also fine with that.
> > > > > > > So anyone willing to work on the migration?
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > > Hi Chris,
> > > > > > >
> > > > > > > In my humble opinion we should not run parallel.
> > > > > > >
> > > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > > >
> > > > > > > So i opt for enabling GitHub Issues and migrating the few
> > > > > > > Jira
> > > Issues
> > > > > > > that are still worked on.
> > > > > > >
> > > > > > > This helps us also for cleaning up and having one public
> > > > > > > issue tracker, where everyone can easily see what is
> > > > > > > worked on and
> what
> > > is
> > > > > > open.
> > > > > > >
> > > > > > > Luk
> > > > > > >
> > > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz
> > > > > > > <
> > > > > > > christofer.dutz@c-ware.de>:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > for those of you that haven’t heard of it, Apache will
> > > > > > > > be
> > > disabling
> > > > > > > signup
> > > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > > So, for people outside of the project, wanting to submit
> issues,
> > > > > > > > there will be no simple way to do so.
> > > > > > > >
> > > > > > > > How about we turn on GitHub Issues and simply run both
> > > > > > > > in
> > > parallel.
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Enable GitHub issues?
Posted by Lukas Ott <ot...@gmail.com>.
successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately
it seems i do not have the rights to close down our JIRA:
"This can be done by turning off the create issue permission for all
non-admins and adding an announcement in Portal Settings redirecting people
to GitHub."
Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott <ot...@apache.org>:
> Updated:
> - Driver-Profinet -> Profinet
> - Driver-ADS -> ADS
> - API -> API
> - Driver-S7 -> S7
> - Core -> ???
> - Util-Pool -> ???
> - newbie -> good first issue
> - Code-Generation
> - Driver-Modbus -> Modbus
> - Integration-NiFi
> - feature-request -> new feature
> - Driver-OPC-UA -> OPC-UA
> - documentation -> documentation
> - Scraper -> ???
> - Driver-Fatek -> Fatek
> - Testing -> test
> - Integration-Camel -> we have donated this to Apache Camel
> - Driver-Ethernet/IP -> Ethernet/IP
> - beginnerv -> good first issue
> - feature -> new feature
> - low-hanging-fruit -> good first issue
> - easy-fix -> good first issue
> - PLC4C -> c
> - documentation-update -> documentation
> - docker -> ???
> - Integration-Kafka-Connect
> - examples -> ??
> - Build -> release
> - Driver-CANopen -> CANopen
> - PLC4J - > java
>
> On 2022/11/04 09:55:44 jl hong wrote:
> > Hello Lukas,
> >
> > - Driver-Profinet
> > - Driver-ADS
> > - API
> > - Driver-S7
> > - Core
> > - Util-Pool
> > - newbie
> > - Code-Generation
> > - Driver-Modbus
> > - Integration-NiFi
> > - feature-request
> > - Driver-OPC-UA
> > - documentation
> > - Scraper
> > - Driver-Fatek
> > - Testing
> > - Integration-Camel
> > - Driver-Ethernet/IP
> > - beginner
> > - feature
> > - low-hanging-fruit
> > - easy-fix
> > - PLC4C
> > - documentation-update
> > - docker
> > - Integration-Kafka-Connect
> > - examples
> > - Build
> > - Driver-CANopen
> > - PLC4J
> >
> > The list which I got by jira-to-issues is current labels in our Jira.
> > Some of them are not on your list, such as "driver".
> >
> > Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
> >
> > > I started cleaning up the Issues on JIRA.
> > > Current status is 84 Issues.
> > >
> > > On Github I added a few labels.
> > > Current list of labels (17):
> > >
> > > - test
> > > - task
> > > - wish
> > > - new feature
> > > - bug
> > > - dependencies
> > > - duplicate
> > > - enhancement
> > > - go
> > > - good first issue
> > > - help wanted
> > > - invalid
> > > - java
> > > - python
> > > - question
> > > - wontfix
> > > - github_actions
> > >
> > > Open tasks:
> > > - Turn off new Jiras
> > > This can be done by turning off the create issue permission for all
> > > non-admins and adding an announcement in Portal Settings redirecting
> people
> > > to GitHub.
> > > - Migrating Existing Issues
> > > - Create / Add Issue Template
> > >
> > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > ben.hutche@gmail.com>:
> > >
> > > > +1
> > > >
> > > > This will make the issues more visible, which is probably a good
> thing.
> > > >
> > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott <ot...@gmail.com>
> > > wrote:
> > > >
> > > > > Thank you Dominik! This
> > > > >
> > > > > It seems we have less of the Cons they are mentioning :-)
> > > > > -> Google Summer of Code was not yet part of PLC4X
> > > > > -> We only need to migrate around 100 Jira issues
> > > > > -> I am not aware of any Milestones in our project that we track in
> > > Jira.
> > > > >
> > > > > Concerning preparation:
> > > > > - We already have list of labels
> > > > > List to be added:
> > > > >
> > > > > Category
> > > > >
> > > > > Values
> > > > >
> > > > > Priority
> > > > >
> > > > > "P0", "P1", "P2", "P3"
> > > > >
> > > > > Type
> > > > >
> > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish",
> "Outage"
> > > > >
> > > > > Component
> > > > >
> > > > > One label per JIRA component, formatted "Component: <JIRA
> component>"
> > > > (e.g.
> > > > > "Component: sdk-go")
> > > > >
> > > > > Status
> > > > >
> > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > > >
> > > > >
> > > > > - Yes we should add a issue template
> > > > > This can be done by turning off the create issue permission for all
> > > > > non-admins and adding an announcement in Portal Settings
> redirecting
> > > > people
> > > > > to GitHub.
> > > > > - Update documentation after migration
> > > > >
> > > > > Next steps
> > > > > - Turn on Github Issues Tab
> > > > > - Turn off Jira Tickets (How do we do that?)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > > riemer@fzi.de
> > > > >:
> > > > >
> > > > > > I've recently looked at other ASF projects which discussed
> migration
> > > > from
> > > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > > >
> > > > > > Feature Comparison:
> > > > > >
> > > > >
> > > >
> > >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > > Migration Plan:
> > > > > >
> > > > >
> > > >
> > >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > > >
> > > > > > And Beam also open-sourced the migration tool they used:
> > > > > > https://github.com/google/jira-to-issues
> > > > > >
> > > > > > I've not yet tried it, but looks quite good 😉
> > > > > >
> > > > > > Cheers
> > > > > > Dominik
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > > To: dev@plc4x.apache.org
> > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > >
> > > > > > I will look into that.
> > > > > >
> > > > > > Currently we have 103 open jira issues. Oldest one is more than 2
> > > years
> > > > > > ago.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > > christofer.dutz@c-ware.de>:
> > > > > >
> > > > > > > I’m also fine with that.
> > > > > > > So anyone willing to work on the migration?
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > > Hi Chris,
> > > > > > >
> > > > > > > In my humble opinion we should not run parallel.
> > > > > > >
> > > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > > >
> > > > > > > So i opt for enabling GitHub Issues and migrating the few Jira
> > > Issues
> > > > > > > that are still worked on.
> > > > > > >
> > > > > > > This helps us also for cleaning up and having one public issue
> > > > > > > tracker, where everyone can easily see what is worked on and
> what
> > > is
> > > > > > open.
> > > > > > >
> > > > > > > Luk
> > > > > > >
> > > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > > > > christofer.dutz@c-ware.de>:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > for those of you that haven’t heard of it, Apache will be
> > > disabling
> > > > > > > signup
> > > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > > So, for people outside of the project, wanting to submit
> issues,
> > > > > > > > there will be no simple way to do so.
> > > > > > > >
> > > > > > > > How about we turn on GitHub Issues and simply run both in
> > > parallel.
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Enable GitHub issues?
Posted by Lukas Ott <ot...@apache.org>.
Updated:
- Driver-Profinet -> Profinet
- Driver-ADS -> ADS
- API -> API
- Driver-S7 -> S7
- Core -> ???
- Util-Pool -> ???
- newbie -> good first issue
- Code-Generation
- Driver-Modbus -> Modbus
- Integration-NiFi
- feature-request -> new feature
- Driver-OPC-UA -> OPC-UA
- documentation -> documentation
- Scraper -> ???
- Driver-Fatek -> Fatek
- Testing -> test
- Integration-Camel -> we have donated this to Apache Camel
- Driver-Ethernet/IP -> Ethernet/IP
- beginnerv -> good first issue
- feature -> new feature
- low-hanging-fruit -> good first issue
- easy-fix -> good first issue
- PLC4C -> c
- documentation-update -> documentation
- docker -> ???
- Integration-Kafka-Connect
- examples -> ??
- Build -> release
- Driver-CANopen -> CANopen
- PLC4J - > java
On 2022/11/04 09:55:44 jl hong wrote:
> Hello Lukas,
>
> - Driver-Profinet
> - Driver-ADS
> - API
> - Driver-S7
> - Core
> - Util-Pool
> - newbie
> - Code-Generation
> - Driver-Modbus
> - Integration-NiFi
> - feature-request
> - Driver-OPC-UA
> - documentation
> - Scraper
> - Driver-Fatek
> - Testing
> - Integration-Camel
> - Driver-Ethernet/IP
> - beginner
> - feature
> - low-hanging-fruit
> - easy-fix
> - PLC4C
> - documentation-update
> - docker
> - Integration-Kafka-Connect
> - examples
> - Build
> - Driver-CANopen
> - PLC4J
>
> The list which I got by jira-to-issues is current labels in our Jira.
> Some of them are not on your list, such as "driver".
>
> Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
>
> > I started cleaning up the Issues on JIRA.
> > Current status is 84 Issues.
> >
> > On Github I added a few labels.
> > Current list of labels (17):
> >
> > - test
> > - task
> > - wish
> > - new feature
> > - bug
> > - dependencies
> > - duplicate
> > - enhancement
> > - go
> > - good first issue
> > - help wanted
> > - invalid
> > - java
> > - python
> > - question
> > - wontfix
> > - github_actions
> >
> > Open tasks:
> > - Turn off new Jiras
> > This can be done by turning off the create issue permission for all
> > non-admins and adding an announcement in Portal Settings redirecting people
> > to GitHub.
> > - Migrating Existing Issues
> > - Create / Add Issue Template
> >
> > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > ben.hutche@gmail.com>:
> >
> > > +1
> > >
> > > This will make the issues more visible, which is probably a good thing.
> > >
> > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott <ot...@gmail.com>
> > wrote:
> > >
> > > > Thank you Dominik! This
> > > >
> > > > It seems we have less of the Cons they are mentioning :-)
> > > > -> Google Summer of Code was not yet part of PLC4X
> > > > -> We only need to migrate around 100 Jira issues
> > > > -> I am not aware of any Milestones in our project that we track in
> > Jira.
> > > >
> > > > Concerning preparation:
> > > > - We already have list of labels
> > > > List to be added:
> > > >
> > > > Category
> > > >
> > > > Values
> > > >
> > > > Priority
> > > >
> > > > "P0", "P1", "P2", "P3"
> > > >
> > > > Type
> > > >
> > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> > > >
> > > > Component
> > > >
> > > > One label per JIRA component, formatted "Component: <JIRA component>"
> > > (e.g.
> > > > "Component: sdk-go")
> > > >
> > > > Status
> > > >
> > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > >
> > > >
> > > > - Yes we should add a issue template
> > > > This can be done by turning off the create issue permission for all
> > > > non-admins and adding an announcement in Portal Settings redirecting
> > > people
> > > > to GitHub.
> > > > - Update documentation after migration
> > > >
> > > > Next steps
> > > > - Turn on Github Issues Tab
> > > > - Turn off Jira Tickets (How do we do that?)
> > > >
> > > >
> > > >
> > > >
> > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > riemer@fzi.de
> > > >:
> > > >
> > > > > I've recently looked at other ASF projects which discussed migration
> > > from
> > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > >
> > > > > Feature Comparison:
> > > > >
> > > >
> > >
> > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > Migration Plan:
> > > > >
> > > >
> > >
> > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > >
> > > > > And Beam also open-sourced the migration tool they used:
> > > > > https://github.com/google/jira-to-issues
> > > > >
> > > > > I've not yet tried it, but looks quite good 😉
> > > > >
> > > > > Cheers
> > > > > Dominik
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > To: dev@plc4x.apache.org
> > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > >
> > > > > I will look into that.
> > > > >
> > > > > Currently we have 103 open jira issues. Oldest one is more than 2
> > years
> > > > > ago.
> > > > >
> > > > >
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > christofer.dutz@c-ware.de>:
> > > > >
> > > > > > I’m also fine with that.
> > > > > > So anyone willing to work on the migration?
> > > > > >
> > > > > > Chris
> > > > > >
> > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > Hi Chris,
> > > > > >
> > > > > > In my humble opinion we should not run parallel.
> > > > > >
> > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > >
> > > > > > So i opt for enabling GitHub Issues and migrating the few Jira
> > Issues
> > > > > > that are still worked on.
> > > > > >
> > > > > > This helps us also for cleaning up and having one public issue
> > > > > > tracker, where everyone can easily see what is worked on and what
> > is
> > > > > open.
> > > > > >
> > > > > > Luk
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > > > christofer.dutz@c-ware.de>:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > for those of you that haven’t heard of it, Apache will be
> > disabling
> > > > > > signup
> > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > So, for people outside of the project, wanting to submit issues,
> > > > > > > there will be no simple way to do so.
> > > > > > >
> > > > > > > How about we turn on GitHub Issues and simply run both in
> > parallel.
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Enable GitHub issues?
Posted by jl hong <my...@gmail.com>.
ok :)
Lukas Ott <ot...@gmail.com>于2022年11月4日 周五20:08写道：
> Feel free to add them as labels on our Github :-)
>
> Am Fr., 4. Nov. 2022 um 10:56 Uhr schrieb jl hong <myhongjinlin@gmail.com
> >:
>
> > Hello Lukas,
> >
> > - Driver-Profinet
> > - Driver-ADS
> > - API
> > - Driver-S7
> > - Core
> > - Util-Pool
> > - newbie
> > - Code-Generation
> > - Driver-Modbus
> > - Integration-NiFi
> > - feature-request
> > - Driver-OPC-UA
> > - documentation
> > - Scraper
> > - Driver-Fatek
> > - Testing
> > - Integration-Camel
> > - Driver-Ethernet/IP
> > - beginner
> > - feature
> > - low-hanging-fruit
> > - easy-fix
> > - PLC4C
> > - documentation-update
> > - docker
> > - Integration-Kafka-Connect
> > - examples
> > - Build
> > - Driver-CANopen
> > - PLC4J
> >
> > The list which I got by jira-to-issues is current labels in our Jira.
> > Some of them are not on your list, such as "driver".
> >
> > Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
> >
> > > I started cleaning up the Issues on JIRA.
> > > Current status is 84 Issues.
> > >
> > > On Github I added a few labels.
> > > Current list of labels (17):
> > >
> > > - test
> > > - task
> > > - wish
> > > - new feature
> > > - bug
> > > - dependencies
> > > - duplicate
> > > - enhancement
> > > - go
> > > - good first issue
> > > - help wanted
> > > - invalid
> > > - java
> > > - python
> > > - question
> > > - wontfix
> > > - github_actions
> > >
> > > Open tasks:
> > > - Turn off new Jiras
> > > This can be done by turning off the create issue permission for all
> > > non-admins and adding an announcement in Portal Settings redirecting
> > people
> > > to GitHub.
> > > - Migrating Existing Issues
> > > - Create / Add Issue Template
> > >
> > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > > ben.hutche@gmail.com>:
> > >
> > > > +1
> > > >
> > > > This will make the issues more visible, which is probably a good
> thing.
> > > >
> > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott <ot...@gmail.com>
> > > wrote:
> > > >
> > > > > Thank you Dominik! This
> > > > >
> > > > > It seems we have less of the Cons they are mentioning :-)
> > > > > -> Google Summer of Code was not yet part of PLC4X
> > > > > -> We only need to migrate around 100 Jira issues
> > > > > -> I am not aware of any Milestones in our project that we track in
> > > Jira.
> > > > >
> > > > > Concerning preparation:
> > > > > - We already have list of labels
> > > > > List to be added:
> > > > >
> > > > > Category
> > > > >
> > > > > Values
> > > > >
> > > > > Priority
> > > > >
> > > > > "P0", "P1", "P2", "P3"
> > > > >
> > > > > Type
> > > > >
> > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish",
> "Outage"
> > > > >
> > > > > Component
> > > > >
> > > > > One label per JIRA component, formatted "Component: <JIRA
> component>"
> > > > (e.g.
> > > > > "Component: sdk-go")
> > > > >
> > > > > Status
> > > > >
> > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > > >
> > > > >
> > > > > - Yes we should add a issue template
> > > > > This can be done by turning off the create issue permission for all
> > > > > non-admins and adding an announcement in Portal Settings
> redirecting
> > > > people
> > > > > to GitHub.
> > > > > - Update documentation after migration
> > > > >
> > > > > Next steps
> > > > > - Turn on Github Issues Tab
> > > > > - Turn off Jira Tickets (How do we do that?)
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > > riemer@fzi.de
> > > > >:
> > > > >
> > > > > > I've recently looked at other ASF projects which discussed
> > migration
> > > > from
> > > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > > >
> > > > > > Feature Comparison:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > > Migration Plan:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > > >
> > > > > > And Beam also open-sourced the migration tool they used:
> > > > > > https://github.com/google/jira-to-issues
> > > > > >
> > > > > > I've not yet tried it, but looks quite good 😉
> > > > > >
> > > > > > Cheers
> > > > > > Dominik
> > > > > >
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > > To: dev@plc4x.apache.org
> > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > >
> > > > > > I will look into that.
> > > > > >
> > > > > > Currently we have 103 open jira issues. Oldest one is more than 2
> > > years
> > > > > > ago.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > > christofer.dutz@c-ware.de>:
> > > > > >
> > > > > > > I’m also fine with that.
> > > > > > > So anyone willing to work on the migration?
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > > Hi Chris,
> > > > > > >
> > > > > > > In my humble opinion we should not run parallel.
> > > > > > >
> > > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > > >
> > > > > > > So i opt for enabling GitHub Issues and migrating the few Jira
> > > Issues
> > > > > > > that are still worked on.
> > > > > > >
> > > > > > > This helps us also for cleaning up and having one public issue
> > > > > > > tracker, where everyone can easily see what is worked on and
> what
> > > is
> > > > > > open.
> > > > > > >
> > > > > > > Luk
> > > > > > >
> > > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > > > > christofer.dutz@c-ware.de>:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > for those of you that haven’t heard of it, Apache will be
> > > disabling
> > > > > > > signup
> > > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > > So, for people outside of the project, wanting to submit
> > issues,
> > > > > > > > there will be no simple way to do so.
> > > > > > > >
> > > > > > > > How about we turn on GitHub Issues and simply run both in
> > > parallel.
> > > > > > > >
> > > > > > > > Chris
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Enable GitHub issues?
Posted by Lukas Ott <ot...@gmail.com>.
Feel free to add them as labels on our Github :-)
Am Fr., 4. Nov. 2022 um 10:56 Uhr schrieb jl hong <my...@gmail.com>:
> Hello Lukas,
>
> - Driver-Profinet
> - Driver-ADS
> - API
> - Driver-S7
> - Core
> - Util-Pool
> - newbie
> - Code-Generation
> - Driver-Modbus
> - Integration-NiFi
> - feature-request
> - Driver-OPC-UA
> - documentation
> - Scraper
> - Driver-Fatek
> - Testing
> - Integration-Camel
> - Driver-Ethernet/IP
> - beginner
> - feature
> - low-hanging-fruit
> - easy-fix
> - PLC4C
> - documentation-update
> - docker
> - Integration-Kafka-Connect
> - examples
> - Build
> - Driver-CANopen
> - PLC4J
>
> The list which I got by jira-to-issues is current labels in our Jira.
> Some of them are not on your list, such as "driver".
>
> Lukas Ott <ot...@gmail.com> 於 2022年11月1日 週二 凌晨3:25寫道：
>
> > I started cleaning up the Issues on JIRA.
> > Current status is 84 Issues.
> >
> > On Github I added a few labels.
> > Current list of labels (17):
> >
> > - test
> > - task
> > - wish
> > - new feature
> > - bug
> > - dependencies
> > - duplicate
> > - enhancement
> > - go
> > - good first issue
> > - help wanted
> > - invalid
> > - java
> > - python
> > - question
> > - wontfix
> > - github_actions
> >
> > Open tasks:
> > - Turn off new Jiras
> > This can be done by turning off the create issue permission for all
> > non-admins and adding an announcement in Portal Settings redirecting
> people
> > to GitHub.
> > - Migrating Existing Issues
> > - Create / Add Issue Template
> >
> > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson <
> > ben.hutche@gmail.com>:
> >
> > > +1
> > >
> > > This will make the issues more visible, which is probably a good thing.
> > >
> > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott <ot...@gmail.com>
> > wrote:
> > >
> > > > Thank you Dominik! This
> > > >
> > > > It seems we have less of the Cons they are mentioning :-)
> > > > -> Google Summer of Code was not yet part of PLC4X
> > > > -> We only need to migrate around 100 Jira issues
> > > > -> I am not aware of any Milestones in our project that we track in
> > Jira.
> > > >
> > > > Concerning preparation:
> > > > - We already have list of labels
> > > > List to be added:
> > > >
> > > > Category
> > > >
> > > > Values
> > > >
> > > > Priority
> > > >
> > > > "P0", "P1", "P2", "P3"
> > > >
> > > > Type
> > > >
> > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage"
> > > >
> > > > Component
> > > >
> > > > One label per JIRA component, formatted "Component: <JIRA component>"
> > > (e.g.
> > > > "Component: sdk-go")
> > > >
> > > > Status
> > > >
> > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate"
> > > >
> > > >
> > > > - Yes we should add a issue template
> > > > This can be done by turning off the create issue permission for all
> > > > non-admins and adding an announcement in Portal Settings redirecting
> > > people
> > > > to GitHub.
> > > > - Update documentation after migration
> > > >
> > > > Next steps
> > > > - Turn on Github Issues Tab
> > > > - Turn off Jira Tickets (How do we do that?)
> > > >
> > > >
> > > >
> > > >
> > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer <
> > riemer@fzi.de
> > > >:
> > > >
> > > > > I've recently looked at other ASF projects which discussed
> migration
> > > from
> > > > > Jira to Github, e.g., here are some discussions from Apache Beam:
> > > > >
> > > > > Feature Comparison:
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
> > > > > Migration Plan:
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv
> > > > >
> > > > > And Beam also open-sourced the migration tool they used:
> > > > > https://github.com/google/jira-to-issues
> > > > >
> > > > > I've not yet tried it, but looks quite good 😉
> > > > >
> > > > > Cheers
> > > > > Dominik
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > Sent: Monday, October 31, 2022 6:41 PM
> > > > > To: dev@plc4x.apache.org
> > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > >
> > > > > I will look into that.
> > > > >
> > > > > Currently we have 103 open jira issues. Oldest one is more than 2
> > years
> > > > > ago.
> > > > >
> > > > >
> > > > >
> > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz <
> > > > > christofer.dutz@c-ware.de>:
> > > > >
> > > > > > I’m also fine with that.
> > > > > > So anyone willing to work on the migration?
> > > > > >
> > > > > > Chris
> > > > > >
> > > > > > From: Lukas Ott <ot...@gmail.com>
> > > > > > Date: Monday, 31. October 2022 at 17:50
> > > > > > To: dev@plc4x.apache.org <de...@plc4x.apache.org>
> > > > > > Subject: Re: [DISCUSS] Enable GitHub issues?
> > > > > > Hi Chris,
> > > > > >
> > > > > > In my humble opinion we should not run parallel.
> > > > > >
> > > > > > Our Jira has already a lot of issues that are outdated.
> > > > > >
> > > > > > So i opt for enabling GitHub Issues and migrating the few Jira
> > Issues
> > > > > > that are still worked on.
> > > > > >
> > > > > > This helps us also for cleaning up and having one public issue
> > > > > > tracker, where everyone can easily see what is worked on and what
> > is
> > > > > open.
> > > > > >
> > > > > > Luk
> > > > > >
> > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz <
> > > > > > christofer.dutz@c-ware.de>:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > for those of you that haven’t heard of it, Apache will be
> > disabling
> > > > > > signup
> > > > > > > to Apache’s Jira due to excessive Spam problems.
> > > > > > > So, for people outside of the project, wanting to submit
> issues,
> > > > > > > there will be no simple way to do so.
> > > > > > >
> > > > > > > How about we turn on GitHub Issues and simply run both in
> > parallel.
> > > > > > >
> > > > > > > Chris
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>