Re: [Groovy] Next steps...

2015-03-25 Thread Guillaume Laforge
For JIRA, can you import our JIRA from Codehaus? http://jira.codehaus.org/browse/GROOVY On Thu, Mar 26, 2015 at 1:31 AM, Emmanuel Lécharny wrote: > Le 26/03/15 01:01, Konstantin Boudnik a écrit : > > I have just helped bootstrapping two podlings in the last a couple of > months, > > so I will ad

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Mattmann, Chris A (3980)
Henry, Do you have time to be a mentor for the project? We could use your help! :) Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasa

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Mattmann, Chris A (3980)
Dear Greg, Please add your name to the mentor list! :) Would appreciate your help! Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasa

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Mattmann, Chris A (3980)
Dear Henry, That’s an omission - I will update the proposal to include them. Sorry about that! Lei, there aren’t any objections to that correct? Cheers, Chris ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Scienc

Re: [Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Le 26/03/15 01:01, Konstantin Boudnik a écrit : > I have just helped bootstrapping two podlings in the last a couple of months, > so I will add JIRAs to do the what needs to be done from the INFRA side of the > things. Here is the Infra JIRA : https://issues.apache.org/jira/browse/INFRA-9338 As

Re: [Groovy] Next steps...

2015-03-25 Thread Konstantin Boudnik
I have just helped bootstrapping two podlings in the last a couple of months, so I will add JIRAs to do the what needs to be done from the INFRA side of the things. Cos I On Wed, Mar 25, 2015 at 05:02PM, Emmanuel Lécharny wrote: > Hi guys, > > ok, the vote result is out, groovy has been accepte

Re: [Groovy] Next steps...

2015-03-25 Thread Konstantin Boudnik
+1 - esp. for private@ list On Wed, Mar 25, 2015 at 09:57AM, Ted Dunning wrote: > I usually start with mentor moderation and try to transition quickly to > committers. > > > > On Wed, Mar 25, 2015 at 9:56 AM, Jake Farrell wrote: > > > depends, if its private@ the mods control the subscription

Re: [Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Le 25/03/15 22:23, Bertrand Delacretaz a écrit : > On Wed, Mar 25, 2015 at 7:54 PM, Emmanuel Lécharny > wrote: >> ...I'm currently fighting to get the groovy page to appears in the >> incubator web site, I'm not lucky atm. > I just published > > http://incubator.apache.org/projects/groovy.htm

Re: [Groovy] Next steps...

2015-03-25 Thread Guillaume Laforge
The "old" Codehaus website on groovy.codehaus.org has been misbehaving and showing only 404. So I redirected all the trafic to the new website groovy-lang.org. But you if you're searching about the lists, details are here on the new site: http://www.groovy-lang.org/mailing-lists.html Guillaume O

Re: [Groovy] Next steps...

2015-03-25 Thread Bertrand Delacretaz
On Wed, Mar 25, 2015 at 10:26 PM, John D. Ament wrote: >>... Hope you don't mind, I just fixed Roman's name Thanks! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail

Re: [Groovy] Next steps...

2015-03-25 Thread John D. Ament
On Wed, Mar 25, 2015 at 5:23 PM Bertrand Delacretaz wrote: > On Wed, Mar 25, 2015 at 7:54 PM, Emmanuel Lécharny > wrote: > > ...I'm currently fighting to get the groovy page to appears in the > > incubator web site, I'm not lucky atm. > > I just published > > http://incubator.apache.org/proj

Re: [Groovy] Next steps...

2015-03-25 Thread Bertrand Delacretaz
On Wed, Mar 25, 2015 at 7:54 PM, Emmanuel Lécharny wrote: > ...I'm currently fighting to get the groovy page to appears in the > incubator web site, I'm not lucky atm. I just published http://incubator.apache.org/projects/groovy.html via https://cms.apache.org/incubator/publish?diff=1 -Be

Re: [Groovy] Next steps...

2015-03-25 Thread Steve Loughran
would be good to get hold of groovy.codehaus.org. I was unable to find out anything about using lists yesterday... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@i

Re: [Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Le 25/03/15 20:00, Roman Shaposhnik a écrit : > On Wed, Mar 25, 2015 at 9:24 AM, Bertrand Delacretaz > wrote: >>> ...Another question : who is in charge of all those tasks ?.. >> If you could create tickets like the >> https://issues.apache.org/jira/browse/INFRA-8968 example that would >> enable o

Re: [Groovy] Next steps...

2015-03-25 Thread Roman Shaposhnik
On Wed, Mar 25, 2015 at 9:24 AM, Bertrand Delacretaz wrote: >> ...Another question : who is in charge of all those tasks ?.. > > If you could create tickets like the > https://issues.apache.org/jira/browse/INFRA-8968 example that would > enable our infra team to get started. Great example. Do we

Re: [Groovy] Next steps...

2015-03-25 Thread Roman Shaposhnik
On Wed, Mar 25, 2015 at 11:42 AM, Jake Farrell wrote: > podlings do not appear in the acreq script until they have been added to > podlings.xml, even if they file their ICLA with initial committer as part > of groovy. > > secretary@ needs to get the grant before we can import the code That's the

Re: [Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Le 25/03/15 19:42, Jake Farrell a écrit : > podlings do not appear in the acreq script until they have been added to > podlings.xml, even if they file their ICLA with initial committer as part > of groovy. It has been added in podlings.xml. I'm currently fighting to get the groovy page to appears

Re: [Groovy] Next steps...

2015-03-25 Thread Jake Farrell
podlings do not appear in the acreq script until they have been added to podlings.xml, even if they file their ICLA with initial committer as part of groovy. secretary@ needs to get the grant before we can import the code -Jake On Wed, Mar 25, 2015 at 1:29 PM, John D. Ament wrote: > On Wed, Ma

Re: [Groovy] Next steps...

2015-03-25 Thread John D. Ament
On Wed, Mar 25, 2015 at 1:24 PM Emmanuel Lécharny wrote: > Technically, I just added two moderators. We can add some more, I guess. > > One more thing : in order to add initial committers, the pdofling must > be listed in https://id.apache.org/acreq/members/?. How do we add it ? > > The ICLAs for

Re: [Groovy] Next steps...

2015-03-25 Thread Jake Farrell
you need to setup the podling in podlings.xml at [1] and update the incubator website -Jake [1]: https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml On Wed, Mar 25, 2015 at 1:23 PM, Emmanuel Lécharny wrote: > Technically, I just added two moderators. We can add some m

Re: [Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Technically, I just added two moderators. We can add some more, I guess. One more thing : in order to add initial committers, the pdofling must be listed in https://id.apache.org/acreq/members/?. How do we add it ? - To unsubscr

Re: [Groovy] Next steps...

2015-03-25 Thread Bertrand Delacretaz
On Wed, Mar 25, 2015 at 6:00 PM, David Nalley wrote: > it's not like we are limited to having just a few moderators. Nothing > wrong with mentors and initial committers both being on the list of > mods... Especially when those non-mentor moderators are experienced open source folks like in the Gr

Re: [Groovy] Next steps...

2015-03-25 Thread David Nalley
it's not like we are limited to having just a few moderators. Nothing wrong with mentors and initial committers both being on the list of mods. On Wed, Mar 25, 2015 at 12:57 PM, Ted Dunning wrote: > I usually start with mentor moderation and try to transition quickly to > committers. > > > > On W

Re: [Groovy] Next steps...

2015-03-25 Thread Jim Jagielski
+1 > On Mar 25, 2015, at 12:56 PM, Jake Farrell wrote: > > depends, if its private@ the mods control the subscription > > -Jake > > On Wed, Mar 25, 2015 at 12:52 PM, Marvin Humphrey > wrote: > >> On Wed, Mar 25, 2015 at 9:44 AM, John D. Ament >> wrote: >>> On that note, interesting thing, ju

Re: [Groovy] Next steps...

2015-03-25 Thread Ted Dunning
I usually start with mentor moderation and try to transition quickly to committers. On Wed, Mar 25, 2015 at 9:56 AM, Jake Farrell wrote: > depends, if its private@ the mods control the subscription > > -Jake > > On Wed, Mar 25, 2015 at 12:52 PM, Marvin Humphrey > wrote: > > > On Wed, Mar 25,

Re: [Groovy] Next steps...

2015-03-25 Thread Jake Farrell
depends, if its private@ the mods control the subscription -Jake On Wed, Mar 25, 2015 at 12:52 PM, Marvin Humphrey wrote: > On Wed, Mar 25, 2015 at 9:44 AM, John D. Ament > wrote: > > On that note, interesting thing, just saw the commit go in for infra to > > create the mailing lists. Are we

Re: [Groovy] Next steps...

2015-03-25 Thread Jake Farrell
Should just be the mentors to start with and not any of the new committers that are not familiar with processes -Jake On Wed, Mar 25, 2015 at 12:44 PM, John D. Ament wrote: > On that note, interesting thing, just saw the commit go in for infra to > create the mailing lists. Are we really allow

Re: [Groovy] Next steps...

2015-03-25 Thread Marvin Humphrey
On Wed, Mar 25, 2015 at 9:44 AM, John D. Ament wrote: > On that note, interesting thing, just saw the commit go in for infra to > create the mailing lists. Are we really allowing new committers to be the > mods? It's typically the mentors (from what I've seen). Definitely having committers serve

Re: [Groovy] Next steps...

2015-03-25 Thread John D. Ament
On that note, interesting thing, just saw the commit go in for infra to create the mailing lists. Are we really allowing new committers to be the mods? It's typically the mentors (from what I've seen). John On Wed, Mar 25, 2015 at 12:34 PM Marvin Humphrey wrote: > On Wed, Mar 25, 2015 at 9:02

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Greg Reddin
On Mon, Mar 23, 2015 at 12:55 AM, Mattmann, Chris A (3980) wrote: > We are actively soliciting interested mentors in this project related to > climate > science and analytics and big data. I'm very interested in this project. I'd like to help mentor it. Any objections? Greg ---

Re: [Groovy] Next steps...

2015-03-25 Thread Marvin Humphrey
On Wed, Mar 25, 2015 at 9:02 AM, Emmanuel Lécharny wrote: > I most certainly am missing some steps... Feel free to add items. > > Another question : who is in charge of all those tasks ? The podling's Mentors, collectively. See the Mentor Guide: http://incubator.apache.org/guides/mentor.html

Re: [Groovy] Next steps...

2015-03-25 Thread Bertrand Delacretaz
Hi, On Wed, Mar 25, 2015 at 5:02 PM, Emmanuel Lécharny wrote: > ...- vote the 5 proposed persons as committers, once they have submitted > their ICLA (it's already done for a few of them).. The iCLAs are needed but no need to vote them in, we just create their accounts - the podling acceptance v

[Groovy] Next steps...

2015-03-25 Thread Emmanuel Lécharny
Hi guys, ok, the vote result is out, groovy has been accepted. I suppose the next steps are : - vote the 5 proposed persons as committers, once they have submitted their ICLA (it's already done for a few of them) - create groovy ML (dev, commits, users, private, ...) - create the git repo - push t

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Henry Saputra
HI Chris, Great proposal. Looks like the people from CMU are excluded from list of initial committers? They are mentioned in the affiliations section but not in the committers section. - Henry On Sun, Mar 22, 2015 at 10:55 PM, Mattmann, Chris A (3980) wrote: > Hi Everyone, > > I am pleased to

Re: [PROPOSAL] Climate Model Diagnostic Analyzer

2015-03-25 Thread Pan, Lei (398K)
Hi Ted: We need a server to host the document before we can delete the URL to the web services. So I updated the URL in the proposal to: http://cmacws4.jpl.nasa.gov:8080/cmac/ Thanks, -Lei From: Ted Dunning mailto:ted.dunn...@gmail.com>> Date: Monday, March 23, 2015 at 11:32 PM To: JPL mailto:le