Skip to Content.
Sympa Menu

phys-npps-mgmt-l - Re: [Phys-npps-mgmt-l] ROOT: Jira -> GitHub

phys-npps-mgmt-l AT lists.bnl.gov

Subject: NPPS Leadership Team

List archive

Chronological Thread  
  • From: Brett Viren <bv AT bnl.gov>
  • To: Torre Wenaus via Phys-npps-mgmt-l <phys-npps-mgmt-l AT lists.bnl.gov>
  • Subject: Re: [Phys-npps-mgmt-l] ROOT: Jira -> GitHub
  • Date: Thu, 10 Sep 2020 12:35:10 -0400

Torre Wenaus via Phys-npps-mgmt-l <phys-npps-mgmt-l AT lists.bnl.gov>
writes:

> Interesting! Thanks Brett. Maybe a good approach to use github issues
> in the software community and let the detector designer builders et al
> deal with Jira.

Absolutely. I didn't mean to imply pursuing any particular changes or
restrictions on any group. Just that ROOT's move and reasoning may be
worth considering in any selection process. I think the "friction"
metric is particularly worth applying to any option.

> Given that our website(s) and doc are github based,
> probably pretty much everything we deal with can be associated with
> github content. ATLAS recently jumped through complicated hoops to
> enable Jira to serve as an issue/improvement tracking tool for wiki
> based website/doc, with it all in github it's trivial.

Another example: DUNE has just recently announced a "glossary" project
which collects our "terms of art" and from which we can derive LaTeX and
WWW definition lists. It uses GH Issues as one channel for feeding
updates.

https://abc.dunescience.org/
https://github.com/dune/abcdune

-Brett.

Attachment: signature.asc
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page