Leo Simons wrote:
Nicola Ken Barozzi wrote:
Hence I ask to vote
It's a big thing to vote on all at once.
Ok, got the message. In fact there are serious enough points to decide to split the vote.
I still have question marks with some points. What I'm looking for is some signal that we are moving in a direction where the TLPs will actually *want* to follow incubation procedure (which would be a good sign of good functioning), *and* where all the oversight / due deligence (sp?) stuff is taken care of as well.
That's our common goal, innit?
+1
...
Legally/officially, There are no *sub*projects in Apache, only Projects that are usually called Top Level Projects or TLP. Incubation of new communities that are intended to become a TLP is the responsibility of the Incubator PMC.
For 'subprojects', the incubation responsibility is divided between the Incubator PMC and the TLP PMC.
Given the latest comments also by others, this seems the correct definition.
...Incubator Scope
================
too many complex words :D
The Incubator [scope is]:
rephrase:
2 - working with existing TLPs that are bringing in new codebases and/or existing communities to help that TLP do its "subproject" "incubation"
Ok.
3 - definition of and maintainance of the policy projects should use
when importing external codebases, therefore creating a clear
audit trail for all donations
rephrase:
3 - definition and maintainance of all policies and procedures that surround incubation
rephrase II:
3 - definition and maintainance of all policies and procedures that
projects should use when accepting code donations, therefore
creating a clear audit trail--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
------------------------------------------------------------------------------------------------------------------------------------------ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
