Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Yann Ylavic
On Fri, Oct 9, 2015 at 12:21 PM, Rainer Jung wrote: > > Or send GH mails to bugs@ similar to the BZ workflow? Looks like good (and simple) way to have even further contributors (which is never bad). Daniel seems to say it's quite easy to do at infra level (including two-way integration, i.e. repl

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Mads Toftum
On Fri, Oct 09, 2015 at 01:00:22PM +0200, Yann Ylavic wrote: > On Fri, Oct 9, 2015 at 12:52 PM, Mads Toftum wrote: > > On Fri, Oct 09, 2015 at 12:42:44PM +0200, Yann Ylavic wrote: > >> On Fri, Oct 9, 2015 at 12:21 PM, Rainer Jung > >> wrote: > >> > > >> > Or send GH mails to bugs@ similar to the

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Yann Ylavic
On Fri, Oct 9, 2015 at 12:52 PM, Mads Toftum wrote: > On Fri, Oct 09, 2015 at 12:42:44PM +0200, Yann Ylavic wrote: >> On Fri, Oct 9, 2015 at 12:21 PM, Rainer Jung wrote: >> > >> > Or send GH mails to bugs@ similar to the BZ workflow? >> >> That would be equally valuable, and probably simpler. > >

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Mads Toftum
On Fri, Oct 09, 2015 at 12:42:44PM +0200, Yann Ylavic wrote: > On Fri, Oct 9, 2015 at 12:21 PM, Rainer Jung wrote: > > > > Or send GH mails to bugs@ similar to the BZ workflow? > > That would be equally valuable, and probably simpler. And less noisy for those who would rather avoid the automated

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Yann Ylavic
On Fri, Oct 9, 2015 at 12:21 PM, Rainer Jung wrote: > > Or send GH mails to bugs@ similar to the BZ workflow? That would be equally valuable, and probably simpler.

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Yann Ylavic
On Fri, Oct 9, 2015 at 11:50 AM, Daniel Gruno wrote: > On 10/09/2015 11:12 AM, Yann Ylavic wrote: >> Could they somehow be sent to dev@, or is there legal issues? >> > No, nothing legal there... ISTM that for patches to be donated-to/acceptable-by the ASF, they must be sent to either bugs@ or dev

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Rainer Jung
Am 09.10.2015 um 12:00 schrieb Nick Kew: On Fri, 2015-10-09 at 11:12 +0200, Yann Ylavic wrote: Could they somehow be sent to dev@, or is there legal issues? Bugzilla activity doesn't get sent to dev@, even when it involves PatchAvailable (kind-of equivalent to a Pull Request, yesno)? If we we

AW: GitHub (mirror) pull requests notifications

2015-10-09 Thread Plüm , Rüdiger , Vodafone Group
> -Ursprüngliche Nachricht- > Von: Nick Kew [mailto:n...@webthing.com] > Gesendet: Freitag, 9. Oktober 2015 12:01 > An: dev@httpd.apache.org > Betreff: Re: GitHub (mirror) pull requests notifications > > On Fri, 2015-10-09 at 11:12 +0200, Yann Ylavic wrote: >

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Nick Kew
On Fri, 2015-10-09 at 11:12 +0200, Yann Ylavic wrote: > Could they somehow be sent to dev@, or is there legal issues? Bugzilla activity doesn't get sent to dev@, even when it involves PatchAvailable (kind-of equivalent to a Pull Request, yesno)? If we were to propagate pull requests, we should pe

Re: GitHub (mirror) pull requests notifications

2015-10-09 Thread Daniel Gruno
On 10/09/2015 11:12 AM, Yann Ylavic wrote: > Could they somehow be sent to dev@, or is there legal issues? > No, nothing legal there...just that people didn't want GH integration ;) If there's a desire to have it enabled, we can make it so.. With regards, Daniel.

GitHub (mirror) pull requests notifications

2015-10-09 Thread Yann Ylavic
Could they somehow be sent to dev@, or is there legal issues?