GHC11 included an Open Source Day, a hackathon where participants worked on a variety of projects including GNU Mailman. These are some rough notes for the session.

Subscriber info summary (membership management page)

1. name
2. email address(es)
3. date of starting subscription
4. How frequently does the subscriber login/post?
5. Phone number if willing to give that info (optional)
6. description of who they are (optional)
   1. list version (drop-down) eg. student, engineer
   2. text box where they can enter more info if needed. (e.g. useful for Systers' essays)
7. How often do they want messages?
   1. daily/weekly/monthly
   2. form (digest, others?)
8. Facebook/twitter info (optional) if they have it

Simple interface notes

What are the most relevant options?

• list name
• description
• subject prefix
• welcome/goodbye message

Links to...

• membership management
• changing setup options (many options are set really one-time and seldom changed, like language options)
• tend moderator requests
• archives

Advanced setup options

• digest format
• non-digest format
• privacy
• bounce processing
• auto-responder

• content filtering & topics

Change simple setup options

• discard held messages aver < 0 > days (hours, minutes, months?)

• Change list ownership pwd

• Language option <English> (drop down multi-select?)

Use Cases for colleges and universities

College Classes:

1. reuse mailing lists with different users (e.g. teaching comp 1001 every semester...)
2. delete everyone on the list
   • and move them to another list
   • and have a custom "you've been moved message option"
   • allow users to share their address with others (or not -- note: FIPPA)
3. add/import new users
   • from another data source
   • and allow different delimiters
4. expert subscription list
5. privacy

6. option to not reveal the senders' email address.

7. option to make lists of subscribers unavailable even to other subscribers (see draconian privacy notes)
8. clone a list/templates