Daniel, To subscribe "commits list", you can follow the same step like subscribe to DEV DL (drop a message to [email protected]). 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 <[email protected]> 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:[email protected]] > Sent: Friday, March 11, 2016 12:36 AM > To: [email protected] > 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 <[email protected]> > 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 >
