You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by Henry Saputra <he...@gmail.com> on 2016/03/11 07:42:19 UTC
[DISCUSS] Adding new mailing list to contain JIRA and Github updates
Hi All,
With Apache Eagle podling getting more active every day, it seemed like
JIRA updates and Github mirror updates start to become clutter to the dev
list.
I think it is time to introduce new list, typically called issues@ as the
reservoir for the updates.
We will still need to make JIRA create event to be delivered to dev@ for
bookeeping but updates could be redirected to issues@
This is one of the "good" problems to have =)
Let me know what you guys think.
Thanks,
Henry
Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Posted by "Liangfei.Su" <su...@gmail.com>.
+1 to have JIRA create to @dev and updates to @issues.
On Thu, Mar 10, 2016 at 10:42 PM, Henry Saputra <he...@gmail.com>
wrote:
> Hi All,
>
> With Apache Eagle podling getting more active every day, it seemed like
> JIRA updates and Github mirror updates start to become clutter to the dev
> list.
>
> I think it is time to introduce new list, typically called issues@ as the
> reservoir for the updates.
>
> We will still need to make JIRA create event to be delivered to dev@ for
> bookeeping but updates could be redirected to issues@
>
> This is one of the "good" problems to have =)
>
> Let me know what you guys think.
>
> Thanks,
>
> Henry
>
Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Posted by Henry Saputra <he...@gmail.com>.
Ah, we already have issues@ list? Sorry, I missed it.
Yeah, if we have karma to change the notifications that would be great.
- Henry
On Fri, Mar 11, 2016 at 12:33 PM, Edward Zhang <yo...@apache.org>
wrote:
> Understood. I checked we already have issues@ and commits@, but we need
> modify JIRA notifications in the page
>
> https://issues.apache.org/jira/plugins/servlet/project-config/EAGLE/notifications
>
> Looks our mentor Sriramadasu have the permission to modify. We can have
> JIRA ticket created message to be sent to dev@, and have other messages to
> be sent to issues@.
>
> Thanks
>
> Edward
>
> On Fri, Mar 11, 2016 at 12:36 AM, Julian Hyde <jh...@gmail.com>
> wrote:
>
> > +1 on keeping the volume on the list manageable. A project with a high
> > volume list is difficult to contribute to if that project is not your
> main
> > job, and we want to encourage a diversity of contributors.
> >
> > A variation on what Henry is suggesting is to have jira send a message to
> > the dev list only when a jira case is created. Subsequent updates go only
> > to the issues list. But the initial email allows anyone interested to
> press
> > "watch" on a case and receive all further updates for that case.
> >
> > Julian
> >
> > > On Mar 10, 2016, at 10:42 PM, Henry Saputra <he...@gmail.com>
> > wrote:
> > >
> > > Hi All,
> > >
> > > With Apache Eagle podling getting more active every day, it seemed like
> > > JIRA updates and Github mirror updates start to become clutter to the
> dev
> > > list.
> > >
> > > I think it is time to introduce new list, typically called issues@ as
> > the
> > > reservoir for the updates.
> > >
> > > We will still need to make JIRA create event to be delivered to dev@
> for
> > > bookeeping but updates could be redirected to issues@
> > >
> > > This is one of the "good" problems to have =)
> > >
> > > Let me know what you guys think.
> > >
> > > Thanks,
> > >
> > > Henry
> >
>
Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Posted by Edward Zhang <yo...@apache.org>.
Understood. I checked we already have issues@ and commits@, but we need
modify JIRA notifications in the page
https://issues.apache.org/jira/plugins/servlet/project-config/EAGLE/notifications
Looks our mentor Sriramadasu have the permission to modify. We can have
JIRA ticket created message to be sent to dev@, and have other messages to
be sent to issues@.
Thanks
Edward
On Fri, Mar 11, 2016 at 12:36 AM, Julian Hyde <jh...@gmail.com>
wrote:
> +1 on keeping the volume on the list manageable. A project with a high
> volume list is difficult to contribute to if that project is not your main
> job, and we want to encourage a diversity of contributors.
>
> A variation on what Henry is suggesting is to have jira send a message to
> the dev list only when a jira case is created. Subsequent updates go only
> to the issues list. But the initial email allows anyone interested to press
> "watch" on a case and receive all further updates for that case.
>
> Julian
>
> > On Mar 10, 2016, at 10:42 PM, Henry Saputra <he...@gmail.com>
> wrote:
> >
> > Hi All,
> >
> > With Apache Eagle podling getting more active every day, it seemed like
> > JIRA updates and Github mirror updates start to become clutter to the dev
> > list.
> >
> > I think it is time to introduce new list, typically called issues@ as
> the
> > reservoir for the updates.
> >
> > We will still need to make JIRA create event to be delivered to dev@ for
> > bookeeping but updates could be redirected to issues@
> >
> > This is one of the "good" problems to have =)
> >
> > Let me know what you guys think.
> >
> > Thanks,
> >
> > Henry
>
RE: [DISCUSS] Adding new mailing list to contain JIRA and Github
updates
Posted by Daniel Zhou <Da...@dataguise.com>.
Hi Ralph,
Got it, thanks for your explanation. :P
Regards,
Daniel
-----Original Message-----
From: Liangfei.Su [mailto:suliangfei@gmail.com]
Sent: Monday, March 14, 2016 11:46 AM
To: dev@eagle.incubator.apache.org
Subject: Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Daniel,
To subscribe "commits list", you can follow the same step like subscribe to DEV DL (drop a message to commits-subscribe@eagle.incubator.apache.org).
But.
*I think one don't need to be in the commit DL to contribute code to eagle, and the commits DL not mean to grant the commit permission. *
To contribute code, you can
1. Fork eagle project at https://github.com/apache/incubator-eagle/ to your own github account 2. Commit your code in your own fork 3. Send pull request like https://github.com/apache/incubator-eagle/pull/118
Committers would review and merge the code to upstream. This process is stated at https://cwiki.apache.org/confluence/display/EAG/Contributing+to+Eagle#ContributingtoEagle-ContributingCodeChanges.
Does it make sense?
Thanks,
Ralph
On Mon, Mar 14, 2016 at 10:49 AM, Daniel Zhou <Da...@dataguise.com>
wrote:
> Hi, all
>
> Can someone add me to the "commit list"?
> I would like to contribute some code regarding to Ealge's support for
> Mapr :P
>
> Thanks and regards,
> Daniel
>
> -----Original Message-----
> From: Julian Hyde [mailto:jhyde.apache@gmail.com]
> Sent: Friday, March 11, 2016 12:36 AM
> To: dev@eagle.incubator.apache.org
> Subject: Re: [DISCUSS] Adding new mailing list to contain JIRA and
> Github updates
>
> +1 on keeping the volume on the list manageable. A project with a high
> volume list is difficult to contribute to if that project is not your
> main job, and we want to encourage a diversity of contributors.
>
> A variation on what Henry is suggesting is to have jira send a message
> to the dev list only when a jira case is created. Subsequent updates
> go only to the issues list. But the initial email allows anyone
> interested to press "watch" on a case and receive all further updates for that case.
>
> Julian
>
> > On Mar 10, 2016, at 10:42 PM, Henry Saputra
> > <he...@gmail.com>
> wrote:
> >
> > Hi All,
> >
> > With Apache Eagle podling getting more active every day, it seemed
> > like JIRA updates and Github mirror updates start to become clutter
> > to the dev list.
> >
> > I think it is time to introduce new list, typically called issues@
> > as the reservoir for the updates.
> >
> > We will still need to make JIRA create event to be delivered to dev@
> > for bookeeping but updates could be redirected to issues@
> >
> > This is one of the "good" problems to have =)
> >
> > Let me know what you guys think.
> >
> > Thanks,
> >
> > Henry
>
Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Posted by "Liangfei.Su" <su...@gmail.com>.
Daniel,
To subscribe "commits list", you can follow the same step like subscribe to
DEV DL (drop a message to commits-subscribe@eagle.incubator.apache.org).
But.
*I think one don't need to be in the commit DL to contribute code to eagle,
and the commits DL not mean to grant the commit permission. *
To contribute code, you can
1. Fork eagle project at https://github.com/apache/incubator-eagle/ to your
own github account
2. Commit your code in your own fork
3. Send pull request like https://github.com/apache/incubator-eagle/pull/118
Committers would review and merge the code to upstream. This process is
stated at
https://cwiki.apache.org/confluence/display/EAG/Contributing+to+Eagle#ContributingtoEagle-ContributingCodeChanges.
Does it make sense?
Thanks,
Ralph
On Mon, Mar 14, 2016 at 10:49 AM, Daniel Zhou <Da...@dataguise.com>
wrote:
> Hi, all
>
> Can someone add me to the "commit list"?
> I would like to contribute some code regarding to Ealge's support for Mapr
> :P
>
> Thanks and regards,
> Daniel
>
> -----Original Message-----
> From: Julian Hyde [mailto:jhyde.apache@gmail.com]
> Sent: Friday, March 11, 2016 12:36 AM
> To: dev@eagle.incubator.apache.org
> Subject: Re: [DISCUSS] Adding new mailing list to contain JIRA and Github
> updates
>
> +1 on keeping the volume on the list manageable. A project with a high
> volume list is difficult to contribute to if that project is not your main
> job, and we want to encourage a diversity of contributors.
>
> A variation on what Henry is suggesting is to have jira send a message to
> the dev list only when a jira case is created. Subsequent updates go only
> to the issues list. But the initial email allows anyone interested to press
> "watch" on a case and receive all further updates for that case.
>
> Julian
>
> > On Mar 10, 2016, at 10:42 PM, Henry Saputra <he...@gmail.com>
> wrote:
> >
> > Hi All,
> >
> > With Apache Eagle podling getting more active every day, it seemed
> > like JIRA updates and Github mirror updates start to become clutter to
> > the dev list.
> >
> > I think it is time to introduce new list, typically called issues@ as
> > the reservoir for the updates.
> >
> > We will still need to make JIRA create event to be delivered to dev@
> > for bookeeping but updates could be redirected to issues@
> >
> > This is one of the "good" problems to have =)
> >
> > Let me know what you guys think.
> >
> > Thanks,
> >
> > Henry
>
RE: [DISCUSS] Adding new mailing list to contain JIRA and Github
updates
Posted by Daniel Zhou <Da...@dataguise.com>.
Hi, all
Can someone add me to the "commit list"?
I would like to contribute some code regarding to Ealge's support for Mapr :P
Thanks and regards,
Daniel
-----Original Message-----
From: Julian Hyde [mailto:jhyde.apache@gmail.com]
Sent: Friday, March 11, 2016 12:36 AM
To: dev@eagle.incubator.apache.org
Subject: Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
+1 on keeping the volume on the list manageable. A project with a high volume list is difficult to contribute to if that project is not your main job, and we want to encourage a diversity of contributors.
A variation on what Henry is suggesting is to have jira send a message to the dev list only when a jira case is created. Subsequent updates go only to the issues list. But the initial email allows anyone interested to press "watch" on a case and receive all further updates for that case.
Julian
> On Mar 10, 2016, at 10:42 PM, Henry Saputra <he...@gmail.com> wrote:
>
> Hi All,
>
> With Apache Eagle podling getting more active every day, it seemed
> like JIRA updates and Github mirror updates start to become clutter to
> the dev list.
>
> I think it is time to introduce new list, typically called issues@ as
> the reservoir for the updates.
>
> We will still need to make JIRA create event to be delivered to dev@
> for bookeeping but updates could be redirected to issues@
>
> This is one of the "good" problems to have =)
>
> Let me know what you guys think.
>
> Thanks,
>
> Henry
Re: [DISCUSS] Adding new mailing list to contain JIRA and Github updates
Posted by Julian Hyde <jh...@gmail.com>.
+1 on keeping the volume on the list manageable. A project with a high volume list is difficult to contribute to if that project is not your main job, and we want to encourage a diversity of contributors.
A variation on what Henry is suggesting is to have jira send a message to the dev list only when a jira case is created. Subsequent updates go only to the issues list. But the initial email allows anyone interested to press "watch" on a case and receive all further updates for that case.
Julian
> On Mar 10, 2016, at 10:42 PM, Henry Saputra <he...@gmail.com> wrote:
>
> Hi All,
>
> With Apache Eagle podling getting more active every day, it seemed like
> JIRA updates and Github mirror updates start to become clutter to the dev
> list.
>
> I think it is time to introduce new list, typically called issues@ as the
> reservoir for the updates.
>
> We will still need to make JIRA create event to be delivered to dev@ for
> bookeeping but updates could be redirected to issues@
>
> This is one of the "good" problems to have =)
>
> Let me know what you guys think.
>
> Thanks,
>
> Henry