Re: my pTLP view
On Mon, Jan 26, 2015 at 8:22 PM, Alex Harui wrote: > ...For Flex, we did not have an established community of developers coming in > with the code. But I don’t know that we could have recruited enough ASF > members to be committers I agree with that, I was a Flex mentor but only interested in the community side of things, I have no technical knowledge and no technical interest in Flex. I think that kind of mentorship is still possible with Greg's pTLP model, but as others have said people who have no technical interest in the project are more likely to become inactive than those who are active committers. In any case, it's fine for people to become inactive in Apache projects so the same has to be true for pTLPs. I guess the board will just have to pay closer attention to those projects, considering them more "fragile" than well-established TLPs maybe. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: my pTLP view
On Mon, Jan 26, 2015 at 7:09 PM, Alan D. Cabrera wrote: > ...- do away w/ the pTLP name, just make it a regular TLP... I don't like that, IMO pTLPs have to be explicitly flagged, to make sure both users and Apache folks are aware of their "immaturity". -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[IP CLEARANCE] CouchDB Mango
Dear Incubator, On behalf of the CouchDB project, I’m requesting IP Clearance for the CouchDB Mango contribution: https://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/couchdb-mango.xml?view=markup Thank you! Best Jan -- signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [DISCUSS] Solicitation for IPMC Chair nomination
+1 for Ted Dunning and Henry Saputra Both are mentors of Apache Kylin and such fantastic mentors they areŠ Regards Seshu Adunuthula On 1/26/15, 11:16 AM, "Marvin Humphrey" wrote: >+1 for Ted Dunning. > >Ted has passion for the Incubator's mission. He is an excellent consensus >builder, with the right mix of patience and advocacy. He can get the job >done >while sending judicious amounts of email, which is important in keeping >traffic on general@incubator under control. He is politically adept and >tough >enough to handle the challenges of interfacing with the Board and with >outside >organizations. If he will take the job, the Incubator would be lucky to >have >him. > >FWIW, I don't have the expectation that Ted or any other Chair will *lead* >reform -- Apache Chairs are not executives. But if Ted chooses to be >be an active moderator, I have faith that he will do as well as anyone >could >in guiding consensus for whatever bottom-up proposals emerge. > >Marvin Humphrey > >On Mon, Jan 26, 2015 at 10:45 AM, Roman Shaposhnik wrote: >> Hi! >> >> after making sure that there's still an Incubator >> to be managed for the next 6-12 months, I'd like >> to open up a discussion thread on soliciting >> nominations for the next IPMC Chair. >> >> Feel free to self-nominate or nominate folks who >> you know. Provide a summary of your 'program' >> or not. At this point, we want as much feedback >> and discussion as possible. The VOTE thread will >> come in a few weeks. >> >> Things to keep in mind while thinking about nominating >> yourself or others: >>1. This is a 6-12 months commitment that, based on my >> personal experience, would require you to allocate 7-10 >> hours per week. >> >> 2. This is a rotating Chair and you would be expected to >> start a similar thread in 12 months. >> >> 3. From where I sit, the most important job for the new >> Chair for the next few months would be to help shape >> the incremental, actionable plan for improving the >> mentoring situation in the Incubator. >> >> 4. The situation around 'professional student' podlings >> is not improving nearly quick enough (4 years without >> a single release? really?). Anybody who has actionable >> ideas on how to improve it would get my support. >> >> Now, to get the ball rolling, here are the two folks I'd >> like to suggest as future IPMC Chairs: >> * Ted Dunning >> * Henry Saputra >> In my view, both have demonstrated an exceptional >> understanding of the 'Apache Way', dedication to >> mentoring podlings they are responsible for and enthusiasm >> around bringing new communities into the ASF family. >> On top of that, both have exercised a remarkable skill >> in conducting public discussions and driving towards >> consensus. >> >> Thanks, >> Roman. >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > >- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: my pTLP view
> On Jan 27, 2015, at 12:31 AM, Bertrand Delacretaz > wrote: > > On Mon, Jan 26, 2015 at 7:09 PM, Alan D. Cabrera wrote: >> ...- do away w/ the pTLP name, just make it a regular TLP... > > I don't like that, IMO pTLPs have to be explicitly flagged, to make > sure both users and Apache folks are aware of their "immaturity". I had considered that. What I was thinking was that what ever specific concerns there can be for the pTLP also apply to a mature TLP. Having various “profiles” that apply to projects can provide a finer degree of visibility. To be sure every project has its nuances and some will be exceptionally unusual, but those will already be on the board’s “radar”. In short, the pTLP designation is a bit too opaque. Anyway, that’s what I was thinking. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Solicitation for IPMC Chair nomination
+1 for Ted Dunning and Henry Saputra They both are very actively helping Kylin incubating from the beginning. Their passion, professional and experience brings great value for our incubator project. With their very nice coach, all of us gained a lot of from them, especially about run open source community which is more important than coding itself. Thanks Luke 2015-01-27 22:12 GMT+08:00 Adunuthula, Seshu : > +1 for Ted Dunning and Henry Saputra > > Both are mentors of Apache Kylin and such fantastic mentors they areŠ > > Regards > Seshu Adunuthula > > > On 1/26/15, 11:16 AM, "Marvin Humphrey" wrote: > > >+1 for Ted Dunning. > > > >Ted has passion for the Incubator's mission. He is an excellent consensus > >builder, with the right mix of patience and advocacy. He can get the job > >done > >while sending judicious amounts of email, which is important in keeping > >traffic on general@incubator under control. He is politically adept and > >tough > >enough to handle the challenges of interfacing with the Board and with > >outside > >organizations. If he will take the job, the Incubator would be lucky to > >have > >him. > > > >FWIW, I don't have the expectation that Ted or any other Chair will *lead* > >reform -- Apache Chairs are not executives. But if Ted chooses to be > >be an active moderator, I have faith that he will do as well as anyone > >could > >in guiding consensus for whatever bottom-up proposals emerge. > > > >Marvin Humphrey > > > >On Mon, Jan 26, 2015 at 10:45 AM, Roman Shaposhnik > wrote: > >> Hi! > >> > >> after making sure that there's still an Incubator > >> to be managed for the next 6-12 months, I'd like > >> to open up a discussion thread on soliciting > >> nominations for the next IPMC Chair. > >> > >> Feel free to self-nominate or nominate folks who > >> you know. Provide a summary of your 'program' > >> or not. At this point, we want as much feedback > >> and discussion as possible. The VOTE thread will > >> come in a few weeks. > >> > >> Things to keep in mind while thinking about nominating > >> yourself or others: > >>1. This is a 6-12 months commitment that, based on my > >> personal experience, would require you to allocate 7-10 > >> hours per week. > >> > >> 2. This is a rotating Chair and you would be expected to > >> start a similar thread in 12 months. > >> > >> 3. From where I sit, the most important job for the new > >> Chair for the next few months would be to help shape > >> the incremental, actionable plan for improving the > >> mentoring situation in the Incubator. > >> > >> 4. The situation around 'professional student' podlings > >> is not improving nearly quick enough (4 years without > >> a single release? really?). Anybody who has actionable > >> ideas on how to improve it would get my support. > >> > >> Now, to get the ball rolling, here are the two folks I'd > >> like to suggest as future IPMC Chairs: > >> * Ted Dunning > >> * Henry Saputra > >> In my view, both have demonstrated an exceptional > >> understanding of the 'Apache Way', dedication to > >> mentoring podlings they are responsible for and enthusiasm > >> around bringing new communities into the ASF family. > >> On top of that, both have exercised a remarkable skill > >> in conducting public discussions and driving towards > >> consensus. > >> > >> Thanks, > >> Roman. > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > > >- > >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! - Luke Han
Re: my pTLP view
On Tue, Jan 27, 2015 at 3:38 PM, Alan D. Cabrera wrote: > In short, the pTLP designation is a bit too opaque So you mean all TLPs should have status labels? Might be useful...probatory, active, low activity, attic candidate...why not. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: my pTLP view
> On Jan 27, 2015, at 6:58 AM, Bertrand Delacretaz > wrote: > > On Tue, Jan 27, 2015 at 3:38 PM, Alan D. Cabrera wrote: >> In short, the pTLP designation is a bit too opaque > > So you mean all TLPs should have status labels? > > Might be useful...probatory, active, low activity, attic candidate...why not. Yeah, these coupled w/ ComDev’s maturity model would help people grok at a glance what’s generally going on w/ the project instead of being forced to go on an easter egg hunt through Jira issues, mailing lists, and commit logs, to try to access the general character of a project. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: my pTLP view
On Tue, Jan 27, 2015 at 6:58 AM, Bertrand Delacretaz wrote: > On Tue, Jan 27, 2015 at 3:38 PM, Alan D. Cabrera wrote: >> In short, the pTLP designation is a bit too opaque > > So you mean all TLPs should have status labels? > > Might be useful...probatory, active, low activity, attic candidate...why not. Absolutely. And it belongs to a different effort (just trying as hard as I can not to boil the ocean with pTLP for now). Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Practical next steps for pTLP experiment
Hi! as I mentioned in a different thread, I feel really passionate about championing the pTLP experiment. To that end, here's what's going to happen shortly: #1 a couple of new projects that feel equally enthusiastic about trying a pTLP route (and have a level of support from a few board members) will submit a pTLP proposal to the board. #2 based on how #1 goes we will try to establish a path for existing (willing!) podlings to be converted to pTLP. A solicitation and details of what to expect will be posted on general@ with the expectations of having a couple existing podlings as part of the experiment In about 3 months time frame, if #1 and #2 are moving in the right direction, I'd like to start offering pTLP *option* for new communities seeking to join ASF. By that time I hope to have some amount of documentation detailing the process and pros/cons compared to the existing IPMC led model. In about 6 months time frame I would like to have enough details in place to submit to IPMC and start a discussion on whether pTLP is a viable model that needs to be encouraged and what does it mean for IPMC and ASF Incubation process. For all practical purposes, consider me a self-appointed pTLP champion and please, please help along as much as you can! Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
On Tue, Jan 27, 2015 at 6:28 PM, Roman Shaposhnik wrote: > ...as I mentioned in a different thread, I feel really > passionate about championing the pTLP experiment So that I can decide to agree or flame (*), do you have a definition of "the pTLP experiment" with a permanent URL (wiki page or similar) ? I quite like Greg's definition in his "my pTLP view" thread but I have no idea if that's what you mean. -Bertrand (*) me, flaming? just kidding ;-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
On Tue, Jan 27, 2015 at 9:51 AM, Bertrand Delacretaz wrote: > On Tue, Jan 27, 2015 at 6:28 PM, Roman Shaposhnik wrote: >> ...as I mentioned in a different thread, I feel really >> passionate about championing the pTLP experiment > > So that I can decide to agree or flame (*), do you have a definition > of "the pTLP experiment" with a permanent URL (wiki page or similar) ? There will be a wiki page emerging. > I quite like Greg's definition in his "my pTLP view" thread but I have > no idea if that's what you mean. That's the starting point (or pretty close anyway). I don't want to put a formal definition up yet. Partially because I don't think any further debates would be useful, but most of all, because until we have real ASF board feedback for the submitted resolution -- there's nothing to talk about, really. If anyone wants to help with drafting an upcoming resolution -- let me know. Stay tuned guys. I'll keep updating this group with links to wiki, etc. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Solicitation for IPMC Chair nomination
Thanks for the nomination, Roman. And thanks for support from Seshu and Luke. I am trying my best to help projects coming to Apache incubator to understand the Apache way and be prepared to be active and healthy top level project. However, after working with Ted in several podlings, I would love to throw my VOTE for him, if he accept the nominations. Like Marvin said in his reply, Ted is politically adept and have a lot of experience to handle the challenges of interfacing with the Board and with outside organizations, which very crucial for working in VP of incubator. - Henry On Mon, Jan 26, 2015 at 10:45 AM, Roman Shaposhnik wrote: > Hi! > > after making sure that there's still an Incubator > to be managed for the next 6-12 months, I'd like > to open up a discussion thread on soliciting > nominations for the next IPMC Chair. > > Feel free to self-nominate or nominate folks who > you know. Provide a summary of your 'program' > or not. At this point, we want as much feedback > and discussion as possible. The VOTE thread will > come in a few weeks. > > Things to keep in mind while thinking about nominating > yourself or others: >1. This is a 6-12 months commitment that, based on my > personal experience, would require you to allocate 7-10 > hours per week. > > 2. This is a rotating Chair and you would be expected to > start a similar thread in 12 months. > > 3. From where I sit, the most important job for the new > Chair for the next few months would be to help shape > the incremental, actionable plan for improving the > mentoring situation in the Incubator. > > 4. The situation around 'professional student' podlings > is not improving nearly quick enough (4 years without > a single release? really?). Anybody who has actionable > ideas on how to improve it would get my support. > > Now, to get the ball rolling, here are the two folks I'd > like to suggest as future IPMC Chairs: > * Ted Dunning > * Henry Saputra > In my view, both have demonstrated an exceptional > understanding of the 'Apache Way', dedication to > mentoring podlings they are responsible for and enthusiasm > around bringing new communities into the ASF family. > On top of that, both have exercised a remarkable skill > in conducting public discussions and driving towards > consensus. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
There are a few things that I would suggest for "next steps": 1) Draft a template resolution. Starting in the wiki is fine, but you'll want to involve board@ when you have your first draft done. This will also start the discussion among the Directors (recall: the Board hasn't even agreed to try this!), and may produce some refinements. 2) Create a ComDev page discussing what it means to be a "provisional TLP". The disclaimers/warnings/release-naming should likely mirror what we do for incubating podlings. 3) Note that I use "provisional", since "probationary" implies you got in trouble. I wouldn't really worry about time frames. This will be a very subjective process, and every project is different. It will be hard to make a solid determination on day X in the future. If I were to put my thumb in the air, I'd say 6 and 12 months, rather than your 3/6. Cheers, -g On Tue, Jan 27, 2015 at 11:28 AM, Roman Shaposhnik wrote: > Hi! > > as I mentioned in a different thread, I feel really > passionate about championing the pTLP experiment. > To that end, here's what's going to happen shortly: > #1 a couple of new projects that feel equally enthusiastic >about trying a pTLP route (and have a level of support >from a few board members) will submit a pTLP proposal >to the board. > #2 based on how #1 goes we will try to establish a path >for existing (willing!) podlings to be converted to pTLP. >A solicitation and details of what to expect will be posted >on general@ with the expectations of having a couple >existing podlings as part of the experiment > > In about 3 months time frame, if #1 and #2 are moving in the > right direction, I'd like to start offering pTLP *option* for new > communities seeking to join ASF. By that time I hope to have > some amount of documentation detailing the process and pros/cons > compared to the existing IPMC led model. > > In about 6 months time frame I would like to have enough details > in place to submit to IPMC and start a discussion on whether > pTLP is a viable model that needs to be encouraged and what > does it mean for IPMC and ASF Incubation process. > > For all practical purposes, consider me a self-appointed pTLP > champion and please, please help along as much as you can! > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Practical next steps for pTLP experiment
On Tue, Jan 27, 2015 at 1:28 PM, Greg Stein wrote: > There are a few things that I would suggest for "next steps": > > 1) Draft a template resolution. Starting in the wiki is fine, but you'll > want to involve board@ when you have your first draft done. This will also > start the discussion among the Directors (recall: the Board hasn't even > agreed to try this!), and may produce some refinements. > > 2) Create a ComDev page discussing what it means to be a "provisional TLP". > The disclaimers/warnings/release-naming should likely mirror what we do for > incubating podlings. +1000. This translates the idea of using ComDev as a venue for managing documentation into reality. Writers here want to pave a path for new projects outside the IPMC that depends on ComDev to take up some tasks. The sooner the action moves from 'here' to 'there', bringing actual volunteer effort, the better. > > 3) Note that I use "provisional", since "probationary" implies you got in > trouble. > > I wouldn't really worry about time frames. This will be a very subjective > process, and every project is different. It will be hard to make a solid > determination on day X in the future. If I were to put my thumb in the air, > I'd say 6 and 12 months, rather than your 3/6. > > Cheers, > -g > > On Tue, Jan 27, 2015 at 11:28 AM, Roman Shaposhnik wrote: > >> Hi! >> >> as I mentioned in a different thread, I feel really >> passionate about championing the pTLP experiment. >> To that end, here's what's going to happen shortly: >> #1 a couple of new projects that feel equally enthusiastic >>about trying a pTLP route (and have a level of support >>from a few board members) will submit a pTLP proposal >>to the board. >> #2 based on how #1 goes we will try to establish a path >>for existing (willing!) podlings to be converted to pTLP. >>A solicitation and details of what to expect will be posted >>on general@ with the expectations of having a couple >>existing podlings as part of the experiment >> >> In about 3 months time frame, if #1 and #2 are moving in the >> right direction, I'd like to start offering pTLP *option* for new >> communities seeking to join ASF. By that time I hope to have >> some amount of documentation detailing the process and pros/cons >> compared to the existing IPMC led model. >> >> In about 6 months time frame I would like to have enough details >> in place to submit to IPMC and start a discussion on whether >> pTLP is a viable model that needs to be encouraged and what >> does it mean for IPMC and ASF Incubation process. >> >> For all practical purposes, consider me a self-appointed pTLP >> champion and please, please help along as much as you can! >> >> Thanks, >> Roman. >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: my pTLP view
On Tue, Jan 27, 2015 at 12:14 PM, Roman Shaposhnik wrote: > On Tue, Jan 27, 2015 at 6:58 AM, Bertrand Delacretaz > wrote: >> On Tue, Jan 27, 2015 at 3:38 PM, Alan D. Cabrera >> wrote: >>> In short, the pTLP designation is a bit too opaque >> >> So you mean all TLPs should have status labels? >> >> Might be useful...probatory, active, low activity, attic candidate...why not. > > Absolutely. And it belongs to a different effort (just trying as hard as I can > not to boil the ocean with pTLP for now). I support Greg's idea that, in the initial experiment, they are flagged (and presumably required to DISCLAIM and respect PR restrictions), because that's the incremental path of not changing everything all at the same time. I support Bertrand's suggestion that, if this idea really turns out to work, the flag may go into the attic over time. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
On Tue, Jan 27, 2015 at 10:36 AM, Benson Margulies wrote: > On Tue, Jan 27, 2015 at 1:28 PM, Greg Stein wrote: >> There are a few things that I would suggest for "next steps": >> >> 1) Draft a template resolution. Starting in the wiki is fine, but you'll >> want to involve board@ when you have your first draft done. This will also >> start the discussion among the Directors (recall: the Board hasn't even >> agreed to try this!), and may produce some refinements. >> >> 2) Create a ComDev page discussing what it means to be a "provisional TLP". >> The disclaimers/warnings/release-naming should likely mirror what we do for >> incubating podlings. > > +1000. This translates the idea of using ComDev as a venue for > managing documentation into reality. Writers here want to pave a path > for new projects outside the IPMC that depends on ComDev to take up > some tasks. The sooner the action moves from 'here' to 'there', > bringing actual volunteer effort, the better. Totally agreed! Who can help me learning the ropes on how ComDev documentation is maintained, etc? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
On Tue, Jan 27, 2015 at 12:38 PM, Roman Shaposhnik wrote: >... > Totally agreed! Who can help me learning the ropes on how ComDev > documentation is maintained, etc? > Maybe ask on dev@community rather than general@ ?? :-P
Re: [DISCUSS] Solicitation for IPMC Chair nomination
Thanks to the Kylin guys for their support. And to Marvin. And Roman. I have spent a lot of time considering and have decided that I will accept this nomination. The source of my reticence is that if I take on this responsibility, I will have to become part of the missing-mentor problem and pull back from some of the mentorship work that I am doing. My feeling is that this won't be a huge problem. In all of the projects I am helping now, there are other active mentors and most of the projects are maturing rapidly (like Calcite) or have graduated (like Flink). Henry is on some of the new projects and Roman is on another so they all seem to be in good hands. So, I would be happy and enthusiastic to help by working with the Incubator project in this role. On Tue, Jan 27, 2015 at 1:17 PM, Henry Saputra wrote: > Thanks for the nomination, Roman. And thanks for support from Seshu and > Luke. > > I am trying my best to help projects coming to Apache incubator to > understand the Apache way and be prepared to be active and healthy top > level project. > > However, after working with Ted in several podlings, I would love to > throw my VOTE for him, if he accept the nominations. > Like Marvin said in his reply, Ted is politically adept and have a lot > of experience to handle the challenges of interfacing with the Board > and with outside > organizations, which very crucial for working in VP of incubator. > > > - Henry > > > On Mon, Jan 26, 2015 at 10:45 AM, Roman Shaposhnik wrote: > > Hi! > > > > after making sure that there's still an Incubator > > to be managed for the next 6-12 months, I'd like > > to open up a discussion thread on soliciting > > nominations for the next IPMC Chair. > > > > Feel free to self-nominate or nominate folks who > > you know. Provide a summary of your 'program' > > or not. At this point, we want as much feedback > > and discussion as possible. The VOTE thread will > > come in a few weeks. > > > > Things to keep in mind while thinking about nominating > > yourself or others: > >1. This is a 6-12 months commitment that, based on my > > personal experience, would require you to allocate 7-10 > > hours per week. > > > > 2. This is a rotating Chair and you would be expected to > > start a similar thread in 12 months. > > > > 3. From where I sit, the most important job for the new > > Chair for the next few months would be to help shape > > the incremental, actionable plan for improving the > > mentoring situation in the Incubator. > > > > 4. The situation around 'professional student' podlings > > is not improving nearly quick enough (4 years without > > a single release? really?). Anybody who has actionable > > ideas on how to improve it would get my support. > > > > Now, to get the ball rolling, here are the two folks I'd > > like to suggest as future IPMC Chairs: > > * Ted Dunning > > * Henry Saputra > > In my view, both have demonstrated an exceptional > > understanding of the 'Apache Way', dedication to > > mentoring podlings they are responsible for and enthusiasm > > around bringing new communities into the ASF family. > > On top of that, both have exercised a remarkable skill > > in conducting public discussions and driving towards > > consensus. > > > > Thanks, > > Roman. > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Solicitation for IPMC Chair nomination
On Tue, Jan 27, 2015 at 9:19 PM, Ted Dunning wrote: > ...I would be happy and enthusiastic to help by working with the Incubator > project in this role +1, thanks! We have a growing number of survivors who demonstrate that it's possible to do a great job as an Incubator PMC chair without losing your sanity (at least not completely ;-). Looking forward to another one! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSS] Solicitation for IPMC Chair nomination
+1 (and on a personal note, thank you for making possible to, once again, avoid throwing my own hat into the ring). Ross -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Tuesday, January 27, 2015 12:32 PM To: Incubator General Subject: Re: [DISCUSS] Solicitation for IPMC Chair nomination On Tue, Jan 27, 2015 at 9:19 PM, Ted Dunning wrote: > ...I would be happy and enthusiastic to help by working with the > Incubator project in this role +1, thanks! We have a growing number of survivors who demonstrate that it's possible to do a great job as an Incubator PMC chair without losing your sanity (at least not completely ;-). Looking forward to another one! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] [PROPOSAL] Singa for Apache Incubator
Hello everyone, I would like to propose the inclusion of Singa as an Apache Incubator project. Here is the proposal - https://wiki.apache.org/incubator/SingaProposal Please review the proposal and give feedback. I am planning to start a vote after 7 days if the proposal looks good. We are also seeking additional Apache mentors for the project. Thanks, Thejas == Singa Incubator Proposal Abstract SINGA is a distributed deep learning platform. Proposal SINGA is an efficient, scalable and easy-to-use distributed platform for training deep learning models, e.g., Deep Convolutional Neural Network and Deep Belief Network. It parallelizes the computation (i.e., training) onto a cluster of nodes by distributing the training data and model automatically to speed up the training. Built-in training algorithms like Back-Propagation and Contrastive Divergence are implemented based on common abstractions of deep learning models. Users can train their own deep learning models by simply customizing these abstractions like implementing the Mapper and Reducer in Hadoop. Background Deep learning refers to a set of feature (or representation) learning models that consist of multiple (non-linear) layers, where different layers learn different levels of abstractions (representations) of the raw input data. Larger (in terms of model parameters) and deeper (in terms of number of layers) models have shown better performance, e.g., lower image classification error in Large Scale Visual Recognition Challenge. However, a larger model requires more memory and larger training data to reduce over-fitting. Complex numeric operations make the training computation intensive. In practice, training large deep learning models takes weeks or months on a single node (even with GPU). Rational Deep learning has gained a lot of attraction in both academia and industry due to its success in a wide range of areas such as computer vision and speech recognition. However, training of such models is computationally expensive, especially for large and deep models (e.g., with billions of parameters and more than 10 layers). Both Google and Microsoft have developed distributed deep learning systems to make the training more efficient by distributing the computations within a cluster of nodes. However, these systems are closed source softwares. Our goal is to leverage the community of open source developers to make SINGA efficient, scalable and easy to use. SINGA is a full fledged distributed platform, that could benefit the community and also benefit from the community in their involvement in contributing to the further work in this area. We believe the nature of SINGA and our visions for the system fit naturally to Apache's philosophy and development framework. Initial Goals We have developed a system for SINGA running on a commodity computer cluster. The initial goals include, * improving the system in terms of scalability and efficiency, e.g., using Infiniband for network communication and multi-threading for one node computation. We would consider extending SINGA to GPU clusters later. * benchmarking with larger datasets (hundreds of millions of training instances) and models (billions of parameters). * adding more built-in deep learning models. Users can train the built-in models on their datasets directly. Current Status Meritocracy We would like to follow ASF meritocratic principles to encourage more developers to contribute in this project. We know that only active and excellent developers can make SINGA a successful project. The committer list and PMC will be updated based on developers' performance and commitment. We are also improving the documentation and code to help new developers get started quickly. Community SINGA is currently being developed in the Database System Research Lab at the National University of Singapore (NUS) in collaboration with Zhejiang University in China. Our lab has extensive experience in building database related systems, including distributed systems. Six PhD students and research assistants (Jinyang Gao, Kaiping Zheng, Sheng Wang, Wei Wang, Zhaojing Luo and Zhongle Xie) , a research fellow (Anh Dinh) and three professors (Beng Chin Ooi, Gang Chen, Kian Lee Tan) have been working for a year on this project. We are open to recruiting more developers from diverse backgrounds. Core Developers Beng Chin Ooi, Gang Chen and Kian Lee Tan are professors who have worked on distributed systems for more than 20 years. They have collaborated with the industry and have built various large scale systems. Anh Dinh's research is also on distributed systems, albeit with more focus on security aspects. Wei Wang's research is on deep learning problems including deep learning applications and large scale training. Sheng Wang and Jinyang are working on efficient indexing, querying of large scale data and machine learning. Kaiping, Zhaojing and Zhongle are new PhD
Re: [DISCUSS] [PROPOSAL] Singa for Apache Incubator
Quick immediate comment that "Apache H2O" is not really Apache project. I assume you are referring to https://github.com/h2oai/h2o (or https://github.com/h2oai/h2o-dev) ? - Henry On Tue, Jan 27, 2015 at 5:29 PM, Thejas Nair wrote: > Hello everyone, > > I would like to propose the inclusion of Singa as an Apache Incubator project. > > Here is the proposal - https://wiki.apache.org/incubator/SingaProposal > > Please review the proposal and give feedback. I am planning to start a > vote after 7 days if the proposal looks good. > We are also seeking additional Apache mentors for the project. > > Thanks, > Thejas > == > Singa Incubator Proposal > > Abstract > > SINGA is a distributed deep learning platform. > > Proposal > > SINGA is an efficient, scalable and easy-to-use distributed platform > for training deep learning models, e.g., Deep Convolutional Neural > Network and Deep Belief Network. It parallelizes the computation > (i.e., training) onto a cluster of nodes by distributing the training > data and model automatically to speed up the training. Built-in > training algorithms like Back-Propagation and Contrastive Divergence > are implemented based on common abstractions of deep learning models. > Users can train their own deep learning models by simply customizing > these abstractions like implementing the Mapper and Reducer in Hadoop. > > Background > > Deep learning refers to a set of feature (or representation) learning > models that consist of multiple (non-linear) layers, where different > layers learn different levels of abstractions (representations) of the > raw input data. Larger (in terms of model parameters) and deeper (in > terms of number of layers) models have shown better performance, e.g., > lower image classification error in Large Scale Visual Recognition > Challenge. However, a larger model requires more memory and larger > training data to reduce over-fitting. Complex numeric operations make > the training computation intensive. In practice, training large deep > learning models takes weeks or months on a single node (even with > GPU). > > Rational > > Deep learning has gained a lot of attraction in both academia and > industry due to its success in a wide range of areas such as computer > vision and speech recognition. However, training of such models is > computationally expensive, especially for large and deep models (e.g., > with billions of parameters and more than 10 layers). Both Google and > Microsoft have developed distributed deep learning systems to make the > training more efficient by distributing the computations within a > cluster of nodes. However, these systems are closed source softwares. > Our goal is to leverage the community of open source developers to > make SINGA efficient, scalable and easy to use. SINGA is a full > fledged distributed platform, that could benefit the community and > also benefit from the community in their involvement in contributing > to the further work in this area. We believe the nature of SINGA and > our visions for the system fit naturally to Apache's philosophy and > development framework. > > Initial Goals > > We have developed a system for SINGA running on a commodity computer > cluster. The initial goals include, * improving the system in terms of > scalability and efficiency, e.g., using Infiniband for network > communication and multi-threading for one node computation. We would > consider extending SINGA to GPU clusters later. * benchmarking with > larger datasets (hundreds of millions of training instances) and > models (billions of parameters). * adding more built-in deep learning > models. Users can train the built-in models on their datasets > directly. > > Current Status > > Meritocracy > > We would like to follow ASF meritocratic principles to encourage more > developers to contribute in this project. We know that only active and > excellent developers can make SINGA a successful project. The > committer list and PMC will be updated based on developers' > performance and commitment. We are also improving the documentation > and code to help new developers get started quickly. > > Community > > SINGA is currently being developed in the Database System Research Lab > at the National University of Singapore (NUS) in collaboration with > Zhejiang University in China. Our lab has extensive experience in > building database related systems, including distributed systems. Six > PhD students and research assistants (Jinyang Gao, Kaiping Zheng, > Sheng Wang, Wei Wang, Zhaojing Luo and Zhongle Xie) , a research > fellow (Anh Dinh) and three professors (Beng Chin Ooi, Gang Chen, Kian > Lee Tan) have been working for a year on this project. We are open to > recruiting more developers from diverse backgrounds. > > Core Developers > > Beng Chin Ooi, Gang Chen and Kian Lee Tan are professors who have > worked on distributed systems for more than 20 years. They have > collaborated
