Listwork Meeting 2006

Looks like its quite hard to define a date for a listworkers' meeting, as they are all around the globe. So lets use this page to help finding something that can fit listworkers' disponibility.

When?

Initial Proposal: February 11th or 12th

Initial meeting: February 12th, 3PM UTC (15:00!)

Next meeting: March 12th, 3PM UTC (15:00!)

Please note here the dates and hours of disponibility. It might be better if we use a common timezone, so please note here your hours in UTC. You can find easily on the web tools to convert timezones if you don't know...

Who	Date	Time (UTC)	11-12/02?
BertAgaz	*	UTC+1	Y
AlsteR	*	UTC+1	Y
PaulWise	*	UTC+8	Y
SimonShine	busy tuesdays and wednesdays	UTC+1 (CET)	Y
JimNelson	busy tuesdays	UTC-5 (EST)	Y
ChrisC	Unavailable 11-20th Feb	UTC	N
MicahA	*	UTC-5 (EST)	Y
PietroFerrari	*	UTC-2 (BRT) untill February 19	Y
GeneX	*	UTC	Y
ToyaMileno	not able from 5 to 10 feb	UTC-2 (BRT)	Y
LuiS	*	UTC-2 (BRT)	Y
IanM	*	UTC-8 (PST)	Y
MattToups	(will likely be busy most days, but I may be able to stop in)	UTC-5 (EST)	?
AnsTi	*	UTC+1 (CET)	Y
AleX	*	UTC+1	Y

Agenda

The following topics have been proposed for the agenda:

1. Listwork policy
   • Mailing list naming conventions proposal
   • Is there any chance to spend time on working on a listwork policy?
   • Mailing list archive tarballs
     • Mailing list archive tarballs are not currently available. Find out for what reasons, discuss them, see if there s a solution to provide access to trusted people.
2. Virtual mail domain alias setup
   • We need to improve the way the postfix configuration is structured, so we can have lists.indymedia.org and indymedia.org and $IMC.indymedia.org more easily and changes can be mad eon the fly
   • Outreach on localized management of email aliases using Postfixadmin
     • This is already possible now but IMCs do not currently know about it. How can we make it known, do we really want to, and who will do it?
     • Setup process: IMCs need to request an MX entry for their subdomain pointing to sarai, and listwork needs to setup virtual mail domains. This needs to be documented.
3. "Slack list admins" listing
   • We need to contact the list admins (+ mailing list subscribers in the secod step if admins don't respond) listed on the "Slack list admins" listings we've been receiving for the past weeks. Who will take casre of which mailing lists (this could be documented on the wiki)?
4. Security and privacy of sarai
   • While the overall security level of some servers has changes in the past year, is this also the case for sarai? Do we need to increase its security level? Are they ways to improve the privacy of its users? What would make sense and what is feasible?
   • A lot of data is stored on sarai. Is there a way to increase users' privacy and reduce the amount of stored data, especially IP addresses, without stopping the software from working (which may rely on it)?
   • Is it possible and would it make sense to rewrite email headers of email sent through sarai to prevent senders' IP addresses to be leaked? Riseup seems to provide a way to do this.
   • Mailman NoIP-patch
   • mixmaster / mixminion ?
5. Listwork and SoS
   • SoS & transparency
     • SoS does not currently allow unauthenticated access to view tickets. A fix is on its way.
     • Does listwork want to restore public access to the requests made to it? Should there be two request queues, one for public and one for non-public requests?
   • SoS has been in use for some time now. Unfortunately, some tickets are stacking up there way too long now, and not every listworker seems to have requested an account, yet.
   • How do you like SoS, does it help, or should the setup be reverted?
6. Mailman updates
   • Discuss mailman 2.1.6/2.1.7 features. Is it worth the update? Are there upstream behavorial changes we need to undo?
   • Edit archiver templates not to set a bgcolor (and maybe to be valid html) - to meet Web Content Accessibility Guidelines
7. Lurker or not lurker?
   • Ansti had once tested it, then installed it on sarai, the files are still there but not accessible through the web.
   • IIRC, experiences made with lurker were better than those made with pipermail, but lurker was also missing some feature or was doing an important feature in a way not suited for Indymedia
     • private vs public lists and switching lists from public to private and back
     • replying via mailto: urls
     • usability for people used to pipermail/etc's emphasis on per-month/etc things.
   • Need to work out how to make mailman use it as an archiver
   • Need to setup a redirection system and migration strategy for the old pipermail archives
8. Encrypted mailing lists
   • Is listwork interested in and able to provide encrypted mailing lists?
   • What is the current situation about GPG encryption patches for mailman and pipermail?
   • Should encrypted mailing lists be run using mailman or should an independant system such as Firma be used?
9. Ways towards more users' self service
   • Which recurring tasks does Listwork have to deal with which it should not need to deal with?
10. Multi domain name SSL certificates for sarai
    • Currently there is only a single-domain SSL certificate for sarai in place for CN lists.indymedia.org. However, there are multiple domain names pointing to it, so it may be worth switching to a multi-domain SSL certificate.
11. What to do about /var/spool/mail/ on sarai?
    • It contains lots of mail for ppl not doing indy or listwork stuff for ages
12. Having more regular meetings?
    • Monthly/bi-monthly?
13. Got more? Please add it here!

Logs

• listwork-meeting-2006-02-12.log: Meeting logs for Febuary 12th 2006.

---

-- BertAgaz - 24 Jan 2006

-- AlsteR - 03 Feb 2006

-- MjR - 06 Feb 2006 (will not attend due to short notice)