On 07/14/2011 01:25 AM, Kay Schenk wrote:
On 07/08/2011 01:39 PM, Dave Fisher wrote:
(5) When the contributor has updated content ready then they can
proceed by according to (a) Non-committer - submit an svn diff as a
patch. (b) Committer - perform an svn commit which triggers an actual
staging build.
OK, I, personally am still not thrilled about this approach. I think
before deciding anything, maybe someone can give us a count of actual
"content developers/admins/software developers" on the existing kenai
site -- this would be folks with direct "update/committer" rights in the
existing environment to see if we can get a breakdown of what there is
now at the openoffice.org and some idea of how it's being maintained.
I'll be happy to contact the kenai admins and see what I can find out.
If there was some way to use an alternate "something" to maintain the
"user facing" site, this would be MUCH better. Right now, I'm looking at
the "es" project on openoffice.org. There are 13 (out of 347 "es"
members) users with development access to this (web) site. These folks
have basically been working in this and only this realm. It would be
optimal to have some facility where these same folks, should they choose
to join say via an Apache wiki account or other mechanism, would be
given the SAME access as they have on the new production environment
without a lot of complication.
Please explain what you mean by new production environment in the last
sentence and how much more complicated it would be.
--
Arthur
