Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Advocacy > Re: Contributor...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 7 Topic 1382 of 1490
Post > Topic >>

Re: Contributor List policy

by josh@[EMAIL PROTECTED] (Josh Berkus) Mar 10, 2008 at 10:14 AM

Josh,

> Per the following emails and a discussion with Bruce Momjian on the
> phone I am suggesting a change (and documentation) of the way
> contributors will be determined and displayed on PostgreSQL.Org.

Mind laying out what you're proposing, exactly?  I can't say that I could 
determine from this post what you're proposing.

I also don't see why -advocacy is the appropriate forum for this 
discussion.

>   * List: sysadmins (link to subscribe form)

Um, the sysadmins list is closed an private for reasons of security.

> [2] Contributors will be determined for each team will be resolved by
> the respective teams (e.g; who is a part of the team, or leaves the
> team etc..)

Wait, wait, are you proposing that we should have contributor breakdown
per 
committee?  And that everyone on every committee should be listed, 
regardless of how much work they actually do?

This is a bit more radical than your earlier proposals.  I can see 3
things 
about it which are potential showstoppers, all of which need to be dealt 
with before we could start implementing the new policy:

1) it's an enormous amount of work compared to the previous policy, like
5x 
to 10x.  Who's going to do all this, exactly?

2) People who contribute a little in multiple areas of the project will
get 
much more exposure that people who contribute a lot in one area.  Not sure

this idea is solvable.
  
3) Asking the committees themselves to do an evaluation of who among them 
is "good enough" to be listed is asking for a lot of political infighting 
around update time, possibly with enough acrimony to make people leave the

project.

4) How do we decide which ancillary projects and organizations get linked,

and which do not?  This alone will need a lot of discussion.

Overall, I think what you're proposing is headed in the right direction, 
but I also think it will take quite a while to hammer out.  Why not update

the listings according to the draft Core policy now, and then you won't be

under time pressure to fix all of these things because we're 15 months out

of date.

-- 
--Josh

Josh Berkus
PostgreSQL @[EMAIL PROTECTED]
 Sun
San Francisco

-- 
Sent via pgsql-advocacy mailing list (pgsql-advocacy@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy




 7 Posts in Topic:
Re: Contributor List policy
josh@[EMAIL PROTECTED] (  2008-03-10 10:14:48 
Re: Contributor List policy
josh@[EMAIL PROTECTED] (  2008-03-10 12:52:04 
Re: Contributor List policy
ajs@[EMAIL PROTECTED] (A  2008-03-10 18:27:46 
Re: Contributor List policy
alvherre@[EMAIL PROTECTED  2008-03-10 19:39:36 
Re: Contributor List policy
dan@[EMAIL PROTECTED] (D  2008-03-10 18:41:45 
Re: Contributor List policy
josh@[EMAIL PROTECTED] (  2008-03-10 16:39:30 
Re: Contributor List policy
bruce@[EMAIL PROTECTED]   2008-03-10 23:11:18 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Fri Jul 4 14:09:57 CDT 2008.