Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: [Original edit by Dave]

...

KAM: Apache SpamAssassin is a framework for writing goals. I deliver rules to prove the code works but I don't view that the project has to provide rules. I use this as a guidance in where I spend my focus. Beyond that, my goal with belonging to the SysAdmin group is to ensure the project is supported with modern, secure hardware and software with a bus factor greater than one.

DAJ: Apache SpamAssassin should be an effective spam detection tool in a user's/admin's mail filtering toolbox. It cannot be perfectly tuned to each mail filtering environment due language, geographical, and other differences but users should be able to install SpamAssassin and follow some guidelines on the wiki to quickly and easily get their mail filtered accurately.

Acronymns

*ASF = Apache Software Foundation
*BZ = Bugzilla
*SA = Apache SpamAssassin
*PMC = Project Management Committee
*SVN = SubVersioN

Current Members

As of May 2017:
*Dave Jones - davej@apache.org
*Kevin A. McGrail - 703-798-0171 - kmcgrail@apache.org
*Bryan Vest - bvest@apache.org

...

*The Apache Way Shane Curcuru's post has many good points.
*LISA/Sage Code of Ethics

Acronymns

*ASF = Apache Software Foundation
*BZ = Bugzilla
*SA = Apache SpamAssassin
*PMC = Project Management Committee
*SVN = SubVersioN

Onboarding

Workflow

  1. A PMC Member nominates a new SASA member as a committer since we store items in SVN for configs.
    NOTE: If they later produce code, they should request that permission from the PMC.
  2. If the vote is successful, they then follow all the normal committer guidelines to get them an Apache ID including an appropriate committer license: New Committers Guide.
  3. After the Apache ID is setup and given to the new team member,the new member will complete their setup of the Important Resources below.
    1. http://id.apache.org - setup strong password, SSH/PGP keys, mail forwarding, etc.
    2. Subscribe to the mailing lists as their apache.org email address
    3. Setup SVN repos using the RW https URL
    4. Make sure they can login to Bugzilla
    5. Create a Jira account with a secure password (not integrated)
    6. Create a wiki login using their full name
    7. Setup OPIE
    8. Setup their Apache home page with their PGP public key
  4. Someone with Karma needs to:
    *Approve request to sysadmins mailing list
    *Add them to the wiki ContributorsGroup and AdminGroup pages
    *Open a JIRA ticket at issues.apache.org similar to INFRA-14045 to get them access to SA servers

...