decide on infrastructure privacy / secrecy policies

Initial Proposal

• A private mailing list (haskell-prime-private)

  1. committee only subscription (and archive)

  2. unmoderated for committee members

• A public mailing list - (haskel-prime) for technical discussion

  1. publicly available for subscriptions (and archive)

  2. unmoderated for committee members

  3. moderated for non-committee members, in order to keep traffic low. I feel that if a major flamewar NEEDS to happen, it can happen on haskell-cafe.

• A wiki / issue tracking system http://haskell.galois.com/cgi-bin/haskell-prime/trac.cgi/wiki

  1. publicly readable

  2. committee writable

  3. folks who ask for an account will get one (and lose it if they're abusive). the main reason for not letting the wiki be world-writable is spam.

• A code repository

  1. publicly readable

  2. anyone can submit changes, Isaac will be gate-keeper. We'll use darcs, so this is pretty easy. That's more of a technical issue than a policy one, since there isn't a machine that we all have accounts on.