+1, I agree with Neil and believe Apache NetBeans would benefit from transitioning to what Airflow has done.
If we continue to use Jira, these changes might help some: 1. As Eric suggested, enable autolink for Jira issues. https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources 2. Turn on more Jira automations like transition an issue once a PR has been merged. (I don't think this is currently enabled) https://www.atlassian.com/software/jira/automation-template-library/bitbucket-github-gitlab --Christian On Fri, Nov 12, 2021 at 6:24 AM Michael Bien <[email protected]> wrote: > On 11.11.21 16:54, Eric Bresie wrote: > > I've been following the openjdk side and they continue to have multiple > > tracking systems which in that context is also burdensome but I believe > > part of that is driven by the organization management side (have an > > "official system of record for issues", have a secondary one on github > > which still has to be linked up with each other). However, I noticed in > PR > > discussion some "switches" that can be added to the discussions to > trigger > > automatic things like or set state like request reviews, set milestones, > > etc. How much of that is present in our current workflow? > > OpenJDK is using skara which was specifically written to integrate > github with the existing OpenJDK workflow which was traditionally on > mailing lists. Without an issue filed and linked to a PR or a > contributor agreement signed, a PR won't even appear on the mailing list. > > This can be a high barrier for external contributors and small fixes, > since an issue can be only filed if you find a sponsor or file a bug > hoping that it might transition to an issue (i went through that). > > The slash commands are from skara. > > https://github.com/openjdk/skara > > this would be overkill for NB. But simple configurations, like for > examples flags in PR text which trigger extra build actions, would be an > option IMO. > > -michael > > > > > > Eric Bresie > > [email protected] > > > > > > On Thu, Nov 11, 2021 at 9:44 AM Eric Bresie <[email protected]> wrote: > > > >> Eric Bresie > >> [email protected] > >> > >> > >> On Thu, Nov 11, 2021 at 9:08 AM Neil C Smith <[email protected]> > >> wrote: > >> > >>> On Thu, 11 Nov 2021 at 14:55, Eric Bresie <[email protected]> wrote: > >>> > >>>> - Repository admins accept content reports > >>> Interesting. Maybe. What does the last one mean exactly?! > >>> > >>> Have to confess I don't know since I'm not an admin :-) but I'm > guessing > >> it has to do with reporting abuse of some kind for the given repository > >> > >> > >> > https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
