[Bro-Dev] Moving to GitHub?
johanna at icir.org
Fri May 18 09:37:51 PDT 2018
I am also more in favor of starting clean and manually letting people
move tickets that they think are important over.
But - currently there is a lot in the tracker that are nice to have or
potential problems that I do not ever see getting addressed.
On 18 May 2018, at 9:17, Slagell, Adam J wrote:
> On May 18, 2018, at 11:11 AM, Robin Sommer
> <robin at icir.org<mailto:robin at icir.org>> wrote:
> What I was envisioning is more or less a clean slate: we'd migrate
> over a few tickets, but essentially we'd start with an empty list. I
> realize that sounds pretty harsh. However, I hardly ever see any
> activity on older tickets in JIRA, and I generally believe that the
> less open tickets a tracker has, the easier it is for people to
> understand what's actually relevant and worth spending cycles on.
> Tagging tickets may help, but in the end if everybody just filters 95%
> out all the time anyways, I'm not sure what the value is.
> That said, I'm open to a real porting effort if people do believe it's
> helpful to get all the JIRA tickets into GitHub. What do others think?
> Start clean for BIT. Unless it is marked critical, I don’t think it
> needs to go over. If people have tickets of their own they want to
> move over, it should not be too hard to manually recreate a couple.
> And after BroCon I think we kill the Jira and wiki completely. We
> should be done with the project management and event tickets by then.
> Adam J. Slagell
> Director, Cybersecurity & Networking Division
> Chief Information Security Officer
> National Center for Supercomputing Applications
> University of Illinois at Urbana-Champaign
> "Under the Illinois Freedom of Information Act (FOIA), any written
> communication to or from University employees regarding University
> business is a public record and may be subject to public disclosure."
> bro-dev mailing list
> bro-dev at bro.org
More information about the bro-dev