Agreed, I think we need to have this as a topic in that meeting.
I think there are two parts of this topic:
1. Do we want to allow both Jira and Github issues to coexist in the
Jenkins infrastructure?
1. This is _somewhat_ moot at this point because we already have a
large number of repos that have Github Issues enabled already.
2. If we want to allow both, do we need to clean up the Jira
components of those plugins that are using Github Issues by
providing a way
to migrate issues from Jira to Github Issues and then removing the
component? Also, the opposite, if the plugin developers want to use Jira
but Github Issues was enabled on their repository without them wanting it
enabled (this could have happened for many reasons), do we need
to cleanup
the Github Issues and provide a way to migrate issues from
Github Issues to
Jira?
2. Do we want to adjust the hosting process to allow selection of the
issue tracking (Github Issues or Jira)?
1. This would mean that the hosting bot would check that field and
either:
1. Create a component in Jira and disable GitHub issues for the
repo (this does not preclude the plugin developers team members from
re-enabling GitHub Issues after the fact)
2. No creation of a component in Jira and GitHub issues are NOT
disabled
Am I missing anything from this thread?
On Thu, Jun 18, 2020 at 11:12 AM Ullrich Hafner <ullrich.haf...@gmail.com>
wrote:
>
> > Am 18.06.2020 um 19:48 schrieb 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com>:
> >
> > > Puh, that is a lot. That means we already cerated a mess for our users
> by providing two different tools for the same thing :-(
> >
> > Which is why I want to know what and how we want to support things
> officially so I can add it to the plugin site.
> >
>
> Wouldn’t it then make sense that the people who want officially support
> GitHub as a second issue tracker would make that an agenda topic for the
> next governance meeting?
> So we can finally come to an official statement? Otherwise this thread
> will continue indefinitely.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/EFE72EBF-2AD3-4F12-9879-8A3864CD643D%40gmail.com
> .
>
--
Website: http://earl-of-code.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVek7hYzQAYSUa_sMN9nvpL7hhMKsH7w2ETd1sUrF4zG4Q%40mail.gmail.com.
