During some productive discussions in the Stewardship Working Group PTG
room, the subject of the mailing list came up. The usual questions
around whether or not we should have per-project lists came up and the
reasons we don't were re-affirmed. To recap those reasons:
* Cross posting is the pits
* People don't always know at the beginning of a thread that a
discussion will need to go wider, leading to silos and confusion.
So we turned to ways to help reduce peoples' load while reading e-mail,
since many (most?) tend to opt out of reading openstack-dev.
There are a number of ways that we can help, including teaching people
to have more efficient workflows and use specific mail reading tools
(don't worry, we're not adding an NNTP gateway.. yet). But one that
received positive feedback from the room was to have moderated
business-only mailing lists for each project.
Basically, there are things that we _do_ know will not go wider when
the thread begins. Just running through the threads on the February
thread index, there are a few obvious classes:
* Mascots
* Social meetups
* Meeting logistics
* Core team membership
There are likely others. The idea is that these messages would go into a
${project}-busin...@lists.openstack.org. Said list would be moderated by
a team of the PTL's choosing, and we would admonish moderators to reject
soundly any threads not obviously single project business related.
Thoughts? If this sounds good, I'll go ahead and write up a spec.
(openstack-specs?)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
