Ceki Gülcü wrote:
> All the developers who have expressed an opinion on the matter so far
> were inclined to have separate repositories with separate access
> rights. The exact internal organization of the Logging Services is
> something that should be left for the Logging Services project to
> decide.
The organization of your TLP is your choice.
I was simply trying to point out an implication as I see it in terms of how
a project's organization can effect Incubation. If a TLP treated itself as
a single project with multiple shared codebases, then it may be easier to
show that a codebase had a larger, more diverse, community than if each
codebase were treated as a separate community.
So, how a project is organized could have an impact on how quickly some of
the Incubation items are met. However, this is not imposing a structure
from above. The structure isn't specified in the STATUS file. There is a
description of what is considered important about an ASF community to
provide for the long term viability of a codebase. To pick an extreme case,
one-man codebases are not considered viable.
Incubation is not intended to be difficult. The Incubator's raison d'être
is to make sure that projects are imported, while ensuring that important
details have been observed.
The brief summary is that there is a STATUS form to be filled in, which is a
combination checklist and fill-in-the-blanks project diary of events during
Incubation. There is paper work, e.g., CLAs and/or grants, to have
completed. If there are no unfulfilled issues on the STATUS form, then
things should be fine. If not, then the Incubator works with the project to
help satisfy those things.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
