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 <
[email protected]>:

> +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 <[email protected]> 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 <[email protected]
> >:
> >
> > > 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 <[email protected]>
> > > Sent: Monday, October 31, 2022 6:41 PM
> > > To: [email protected]
> > > 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 <
> > > [email protected]>:
> > >
> > > > I’m also fine with that.
> > > > So anyone willing to work on the migration?
> > > >
> > > > Chris
> > > >
> > > > From: Lukas Ott <[email protected]>
> > > > Date: Monday, 31. October 2022 at 17:50
> > > > To: [email protected] <[email protected]>
> > > > 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 <
> > > > [email protected]>:
> > > >
> > > > > 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
> > > > >
> > > >
> > >
> >
>

Reply via email to