Re: Soliciting feedback for a detailed pTLP policy document

2015-03-06 Thread Shane Curcuru
On 3/4/15 1:41 PM, Benson Margulies wrote:

 On Wed, Mar 4, 2015 at 1:12 PM, Doug Cutting cutt...@apache.org
 mailto:cutt...@apache.org wrote:

 On Mon, Mar 2, 2015 at 5:31 PM, Roman Shaposhnik r...@apache.org
 mailto:r...@apache.org wrote:
...
 As a director, I still don't think the board needs to be involved in a
 pTLP's graduation.  As far as I'm concerned, any provisional
 status is self-imposed by the PMC and can be removed at its pleasure.
 From the board's perspective it's either an ASF project or it's not,
 there's not a useful middle ground.  As a project it needs to provide
 reports, release according to accepted standards, operate openly, etc.
 It may be a young project, with a PMC dominated by old-timers who
 aren't responsible for much of the contribution, but I don't see why
 that requires a new formal status any more than we need a formal
 status for old, slow-moving projects that rarely release.
 
 Put directly, what does a pTLP's graduation change from the board's
 perspective?  How should it change the way we review the project's
 reports, etc.?  In short, why should we care about this label?  If a
 PMC wishes to call itself blue that's fine too, but we don't need a
 resolution when it decides to call itself purple.
 
 
 What's your view of 'incubation disclaimers'? The above paragraph makes
 most sense to me if there are none for pTLPs.

The bigger question is: what does pTLP mean to the rest of the world?

Incubation disclaimers are there to inform the rest of the world that
the community working there, and the software it produces, are not (yet)
true Apache projects.  That is, we want end users to understand that
there may be different expectations of project behavior and software
product quality or availability for Incubator podlings than the world
has for full Apache projects.

How are we clearly describing to end users what differences they might
expect between the operations and functionality of pTLPs versus Apache
projects (i.e. formal TLPs)?  And who, specifically, decides when the
pTLP becomes a TLP?

While it's important to ensure that we're being clear within our
communities about how we operate and improve, in this case it's also
really important that we make it clear to the rest of the world what a
pTLP is.

- Shane


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Wiki access

2015-03-06 Thread Bertrand Delacretaz
On Fri, Mar 6, 2015 at 11:07 AM, Daniel Gruno humbed...@apache.org wrote:
 Can someone grant Humbedooh write access to the wiki, please?

Humbedooh is now in https://wiki.apache.org/incubator/ContributorsGroup

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



podlings.xml has incorrect entry for AsterixDB

2015-03-06 Thread Geoffrey Corey
Hi Incubator,

It appears that there is a typo in podlings.xml that is blocking the
AsterixDB podling creation tickets.

It looks like the person who updated podlings.xml forgot to fix the places
where it says aurora during the copy and paste, e.g.:

 154 podling name=AsterixDB status=current resource=aurora
sponsor=Incubator startdate=2015-02-28

Can you please fix this?

Thanks!

On behalf of Infra,
Geoff Corey


Re: podlings.xml has incorrect entry for AsterixDB

2015-03-06 Thread Geoffrey Corey
Thanks!

On Fri, Mar 6, 2015 at 8:51 AM, Mattmann, Chris A (3980) 
chris.a.mattm...@jpl.nasa.gov wrote:

 Fixed!

 [chipotle:~/tmp/incubator/content] mattmann% svn commit -m fix typo in
 AsterixDB entry. h/t to Geoffrey Corey.
 Sendingpodlings.xml
 Transmitting file data .
 Committed revision 1664677.
 [chipotle:~/tmp/incubator/content] mattmann%

 
 From: Mattmann, Chris A (3980) [chris.a.mattm...@jpl.nasa.gov]
 Sent: Friday, March 06, 2015 8:42 AM
 To: cor...@apache.org
 Cc: general@incubator.apache.org; infrastruct...@apache.org
 Subject: Re: podlings.xml has incorrect entry for AsterixDB

 I'll fix sorry

 Sent from my iPhone

  On Mar 6, 2015, at 8:27 AM, Geoffrey Corey cor...@apache.org wrote:
 
  Hi Incubator,
 
  It appears that there is a typo in podlings.xml that is blocking the
 AsterixDB podling creation tickets.
 
  It looks like the person who updated podlings.xml forgot to fix the
 places where it says aurora during the copy and paste, e.g.:
 
   154 podling name=AsterixDB status=current resource=aurora
 sponsor=Incubator startdate=2015-02-28
 
  Can you please fix this?
 
  Thanks!
 
  On behalf of Infra,
  Geoff Corey

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org




Re: podlings.xml has incorrect entry for AsterixDB

2015-03-06 Thread Mattmann, Chris A (3980)
I'll fix sorry 

Sent from my iPhone

 On Mar 6, 2015, at 8:27 AM, Geoffrey Corey cor...@apache.org wrote:
 
 Hi Incubator,
 
 It appears that there is a typo in podlings.xml that is blocking the 
 AsterixDB podling creation tickets.
 
 It looks like the person who updated podlings.xml forgot to fix the places 
 where it says aurora during the copy and paste, e.g.:
 
  154 podling name=AsterixDB status=current resource=aurora 
 sponsor=Incubator startdate=2015-02-28
 
 Can you please fix this?
 
 Thanks!
 
 On behalf of Infra,
 Geoff Corey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



RE: podlings.xml has incorrect entry for AsterixDB

2015-03-06 Thread Mattmann, Chris A (3980)
Fixed! 

[chipotle:~/tmp/incubator/content] mattmann% svn commit -m fix typo in 
AsterixDB entry. h/t to Geoffrey Corey.
Sendingpodlings.xml
Transmitting file data .
Committed revision 1664677.
[chipotle:~/tmp/incubator/content] mattmann% 


From: Mattmann, Chris A (3980) [chris.a.mattm...@jpl.nasa.gov]
Sent: Friday, March 06, 2015 8:42 AM
To: cor...@apache.org
Cc: general@incubator.apache.org; infrastruct...@apache.org
Subject: Re: podlings.xml has incorrect entry for AsterixDB

I'll fix sorry

Sent from my iPhone

 On Mar 6, 2015, at 8:27 AM, Geoffrey Corey cor...@apache.org wrote:

 Hi Incubator,

 It appears that there is a typo in podlings.xml that is blocking the 
 AsterixDB podling creation tickets.

 It looks like the person who updated podlings.xml forgot to fix the places 
 where it says aurora during the copy and paste, e.g.:

  154 podling name=AsterixDB status=current resource=aurora 
 sponsor=Incubator startdate=2015-02-28

 Can you please fix this?

 Thanks!

 On behalf of Infra,
 Geoff Corey

-
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: Soliciting feedback for a detailed pTLP policy document

2015-03-06 Thread Bertrand Delacretaz
Hi Roman,

On Tue, Mar 3, 2015 at 2:31 AM, Roman Shaposhnik r...@apache.org wrote:
 ...   
 https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=51812862 ...

Thanks for this, I meant to review but haven't found time so far for a
detailed review.

However, reading the comments of other board members here I'm more and
more thinking that the provisional bit might not be practical nor
really needed. A fast track to TLP creation sounds useful in some
cases however, and some of it intersects with what the Incubator is
doing with podlings, so we might reuse most of the pTLP ideas to
better define that fast track.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Wiki access

2015-03-06 Thread Daniel Gruno

Can someone grant Humbedooh write access to the wiki, please?

With regards,
Daniel.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org