Re: [Cdk-devel] A CDK Policy

[Egon W. <ego...@gm...>]

Hi all,

I am happy that no one disagreed much with what I wrote...

On Thu, Jun 26, 2008 at 1:35 PM, Egon Willighagen
<ego...@gm...> wrote:
> So, I started a new project cdk-policy in trunk/, where these
> currently implicit rules will be described and their purposes
> explained.

One thing I describe in the draft is a number of roles. Keep in mind
that CDK is an open project, where anyone has a vote. Traditionally,
those who actually code up solutions have a higher vote.

CDK Member:

Anyone who is subscribed to cdk...@li.... Therefore, anyone
can become a CDK member; it's a bit more than just a CDK User (see
below). There are ~74 CDK users (probably lower, as at least I have a
few email addresses registered) [1].

CDK Developer:

Any CDK Member with SVN write access. In the future, anyone who agrees
to promises to live by the new CDK Policy can get SVN write access.
Unlike now, where there needs to be some (marginal) patch history;
however, since anyone can set up branches now to hack away, and that
trunk/ is more controlled, people have the option to learn things
while things can still be contributed to SVN.

There currently are 57 CDK Developers [2].

There are a few sub categories, with extra/special rights and responsibilities:

  CDK Maintainer:

  A CDK Developer who supervises a particular CDK project and/or
module. For example, Miguel for the reaction module, Christoph for the
SDG module, and Thomas for the CDK-Taverna project.

  CDK Project Leader:

  A CDK Developer who oversees a particular bit of the CDK project
infrastructures, such as the main CDK website, CDK News, and CDK
Nightly.

CDK User:

Anyone else who is using a CDK project.

It would be nice if we could use this Google map again:

  http://cdk.sourceforge.net/maps/people/

Red = developer, Yellow = user. Details are given on that page on how
to get yourself added, though we could consider thinking about making
icons for on webpages, with some links, so that a simple crontab
script can check some Apache log, and grep long/lat from the image
provider script, and automatically update the map.

Egon

1.http://sourceforge.net/mail/?group_id=20024
2.http://sourceforge.net/project/memberlist.php?group_id=20024

-- 
----
http://chem-bla-ics.blogspot.com/