----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: users@ovirt.org Sent: Thursday, April 2, 2015 2:46:42 AM Subject: Re: [ovirt-users] [DISCUSSION] oVirt Weekly Sync Goals and Future.
Il 01/04/2015 17:28, Yaniv Dary ha scritto:
Hi, In my opinion the current format can be replaced by a etherpad update that is sent as a newsletter every week. The current format doesn't add a lot of value to the project work and doesn't create a real sync on the ongoing topics. No decisions are done today there as well.
What do you think should be the goal of the weekly meeting? How can we improve it? Is a newsletter a good enough update?
I think a newsletter can replace the current sync format.
[snip]
Etherpad will unfortunately not work, nor any tool that is available to Red Hat-only community members. Any medium we evaluate has to be publicly available, or it is of little use to the oVirt community.
http://lists.ovirt.org/pipermail/users/2014-April/023399.html
:-)
Mailing lists can work, but we have to get around the problem of "missed" threads. The very fact that this thread went answered by just one person in the six days it has been live is evidence that threads on high-traffic mailing lists can get missed. Or consciously ignored. Encouraging people to attend a real-time synchronous meeting with a regular cadence can avoid that problem.
Projects that get larger often split their mailing lists along the way.
The real problem will be to split at the right place - to define the role of each list in a way that will make it very clear to people that want to post, what's the best list to use. This isn't easy at all. OTOH, if we have, say, discussion@, and keep the existing users@ and devel@, and someone posts to users@, and I think it should attract people on discussion@, it's much easier to move the discussion there, instead of starting to think who specifically I might want to Cc so that they notice.
[snip] -- Didi
Adding a new mailing list is possible, though I think that the parsing of which kind of discussion goes on what list might ultimately lead to confusion. Plus, there is a very real notion that the more "channels" people have to watch, the more chance there is that something will get missed. That's part of why we consolidated the various development-oriented mailing lists into [devel] last year in the first place. BKP -- Brian Proffitt Community Liaison oVirt Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC