On Wednesday, February 25, 2015, Niclas Hedhman <nic...@hedhman.org> wrote:
> 3.7 --> That is not default for TLPs, as only PMC members subscribe to > private@ > > 3.8 --> Follow TLP recommendations and guidelines. > > 3.9 --> Follow TLP recommendations and guidelines. > > i.e. what is now written in 3.11 will cover these three points and can be > removed. > > > The proposal only refer to new projects entering Apache, would it be worth while to consider a way for projects that entered Incubator recently and has enough (whatever that is) asf members as committers ? rgds jan i > > On Wed, Feb 25, 2015 at 4:18 PM, Roman Shaposhnik <ro...@shaposhnik.org > <javascript:;>> > wrote: > > > Hi Niclas! > > > > First of all: https://issues.apache.org/jira/browse/INFRA-9195 > > Hopefully INFRA will respond soon so we can all collaborate > > on the content. At this point I've started the documentation to > > the level of details currently on Incubator pages. > > > > On Mon, Feb 23, 2015 at 6:15 PM, Niclas Hedhman <nic...@hedhman.org > <javascript:;>> > > wrote: > > > Roman, > > > > > > See comments below to > > > https://cwiki.apache.org/confluence/display/COMDEV/Provisional+TLP > > > > > > > > > 2.1 --> I suggest to change the word "probationary" to "provisional". > > > I also suggest that a text is added such as; 'It is required that the > > > "provisional" concept is explained in detail to the users, for instance > > by > > > linking to page http://xxxx' where xxxx is another page on ComDev > > > explaining pTLP from the user's perspective. > > > > Good catch. Done. > > > > > I think that 3.7. to 3.9. are really not necessary. I would like to > > suggest > > > to change that to; > > > > Could you elaborate on why do you think it is not necessary? > > > > > Setting up a Provisional Top Level Project > > > > > > * Complete Name Search in accordance with Branding policy at > > > http://www.apache.org/dev/project-names > > > * Check PMC Chair is recorded in LDAP. > > > * Request Jira from INFRA > > > * Request Mailing lists from INFRA > > > * Add project to Reporting Schedule > > > * Request source control (svn or git) from INFRA > > > * Submission of ICLAs from existing committers. > > > * Submission of CCLAs from affected companies > > > * IP Clearance as described on > http://incubator.apache.org/ip-clearance/ > > > * Filing of Software Grant, if applicable. > > > * Change to Apache License v2.0, if applicable. > > > * Update Apache Navigation to include project > > > * Request User Accounts from INFRA > > > * Request CMS from INFRA > > > * Migrate existing documentation to Apache. > > > * Ensure "Provisional" markings are adhered to, and link to http:// > .... > > > * Enable Notifications from Jira to Mailing list > > > * Migrate existing codebase to Apache > > > * Ensure dependency licensing compatibility, see > > > http://www.apache.org/legal/resolved.html > > > * Review legal compliance on all dependencies, in particular NOTICE > file. > > > * Ensure compliance with Branding policy > > > * Establish self-assessed Apache Maturity Model declaration. > > > > Great list! Added it to the dedicated section and plan to massage it > > to the level > > of details of the current Incubator process documentation. > > > > Honestly, I think if that level is enough for the board to recognize > > Incubator > > as legit it should be enough to recognize a pTLP. > > > > Thanks, > > Roman. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > <javascript:;> > > For additional commands, e-mail: general-h...@incubator.apache.org > <javascript:;> > > > > > > > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > -- Sent from My iPad, sorry for any misspellings.
