<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Some comments in line On 24/04/14 23:26, Pasi Lallinaho wrote: </div> <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap="">Hello there, during the meeting today [1] there was some discussion to set up a new, low-traffic, high-importance list for the Xubuntu team. Only team members could post to the list, but everybody could subscribe to read the list. Topics and tasks for the list would include: * Voting on project-related questions (currently done during the meetings)</pre> </blockquote> <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> </blockquote> This should only be members of -team anyway (relates to a later point) <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> * Announcing meeting minutes and monthly team reports</pre> </blockquote> <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> </blockquote> Shouldn't those be for the Xubuntu Community <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> * Calls for testing, or request for other input</pre> </blockquote> <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> </blockquote> This will not work with regard to -qa - we use more than just the dev list to call for testing. Also get more response to calls from testing from those people than anyone in -team. We'd have to get people to subscribe to a new list - that likely wouldn't be of much use - just to get testing calls. <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> * Other important project announcements</pre> </blockquote> <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> </blockquote> These should be announced to the Xubuntu Community, <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> Some of the pros of setting up this new list include: * The team is currently heavily organized in IRC, moving more of the important communication to a low-traffic mailing list could make contributing less exclusive * A low traffic list would be easier to read for the team members as well as other people digging up decicions and important milestones later</pre> </blockquote> These points are the ones that made me think of this in the first place. Communication between us in the last cycle left something to be desired - my original thoughts re this new list relate to that only, side benefits being inclusiveness re meetings - during the last cycle we were lucky if we got a third of the team there at meetings. Though opening up a new list to more than the things that -team need to discuss will soon negate that 'pro' <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> There are some potential caveats to the new list: * Subject/topic partly overlaps with the current developer list</pre> </blockquote> Not if we work it properly it won't. <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> * Not allowing people who aren't team members could make the list seem exclusive (though commenting on issues would still be possible on the development list)</pre> </blockquote> Some things are exclusive <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap="">Alternative options include: * Start using a speficic "tag" for the aforementioned communication (and possibly automoderate non-team members' posts with that tag)</pre> </blockquote> Not at all sure how a tag will help. All that means is that a mail that people are ignoring has a tag - and it's still hidden in the list and the mists of time. <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap=""> * Increase the strictness of the moderation in the developer list to make it lower traffic and more relevant (con: probably affects list atmosphere and makes the thresold to post too(?) high)</pre> </blockquote> I'm not sure that this will help to increase communication - which is what my proposal was about. <blockquote cite="mid:53598FB3.8010501@shimmerproject.org" type="cite"> <pre wrap="">I hope we can get all the issues raised before the next meeting, and that everybody would have some kind of opinion before the next meeting in two weeks. Start discussing! Cheers, Pasi [1] <a class="moz-txt-link-freetext" href="https://wiki.ubuntu.com/Xubuntu/Meetings/Archive/Minutes/2014-04-24">https://wiki.ubuntu.com/Xubuntu/Meetings/Archive/Minutes/2014-04-24</a> </pre> </blockquote> This does all I suppose depend to some extent on what we do with regard to Trello, if we go that way then a mailing list will likely be unnecessary. It's certainly a lot easier to work with that - and see the current status of something that trawling a mailing list. Elfy. <pre class="moz-signature" cols="72">-- Ubuntu Forum Council Member Xubuntu QA Lead</pre> </body> </html>