<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div style="direction: inherit;"><br></div><div><br>On Oct 28, 2016, at 8:47 PM, Christopher Aedo <<a href="mailto:doc@aedo.net">doc@aedo.net</a>> wrote:<br><br></div><blockquote type="cite"><div><span>On Fri, Oct 28, 2016 at 12:23 PM, Kenny Johnston <<a href="mailto:kenny@kencjohnston.com">kenny@kencjohnston.com</a>> wrote:</span><br><blockquote type="cite"><span>There seems to be mixed usage of mailing lists within UC groups with some</span><br></blockquote><blockquote type="cite"><span>running their own independent mailing list (Enterprise, Product Work Group)</span><br></blockquote><blockquote type="cite"><span>and others using the [GROUP] structure in the subject line to the</span><br></blockquote><blockquote type="cite"><span>user-committee list.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Given the [openstack-dev] list benefits of shared information would it be</span><br></blockquote><blockquote type="cite"><span>possible to create an [openstack-user] list and migrate the Enterprise,</span><br></blockquote><blockquote type="cite"><span>Product Work Group and non-UC specific conversations there? We could leave</span><br></blockquote><blockquote type="cite"><span>it up to the teams on if they choose to migrate.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Please educate me if this has been discussed before my time. :)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Thanks!</span><br></blockquote><span></span><br><span>Thank you for bringing this up. I'm strongly in favor of bringing all</span><br><span>the working group communication to one list and always including the</span><br><span>group in brackets on the subject line. As you pointed out, this has</span><br><span>worked well for the dev list for a very long time. Improving</span><br><span>communication across all the working groups is one thing I plan to</span><br><span>work on in the months to come, and calling this out is a great first</span><br><span>step. Getting all the working groups to discuss their</span><br><span>issues/plans/progress on the same mailing list would bare tremendous</span><br><span>benefit.</span><br><span></span><br><span>I would actually go further than you suggest, and make communicating</span><br><span>via the User Committee mailing list a requirement for every working</span><br><span>group. Imagine how much easier cross-WG coordination would be if we</span><br><span>were all on one list and made a habit of communicating on the list</span><br><span>first (vs. waiting for weekly meetings to discuss issues). The more</span><br><span>conversations we all have in the open, the more effective our groups</span><br><span>will become.</span><br></div></blockquote><div style="direction: inherit;">+1, Thanks for suggesting this Ken and, I agree with Christopher, we should try to make this a requirement for official UC working groups. It will help us collaborate with one another and it would also make it easier for new members of the OpenStack community what working groups are up to (subscribing to one address versus having to find mailing lists for all topics one might be interested in).</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">[random thought/question]</div><div style="direction: inherit;">Beyond workings group mailing lists, would/should the operator mailing list also use this new mailing list? The pro of using this new list for operators is that they can see everything and give feedback when they see fit but the con is possibly too many unrelated emails.. they could use an [operator] tag.</div><div style="direction: inherit;"><br></div><blockquote type="cite"><div><div style="direction: inherit;"><br></div><span></span><span>-Christopher</span><br><span></span><br><span>_______________________________________________</span><br><span>Enterprise-wg mailing list</span><br><span><a href="mailto:Enterprise-wg@lists.openstack.org">Enterprise-wg@lists.openstack.org</a></span><br><span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg">http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg</a></span><br></div></blockquote></body></html>