This has been coming up in various contexts & subgroups of people, and
I wanted to send it out as a proposal to gather some broader feedback:
Do we want to move Bro's git repositories and tickets to GitHub?
Currently we're hosting our Git repositories on our own server at
git.bro.org; from there,
> What do people think? Any support, or concerns?
I am in favor. The only thing I would miss are the immediate change
notifications by email - I really like those...
Johanna
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mail
I am in favor. I would like to still maintain the the Jira and wiki for a
couple months until we finish up some work. Really just the BPM tickets.
> On May 15, 2018, at 7:19 PM, Robin Sommer wrote:
>
> This has been coming up in various contexts & subgroups of people, and
> I wanted to send it
Big thumbs up.
On May 15, 2018, at 5:34 PM, Johanna Amann wrote:
>> What do people think? Any support, or concerns?
>
> I am in favor. The only thing I would miss are the immediate change
> notifications by email - I really like those...
>
> Johanna
>
I too would miss the commit / change notifications, however, I think that this
can be set up in GitHub in some way. We use Slack / Email internally for commit
notifications. For Slack, we use webhooks to send notifications.
Email commit notifications are actually a builtin integration in GitHub
Well... in looking at how I set this up internally, I now realize that this
feature is being EOL and will no longer work as of January 31, 2019. I guess it
would have to be webhooks.
On 5/16/18, 11:30 AM, "bro-dev-boun...@bro.org on behalf of Hosom, Stephen M"
wrote:
I too would miss the
On Wed, May 16, 2018 at 15:23 +, you wrote:
> I too would miss the commit / change notifications, however, I think
> that this can be set up in GitHub in some way.
We can still get the same email notifications as today (which have a
bit more information that GitHub's standard ones), they wi
On 5/15/18 7:19 PM, Robin Sommer wrote:
> What do people think? Any support, or concerns?
Yeah, generally in favor with some comments:
* For porting over JIRA tickets to GitHub, "most recent" doesn't seem
like a good metric to use. e.g. BIT-1829 (pcap triggering assertion in
binpac) seems ki
On 15 May 2018, at 20:19, Robin Sommer wrote:
> This has been coming up in various contexts & subgroups of people, and
> I wanted to send it out as a proposal to gather some broader feedback:
> Do we want to move Bro's git repositories and tickets to GitHub?
I like the idea. It'll be nice to ha
On Thu, May 17, 2018 at 11:21 -0500, you wrote:
> * For porting over JIRA tickets to GitHub, "most recent" doesn't seem like a
> good metric to use.
Agree. :)
> they may as well just port all the older ones that are still valid
> over to GitHub.
That may be a bit too broad though. How about "
On 5/17/18 6:27 PM, Robin Sommer wrote:
> That may be a bit too broad though. How about "still valid and either
> (1) quite important or (2) something we expect will be addresses
> reasonably soon"? We have many old tickets that are technically still
> valid but unlikely to see any work anytime
On Fri, May 18, 2018 at 08:27 -0500, you wrote:
> Doing a half-hearted effort to migrate tickets from JIRA undermines the goal
> of having an authoritative/central location for all code + tickets. Can we
> instead try to deal with it once and for all?
What I was envisioning is more or less a c
On May 18, 2018, at 11:11 AM, Robin Sommer
mailto:ro...@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 ti
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.
Johanna
On 18 May 2018, at 9:17, Slagell, A
On Fri, May 18, 2018 at 9:12 AM Robin Sommer wrote:
>
>
> 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?
>
Having the historical tickets available are useful for searching to see if
someone else had
On 5/18/18 11:11 AM, Robin Sommer 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 gener
> * Someone is likely to report the same problem again
> * There's clear directions on how to reproduce an undesired behavior
> * There been a proposed plan of action recently
>
> And many tickets can be ruled out:
>
> * Vague feature requests
> * Not enough details / difficult to reproduce
> *
17 matches
Mail list logo