Slightly separate sub-topic but while on the Apache/Netbeans Github repository site I noticed the Insite tab (see https://github.com/apache/netbeans/pulse ) which seems to provide some similar reports like those generated in JIRA as mentioned previously.
One sub-selections was how things align with "community" standards (see https://github.com/apache/netbeans/community ) It seems like have green checks on all of these but the following - Issue templates - Pull request template - Repository admins accept content reports - Assume since Issues are not presently in use that probably explains the Issue template, but do the other items need to be considered? Eric Bresie [email protected] Eric Bresie [email protected] On Thu, Nov 11, 2021 at 8:35 AM Eric Bresie <[email protected]> wrote: > Not sure if this would help in integration between existing systems but is > "autolink" enabled on github to ease references to NETBEANS JIRA tickets? > If not and the github product (pro, enterprise, etc.) in use allows its use > but if it does, it seems like it might help a little to put in a ticket > reference which automatically links to the JIRA ticket. > > For more see > https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources > > Assume if setup with a prefix of NETBEANS pointing to a URL something like > https://issues.apache.org/jira/browse/NETBEANS-<num> then references > starting with NETBEANS may automatically link up. > > That does assume a ticket exists to do so. > > Eric Bresie > [email protected] > > > On Wed, Nov 10, 2021 at 11:58 AM Neil C Smith <[email protected]> > wrote: > >> On Mon, 27 Sept 2021 at 18:54, Neil C Smith <[email protected]> >> wrote: >> > There's also the possibility some >> > of this will end up revised on a wiki page around GitHub best >> > practices across ASF ... >> >> So, reviving this thread. That wiki page from Jarek did come about >> btw, and is public access - >> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632 >> >> Working on the 12.6 release is reminding how much I hate working with >> JIRA as we have it set up right now. Either we need to improve how >> we're using it, or we need to migrate - and I'm very much in the >> latter camp! Something needs to improve, or I feel sorry for whoever >> is leading on the next release process (not me!) :-) >> >> The lack of useful synchronization between PRs and issues needs >> addressing. The lack of linking, including conversations, milestones, >> statuses, users, issue existence(!), etc. is massive duplicate effort. >> >> Eric did a great job putting this page together >> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+12.6 >> But the fact that we have two different change records, that we don't >> have JIRA tickets for half the changes, and that half of those are >> tickets created to link the PR to, is again a load of duplication. >> >> Either way we also need templates for users to fill out, and to remove >> access to things like priorities, and more eyes on the incoming ... >> and ... >> >> OK, rant over! :-) Frustration at play. I like Airflow's approach >> linked above, but maybe we can do other things. But let's fix this >> somehow before NB13! >> >> Best wishes, >> >> Neil >> >> --------------------------------------------------------------------- >> 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 >> >> >> >>
