Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Core team Community members take turns monitoring the mailing listlists, performing the tasks listed below.

Making Sure Questions are Answered

  • If a question appears to be important, and goes unanswered or insufficiently answered for more than a day, then
    • if you know the answer, answer it. :-)
    • if you don't, please add a link to the thread, plus a one-line summary, to the Mailing List Todos page.
  • If a question recurs on the list, or is of general interest, please add the question and answer to the FAQ.

Approving Messages from New Posters


  • 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

  • What is a good period for rotation as list monitor (1 week)?
  • 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.