xfce goodies SVN

[Brian J. Tarricone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/24/2006 3:19 PM, Auke Kok wrote:
> hi,
> 
> Now that we have a separate goodies project, new developers will come in and I need to figure out some way to delegate authority. I propose to use the same method as we're doing with xfce-po: have one or two seniors authorize new accounts.
> 
> Details:
> 
> 1) I will still handle setting up the accounts
> 2) new devs fill in "the form", get approved by one senior group dev
> 3) we assign two senior group devs right now (not excluding core xfce devs at any rate)
> 4) goodies accounts are https/svn only unless webaccess is needed
> 5) we have a small group capable of editing the goodies website and upload files, screenies etc. (3 people max preferably)
> 
> I'd like some group consensus on the following from jasper, olivier, brian, benny, and the other core devs that I've forgotten in this list on:
> (so please Ack (acknowledge) or Nack these):
> 
> 
> a) above setup for basic project authorization

ACK

> b) Benny and Jannis as senior group devs approving new svn dev access (they already have full access to svn+webpage)

ACK

> c) approve ssh/webaccess for Nicholas Masse and grant him webpage maintainership

ACK

On a side note, someone mentioned bugzilla...  Anyone know how more
fine-grained permissions work in bugzilla?  As it stands now, anyone
with e.g. editbugs permissions can edit any bug in any product.  It
wasn't clear to me how to nail this down so specific users can just
admin specific products.  Then again, I didn't look very hard.  I really
don't want to set up separate bugzillas for everything.

Should each goodie have its own product?  Or should we just have one
"xfce goodies" project, with a component for each goodie?

	-b


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFEdN3Y6XyW6VEeAnsRAq7kAJ9p2UyevnsOKygEpFbnTLyHmd9CqwCg4h7X
IcMtskOaIYEALKCqv1Rb8X0=
=Rkwe
-----END PGP SIGNATURE-----