Mailing List Archive

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/RulesProjectPlan

The comment on the change is:
add the task list

------------------------------------------------------------------------------
= SpamAssassin Rules Project =

- '''(DRAFT - this part of the wiki is a discussion document, based on emails to dev list. Please feel free to add comments, but be sure to make clear that it's your opinion, by signing your name to them.)'''
+ '''(DRAFT - this part of the wiki is a discussion document, based on emails to dev list. Please feel free to add comments, but be sure to make clear that it's your opinion, by signing your name to them. Your real name is preferred, btw.)'''

== The Problem ==

@@ -25, +25 @@

Based on the problem areas outlined above, here are the pages for each aspect of the problem, and proposed solutions:

* Encouraging contribution: RulesProjMoreInput
+ * the sandboxes solution: RulesProjSandboxes
* Streamlining the 'getting rules into SpamAssassin' task: RulesProjStreamlining
* Speeding up the release cycle for rules: SaUpdatePlan
* the secrecy problem: RulesProjSecrecy
* the language problem: RulesNotEnglish

- == Repository Organization ==
+ == Outstanding Tasks/Votes ==

+ Here's a list of the tasks that have fallen out of the above plan so far... we now need to vote to go forward with these, then put them into action.
- * rules/core/ = standard rules directory
- * rules/sandbox/<username>/ = per-user sandboxes
- * rules/extra/<directory>/ = extra rule sets not in core

+ First step -- the sandboxes:
- The proposal is for rules/core to become the rules directory for trunk (3.2 and later, via SVN
- externals which will make their inclusion seamless in the standard SA tree). The sandbox is discussed
- further in RulesProjMoreInput.

- == Extras/ ==
+ * PMC vote to approve the sandboxes project (RulesProjSandboxes).
+ * ''VOTE: in progress''

+ * reorganise the rules directory into core/ , sandbox/, and extra/; link that rules project SVN repository to 3.2.0's 'rules' dir; use SVN externals to do this.
+ * ''VOTE: in progress''
- We'll want to discuss the structure and process behind creating new extras
- directories further once we reach a critical mass of committers in the rules
- project; but here's some initial thoughts on typical 'extra' rulesets.

+ * write scripts to test, filter, and pull rules from sandboxes automatically into core/ production ruleset
+ * ''VOTE: in progress''
- * 'Aggressive' rulesets, which are too likely to produce FPs for the base release
- * non-spam-oriented rules, such as the anti-virus-bounce ruleset
- * non-English-language rulesets (although see RulesNotEnglish)

+ * move current ruleset into a new "legacy" sandbox
+ * ''VOTE: in progress''
+
+ * start using the above scripts to generate core/ ruleset in svn
+ * ''VOTE: in progress''
+
+ Second step -- list-driven mass-checks:
+
+ * set up the mailing list; get subscribers. (RulesProjMoreInput)
+
+ * implement scripts, or get them from SARE. (RulesProjMoreInput)
+

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/RulesProjectPlan

The comment on the change is:
update to reflect vote status

------------------------------------------------------------------------------
First step -- the sandboxes:

* PMC vote to approve the sandboxes project (RulesProjSandboxes).
- * ''VOTE: in progress''
+ * ''VOTE: passed!''

* reorganise the rules directory into core/ , sandbox/, and extra/; link that rules project SVN repository to 3.2.0's 'rules' dir; use SVN externals to do this.
- * ''VOTE: in progress''
+ * ''VOTE: passed''
+ * ''now we need someone crazy enough to actually do this ;)''

* write scripts to test, filter, and pull rules from sandboxes automatically into core/ production ruleset
- * ''VOTE: in progress''
+ * ''VOTE: not approved -- Daniel says 'I'd like more details'.''

* move current ruleset into a new "legacy" sandbox
- * ''VOTE: in progress''
+ * ''VOTE: vetoed by Daniel.''

* start using the above scripts to generate core/ ruleset in svn
- * ''VOTE: in progress''
+ * ''VOTE: not approved -- Daniel says 'I'd like more details'.''

Second step -- list-driven mass-checks:

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/RulesProjectPlan

------------------------------------------------------------------------------

* write scripts to test, filter, and pull rules from sandboxes automatically into core/ production ruleset
* ''VOTE: not approved -- Daniel says 'I'd like more details'.''
+ * see RulesProjPromotion

* move current ruleset into a new "legacy" sandbox
* ''VOTE: vetoed by Daniel.''
+ * alternative proposal looks good though

* start using the above scripts to generate core/ ruleset in svn
* ''VOTE: not approved -- Daniel says 'I'd like more details'.''
+ * see RulesProjPromotion

Second step -- list-driven mass-checks: