Skip to end of metadata
Go to start of metadata

Community members monitoring the mailing lists, performing the tasks listed below.

Approving Messages from New Posters

Messages from new posters go into a moderation queue. When you review this queue (from the Google web UI) you need to:

  • click through and read the message, don't just assume non-spam from the title
  • mark obvious spam as spam
  • if you aren't sure if something is appropriate for the list, leave it in unmoderated and add an item to Mailing List Todos.
    * if the tone of a message is sliding from "tech discussion" toward "personal attack", leave the message unmoderated and add an item to Mailing List Todos.

clojure-dev requires a CA

Lots of people sign for clojure-dev without a CA. Please encourage them to sign the CA, and only add them to the list after that (CA list here). If somebody wants to make a request for the development team without signing the CA, they should do that on the Clojure mailing list.

Approving New Members

Posts from new members go in the moderation queue (see above). This continues for some time until Google magically decides the person no longer needs moderation. This can be frustrating for new members. If you see a person make several sensible posts in a row and they are still being moderated, go ahead and click on their name and set them to "no moderation needed".

Open Questions

  • The web UI is slow, and requires more clicking around than I would like. Any efficiency tips here, or API wrappers (if such exist) would be welcome.
Labels:
  1. Dec 10, 2010

    Per the meeting, my feedback was to not use Mailing List Todos wiki, but instead use Clojure Core Jira issues for follow up items. That way we get dashboard, followup/waiting-on and history support vs a wiki page. Means it waits on core Jira setup.