I'm going to nip this one in the bud right away, and given that core
and extension SVN access is already separate already, I already know
we're making use of it. In your SVN auth file on the server:
[/mediawiki/trunk/extensions/SomeExtension]
username = rw
[/mediawiki/tags/extensions/SomeExtension]
username = rw
[/mediawiki/branches/extensions/SomeExtension]
username = rw
Done. Right now I imagine for extension only access there is just 3
entries like the above, but for the whole extensions directory (I'm
guessing) and one for the whole repo.
And what review? You're not looking at code quality here, if they have
a working extension that they are releasing, do you really want them
pasting it onto the page on mw.org? I keep hearing people saying they
want to check all those in. Where's the review there? At least with a
checkin people have the opportunity to give them real feedback instead
of being ignored and stagnate into obsoleteness on
mw.org.
And really I don't think you can really comit to maintaining every
extension every person makes forever. Let's be realistic here, it's
their extension, they will maintain it, and if not and it breaks after
a long period of time, you archive it with no activity somewhere in
/branches/archives or another plan.
What I'm saying is requesting access + having a finished extension
should mean someone can immediately just add them access.
You're right this means one request per extension, but after 2 you
should be asking yourself "okay this person is contributing a lot to
the community, maybe we can give them access to the whole ext dir?"
and actually review them.
On Tue, Oct 4, 2011 at 3:35 AM, Daniel Friesen
<lists(a)nadir-seen-fire.com> wrote:
On 11-10-03 07:08 PM, Olivier Beaton wrote:
#2 Extension access? Has a working extension
attached to submission
(has some .php files in it, no need for a code review here, the
community will handle that) . Granted. Create their account, and give
them access to _only_ their extension directory.
SVN Doesn't work that way. We
can apply limited restrictions like making
the wmf branch and trunk only accessible by specific groups.
But we can't create efficiently (I don't even know if it's possible at
all) create a separate right for each and every extension and give new
committers only access to their own extension.
So anyone that gets commit implicitly has the ability to screw up any
extension or tool other than phase3 or the wmf branch.
Besides, such a pattern would suddenly mean that instead of an extension
author going through review once, they'd have to go through review for
each new extension they make so that we can add the new directory and right.