> I am not a committer and I have never even voted for information purposes,
> but I think it is important for both the developer and the user community
> to maintain the transparency of the management of the project. This means
> having votes out in the open, where others can see them.
ABSOLUTELY! :-) You are 100% correct! :-)
> What is general@? If you are suggesting that votes should take place on
> some other mailing list, then I am not very keen.
Here is the deal: we are now a top-level project. The
james-[user|dev]@jakarta.apache.org ([user|dev]@james.apache.org when we can
rename them painlessly) mailing lists have specific roles: user discussion
and development discussion, respectively. We also have two NEW mailing
lists: [EMAIL PROTECTED] and [EMAIL PROTECTED] The latter is
private for the PMC, and open only to PMC members. It's use will likely NOT
be common. general@ is for open project discussion that is more
organizational than specific to USING or CODING james.
The [EMAIL PROTECTED] list IS open to everyone. We're talking about
how best to use it, but my view is that it should be relatively light
traffic, and used for most PMC and other project related, organizational,
discussions. Like do we want a new mailing list for the MailetAPI. Like
splitting the CVS repository into james-server, james-mailet and james-site,
and the discussion of why. And, hence my aside, that is probably where
Release Votes should take place. As I understand Danny Angus' position,
that general@ be used for most PMC business so that it *is* out in the open,
those are compatible views.
So I hope that you realize, now, that there is no intent at all to hide the
votes. :-)
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
