You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2005/08/19 02:54:11 UTC

[Spamassassin Wiki] Update of "VotingProcedure" by JustinMason

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/VotingProcedure

The comment on the change is:
use a definition I think we're all agreeing on

------------------------------------------------------------------------------
  To veto code, you must issue an explicit -1 veto in a bug or in a reply to the check-in on the spamassassin-dev mailing list.  If the
  veto is for a security-related fix, you may veto on a private forum.  In addition, the veto must be accompanied with a technical reason.  Vetos should be avoided for purely procedural reasons.  If you are vetoing code, it is considered polite to allow the author an opportunity to respond or revert the code themselves, but it is not quite as imperative to wait if the change is very broken and fixing it would require significantly more effort than reverting it.
  
+ === Setting up Subprojects ===
+ 
+ Requires +1s from ''more than'' half of the PMC membership.
+