I was one person who advocated for separate mailing lists in the past. But given what I have seen so far, I think you raise some very important concerns. I'm +1 on consolidating the lists provided we keep the commits/JIRA to a separate list.
It seems a lot of "users" are not aware of proton or have the wrong impression about it. We need to make a prominent notice on our main website about proton and how it relates to Qpid etc.. A common list should also make this task easier as we will increase our the audience for our discussions. Rajith On Fri, Jan 18, 2013 at 12:21 PM, Gordon Sim <[email protected]> wrote: > I believe that we have too many mailing lists and that we are missing out on > valuable collaboration and transparency as a result. > > Too often in the past topics have been discussed on the dev list without > reflecting any of the discussion back to the user list, keeping a large part > of the community in the dark. Now that we have a distinct list for proton > there is the possibility of yet more fragmentation. > > I honestly believe that we would be better off with just one list for > discussions. I think there will increasingly be issues that cross-cut > different components or that would benefit from wider participation. Not all > topics will be of interest to all subscribers, but that is always going to > be the case. > > It doesn't seem to me like any of the lists are so high in volume that this > would cause significant problems. More rigorous use of subject could help > people filter if needed. (JIRA and commit notices I think do warrant their > own lists allowing a lot of the 'noise' to be avoided if so desired). > > Any other thoughts on this? Does anyone have fears of being deluged with > unwanted emails? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
