I thought that non-committer write access to Confluence had been
turned off. I now see that it was one of your questions -- my answer
is "now".
Hernan, can you make this happen?
WRT further process questions, see inline...
--kevan
On Apr 28, 2008, at 10:02 AM, Hernan Cunico wrote:
Guys we need to wrap up this discussion. I'm not sure where are we
standing but still have a bunch of questions.
A few things that look clear to me thus far
- We'll request every contributor to submit a CLA. Filing
instructions are provided in the Individual Contributor License
Agreement itself available here http://www.apache.org/licenses
- Every contributor will have to expressly communicate intention for
contributing with the project's documentation sending a email to dev@geronimo.apache.org
Some things still pending
- Having a CLA on file will suffice to grant edit access to the doc
or we'll seek PMC voting?
We should create a geronimo/project/confluence-contributors.txt file
in svn. When someone requests access and we've verified a CLA is on
file, add their name to this file with confluence information. commit
the new contents to svn.
- Although a CLA is ASF wide we should provide access to only those
interested in contributing to Geronimo's documentation. Do we
already keep a separate list?
Does the above file address this?
- When do we make effective such access restriction?
Now.
- What Confluence spaces will be affected?
All.
- How do we deal with existing content? We can not apply this
retroactively.
Retroactively request ICLAs from past contributors. Address the
problem when/if we want to use our current content in some new way
Once all these are sorted out I'll update the Apache Geronimo
Policies on the web site (http://geronimo.apache.org/project-policies.html
) to reflect these changes
Cool.
--kevan
