On 17/06/2013 10:38, Anil Madhavapeddy wrote:
From experience, the mail filter problem is the worst one. It's
*really* annoying when a mailing list I read occasionally changes its
name, and it all comes flooding through into my Inbox since I didn't
see the change notice in time (for instance, I only sample xen-devel
once a month or less).
That can be avoided by sending a "direct" mail to all xen-api list users
a week or two before the rename and then again just before (I can export
who is signed up to the list)
I would prefer a xapi-de...@lists.xenproject.org list for now, where both
developer discussion and user
enquiries are welcome (i.e. this list).
That would be a possibility, however the reality is that today most traffic on
xen-api is user traffic, with the occasional developer question. Choosing
xapi-general, was a reflection of this. My personal view is to have two lists,
but Mike as project lead does not agree as he is worried that the developer
list would be too quiet and thus would discourage new developers. This is a
valid point.
I think that the problem of a "too-quiet" developer list should be tackled
straight away. Combining the mailing lists only solves the symptom. There's clearly a
lot of discussion about xapi that happens off-list or internally to Citrix, and that's
not appropriate for an open-source project that wants to attract fresh developers.
Agreed. I will let Mike respond to that. I have brought this up several
times and opinion is not always consistent : I don't see any reasons why
most of these off-list discussions cannot happen in public. However, I
am not going to force anything on the project though. Ultimately,
contributors will look at the devel list first. If nothing is going on
on a list, they will not bother. There is a direct correlation between
list traffic and a project's capability to attract developers (and users).
A lot of developer mail traffic is usually generated by patchbombs that elicit
peer review. This doesn't really apply to Xapi since most of the discussion
goes on in Github now. One solution is to gateway Github comments into a mail
digest to have an archive of it on the developer list. That's a convenient way
to get the discussion into our mail clients for easier search, etc.
Again one for Mike. Maybe the symtom is that developer discussions
happen on Github. If that is true, we don't need a list which replicates
the traffic, but nudge developers to use github. But to be honest, I
don't believe that all discussions are happening there.
Another way to generate discussion is to have a volunteer write up a monthly "xapi
review" that gets posted on the blog and mailing list. See, for example, the
legendary Caml Weekly News that has been running for over a decade:
http://alan.petitepomme.net/cwn/
Not sure this is the answer.
Regards
Lars
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
