[openstack-dev] [policy] Let's make topics mandatory for openstack-dev
Hi folks, Open Stack community grows continuously bringing more people and so new initiatives and new projects. This growing amount of people, initiatives and projects causes increasing the amount of discussions in our mailing list. The problem which I'm talking about is that controlling the mailing list gets harder with the growth of the community. It takes too much time to check for important emails and delete/archive the rest even now. And it does not tend to get any easier in the future. Most of the email services and email clients support filtering incoming emails. So one can automatically get rid of certain emails by creating appropriate filters. Topics in subjects seem to be the best objects for creating rules, i.e., when someone is interested only in Keystone he can create an email filter for '[keystone]' substring in the subject. The problem with the topics is that a lot of emails in openstack-dev do not contain topics in their subjects, which makes this kind of filtering very ineffective. My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? - Roman Prykhodchenko - romcheg on freenode.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
On 5 December 2013 22:35, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: Hi folks, My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? My expectation is that [ALL] would be the result, for things that currently have no topic. - Why not filter for just topics locally, wouldn't that be equivalent? -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
On Thu, 2013-12-05 at 11:35 +0200, Roman Prykhodchenko wrote: Hi folks, Open Stack community grows continuously bringing more people and so new initiatives and new projects. This growing amount of people, initiatives and projects causes increasing the amount of discussions in our mailing list. The problem which I'm talking about is that controlling the mailing list gets harder with the growth of the community. It takes too much time to check for important emails and delete/archive the rest even now. And it does not tend to get any easier in the future. Most of the email services and email clients support filtering incoming emails. So one can automatically get rid of certain emails by creating appropriate filters. Topics in subjects seem to be the best objects for creating rules, i.e., when someone is interested only in Keystone he can create an email filter for '[keystone]' substring in the subject. The problem with the topics is that a lot of emails in openstack-dev do not contain topics in their subjects, which makes this kind of filtering very ineffective. My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? Alternatively, separate mailing lists for each current topic area. A top-level mailing list could subscribe to all of them for anybody who truly wants the fire hose. Matt ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
I like the proposal and I share the pain of checking for the important emails in the pile of all and potentially missing on some in timely fashion. My 2 cents on top of creating an automated rule: Most of the people (not all) I see on dev-list are active on either 1 or 2 project specific discussions. Why not create openstack-dev-project lists and have people subsribe to project list(s) that they are interested in. Biggest advantage I see with this approach is that one can actively participate by getting individual emails for the project mailing list that they are working on. In parallel they can opt for digest for rest of the project(s) where they act only in read-only mode. Thoughts? Ronak On Thu, Dec 5, 2013 at 3:05 PM, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: Hi folks, Open Stack community grows continuously bringing more people and so new initiatives and new projects. This growing amount of people, initiatives and projects causes increasing the amount of discussions in our mailing list. The problem which I'm talking about is that controlling the mailing list gets harder with the growth of the community. It takes too much time to check for important emails and delete/archive the rest even now. And it does not tend to get any easier in the future. Most of the email services and email clients support filtering incoming emails. So one can automatically get rid of certain emails by creating appropriate filters. Topics in subjects seem to be the best objects for creating rules, i.e., when someone is interested only in Keystone he can create an email filter for '[keystone]' substring in the subject. The problem with the topics is that a lot of emails in openstack-dev do not contain topics in their subjects, which makes this kind of filtering very ineffective. My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? - Roman Prykhodchenko - romcheg on freenode.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
We can create a list of official topics that correspond to certain projects, i.e., [keystone], [nova], . [org]. If none of them is in the subject the email can be rejected. It's also possible to create an [other] topic and pre-moderate it. On 05.12.13 12:02, Robert Collins wrote: On 5 December 2013 22:35, Roman Prykhodchenko rprikhodche...@mirantis.com wrote: Hi folks, My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? My expectation is that [ALL] would be the result, for things that currently have no topic. - Why not filter for just topics locally, wouldn't that be equivalent? -Rob signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
Le 05/12/2013 11:03, Matthew Booth a écrit : On Thu, 2013-12-05 at 11:35 +0200, Roman Prykhodchenko wrote: Hi folks, Open Stack community grows continuously bringing more people and so new initiatives and new projects. This growing amount of people, initiatives and projects causes increasing the amount of discussions in our mailing list. The problem which I'm talking about is that controlling the mailing list gets harder with the growth of the community. It takes too much time to check for important emails and delete/archive the rest even now. And it does not tend to get any easier in the future. Most of the email services and email clients support filtering incoming emails. So one can automatically get rid of certain emails by creating appropriate filters. Topics in subjects seem to be the best objects for creating rules, i.e., when someone is interested only in Keystone he can create an email filter for '[keystone]' substring in the subject. The problem with the topics is that a lot of emails in openstack-dev do not contain topics in their subjects, which makes this kind of filtering very ineffective. My proposal is to create an automated rule that rejects new emails, if they do not contain any topic in their subject. What do you guys think? Alternatively, separate mailing lists for each current topic area. A top-level mailing list could subscribe to all of them for anybody who truly wants the fire hose. Matt And so we create silos... :-) I would give a -1 to Roman's proposal but amend it : why not tagging them as [Nosubject] and filter them accordingly in our inboxes, ie. with low priority ? -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
On 12/05/2013 05:09 AM, Ronak Shah wrote: I like the proposal and I share the pain of checking for the important emails in the pile of all and potentially missing on some in timely fashion. My 2 cents on top of creating an automated rule: Most of the people (not all) I see on dev-list are active on either 1 or 2 project specific discussions. Why not create openstack-dev-project lists and have people subsribe to project list(s) that they are interested in. Biggest advantage I see with this approach is that one can actively participate by getting individual emails for the project mailing list that they are working on. In parallel they can opt for digest for rest of the project(s) where they act only in read-only mode. Thoughts? We already have that functionality with the Topics support in mailman. You can sign up for just specific topics there and only get those topics. Emails are tagged with an X-Topics: header for filtering (much more reliable than subject lines). For instance: X-Topics: Keystone If you only subscribe to some topics, anything that doesn't match those will not be delivered to you. So you assume everyone tags everything correctly (which they don't). So do so at your own peril. -Sean -- Sean Dague http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
On Thu, Dec 5, 2013 at 6:23 AM, Sean Dague s...@dague.net wrote: We already have that functionality with the Topics support in mailman. You can sign up for just specific topics there and only get those topics. Emails are tagged with an X-Topics: header for filtering (much more reliable than subject lines). This topic comes up regularly these days and this and another message from Stefano[1] are helpful to using topics so I've added it to the MailingList wiki page[2]. Plus pointers to split-the-list threads so we can maybe refresh on why things are the way they are. [1] http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html [2] https://wiki.openstack.org/wiki/Mailing_Lists#Future_Development dt -- Dean Troyer dtro...@gmail.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [policy] Let's make topics mandatory for openstack-dev
Dean Troyer wrote: On Thu, Dec 5, 2013 at 6:23 AM, Sean Dague s...@dague.net mailto:s...@dague.net wrote: We already have that functionality with the Topics support in mailman. You can sign up for just specific topics there and only get those topics. Emails are tagged with an X-Topics: header for filtering (much more reliable than subject lines). This topic comes up regularly these days and this and another message from Stefano[1] are helpful to using topics so I've added it to the MailingList wiki page[2]. Plus pointers to split-the-list threads so we can maybe refresh on why things are the way they are. [1] http://lists.openstack.org/pipermail/openstack-dev/2013-November/019233.html [2] https://wiki.openstack.org/wiki/Mailing_Lists#Future_Development Mailman Topics are good enough at this point -- the main issue with them is that if you fail to provide any topic with your email, mailman defaults to sending it to everyone... so people not following the topic rules actually get more visibility than people who do. I think we should just extend the use of sane subject lines and fight people who fail to provide a topic (if what they are posting is not of cross-project interest). As someone who proposed a basic split recently, I'll admit that adopting a more violent approach to ignoring threads based on their subject lines worked for me over the last weeks. The harder is to accept that you can't read everything. Once you do that, aggressively ignoring stuff you're less interested in is not that hard. -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
