[wp-hackers] Adding a plugins svn committer

[Dion Hulse (dd32)]

Just to come to the defence of SVN here...

SVN when served via HTTP (at least, as that's the only experience I have of
it) can have permissions applied to any specific directory within the tree.
User1 has access to /, User2 can only commit to /trunk/, user3 can do
/trunk/ and /branches/, User4 can only do /trunk/translations/ etc - The
.org plugin repo is a good example really, all plugins are stored within the
same repo, with different permissions for different paths!

However, for ease of administration, the WordPress.org Plugin directory only
does it based on a a plugin slug itself, the number of multi-committor
projects is rather small (from what I know) and generally.. you trust the
person you're adding as a committor to a project.

To go into some more details.. the readme.txt file can specify trunk as the
stable tag anyway.. so a rouge committor to /trunk/ could still release a
release if they wanted to..

So:
 - SVN isn't as unfriendly as most people make it out to be
 - .org repositories are setup for ease of management
 - The number of people who would request for fine-grained permission set is
IMO probably quite small
 - If release management is what you're after, that'd probably best done as
an addition to the .org plugin bundler/etc rather than at the SVN level
anyway..

So for now: Publishing to GitHub/other providers is a good solution if you
want to allow people to have commit access, whilst still retaining control
over what is released on WordPress.org.


On 5 October 2011 06:27, Dan Phiffer <dan at phiffer.org> wrote:

> Thanks, I had over estimated the feature set of svn! GitHub is probably a
> good choice.
>
> -Dan
>
>
> On Oct 4, 2011, at 2:03 PM, Chip Bennett wrote:
>
> > Have you considered GitHub? You can give others push access to a
> development
> > version on GitHub, and then determine when to tag/commit to SVN.
> >
> > Chip
> >
> > On Tue, Oct 4, 2011 at 12:58 PM, Dan Phiffer <dan at phiffer.org> wrote:
> >
> >> I see, I was hoping to add a committer but retain sole control over
> >> releases. Sounds like it's an all or nothing proposition.
> >>
> >> Thanks,
> >> -Dan
> >>
> >>
> >> On Oct 3, 2011, at 5:41 PM, Otto wrote:
> >>
> >>> Not much to it, really.
> >>>
> >>> -Go to the plugin.
> >>> -Click the Admin link in the menu bar.
> >>> -Add the user's wordpress.org username to the committers list for the
> >> plugin.
> >>> -Wait an hour or so for it to take effect.
> >>> -Done.
> >>>
> >>> -Otto
> >>>
> >>>
> >>>
> >>> On Mon, Oct 3, 2011 at 4:33 PM, Dan Phiffer <dan at phiffer.org> wrote:
> >>>> Hello,
> >>>>
> >>>> Is there a guide to adding svn committers to an existing plugin on
> >> plugins.svn.wordpress.org? I'd just like to make sure I get the
> >> permissions part right.
> >>>>
> >>>> Thanks,
> >>>> -Dan
> >>>> _______________________________________________
> >>>> wp-hackers mailing list
> >>>> wp-hackers at lists.automattic.com
> >>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>>>
> >>> _______________________________________________
> >>> wp-hackers mailing list
> >>> wp-hackers at lists.automattic.com
> >>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>