Let's use [dev] for development discussions
Hi openstack-discuss, As part of the ML merge, we introduced a number of subject prefixes to help subscribers filter discussions. The most important ones are to use: [dev] For discussions that are purely development-oriented [ops] For discussions that are purely operations-oriented Of course (as we have realized with the amount of cross-posted topics), most discussions benefit from input from all our contributors, whether they come from an development or an operational background. For those, there is no need to apply [dev] and/or [ops] prefixes, just try to be informative by adding the project name, team name or other information instead. You can ping specific populations by adding: [tc] Discussions of interest for TC members [uc] Discussions of interest for UC members [ptl] Discussions of interest for all PTLs [release] Release team, release liaisons and PTLs You can also specifically use (with care): [all] For discussions that should really be of interest to EVERYONE See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics Thanks for your help in making this common list more navigable. -- Thierry Carrez (ttx)
To be clearer, since I realize now my subject title (ironically) was a bit poor... The goal here is definitely to have common discussions around OpenStack between all contributors. But while most topics benefit from wide input, some are very specific, and applying appropriate subject prefixes will people efficiently filter the discussions they are the most interested about. Upgrading a version of pep8 has little user-visible impact, for example, and would benefit from being tagged [dev]. Cheers, -- Thierry Carrez (ttx)
I believe it is better to mention combined version of tags to clarify the intended usage. Even if a project specific topic, both [dev] and [ops] topics are possible. For nova development, do we use [dev] [nova] or simply [nova]? Some guidance would help subscribers. Thanks, Akihiro 2018年11月21日(水) 17:40 Thierry Carrez <thierry@openstack.org>:
Hi openstack-discuss,
As part of the ML merge, we introduced a number of subject prefixes to help subscribers filter discussions. The most important ones are to use:
[dev] For discussions that are purely development-oriented [ops] For discussions that are purely operations-oriented
Of course (as we have realized with the amount of cross-posted topics), most discussions benefit from input from all our contributors, whether they come from an development or an operational background. For those, there is no need to apply [dev] and/or [ops] prefixes, just try to be informative by adding the project name, team name or other information instead.
You can ping specific populations by adding:
[tc] Discussions of interest for TC members [uc] Discussions of interest for UC members [ptl] Discussions of interest for all PTLs [release] Release team, release liaisons and PTLs
You can also specifically use (with care):
[all] For discussions that should really be of interest to EVERYONE
See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics
Thanks for your help in making this common list more navigable.
-- Thierry Carrez (ttx)
Akihiro Motoki wrote:
I believe it is better to mention combined version of tags to clarify the intended usage. Even if a project specific topic, both [dev] and [ops] topics are possible. For nova development, do we use [dev] [nova] or simply [nova]?
Personally I would only use [dev] if the topic is *only* of interest to contributors coming from a more developer-oriented angle. Extreme examples: [dev][nova] Enabling py37 unit tests in gate [nova] Can we deprecate the server backup API?
Some guidance would help subscribers.
It might be a bit early to emit stronger guidance. I suspect usage will drive the norm... -- Thierry Carrez (ttx)
Thierry Carrez <thierry@openstack.org> writes:
Hi openstack-discuss,
As part of the ML merge, we introduced a number of subject prefixes to help subscribers filter discussions. The most important ones are to use:
[dev] For discussions that are purely development-oriented [ops] For discussions that are purely operations-oriented
Of course (as we have realized with the amount of cross-posted topics), most discussions benefit from input from all our contributors, whether they come from an development or an operational background. For those, there is no need to apply [dev] and/or [ops] prefixes, just try to be informative by adding the project name, team name or other information instead.
You can ping specific populations by adding:
[tc] Discussions of interest for TC members [uc] Discussions of interest for UC members [ptl] Discussions of interest for all PTLs [release] Release team, release liaisons and PTLs
You can also specifically use (with care):
[all] For discussions that should really be of interest to EVERYONE
See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics
Thanks for your help in making this common list more navigable.
-- Thierry Carrez (ttx)
Should we start moving this information into the project team guide? -- Doug
On 2018-11-21 09:47:18 -0500 (-0500), Doug Hellmann wrote:
Thierry Carrez <thierry@openstack.org> writes: [...]
See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics
Thanks for your help in making this common list more navigable.
Should we start moving this information into the project team guide?
That was the plan, I just wanted to give people a little more time to add things they thought were relevant before we up the bar for additions to submitting them as code-reviewed changes. The Project Teams Guide seems like the most appropriate place for it (with a link added in the listserv's description text). -- Jeremy Stanley
Jeremy Stanley <fungi@yuggoth.org> writes:
On 2018-11-21 09:47:18 -0500 (-0500), Doug Hellmann wrote:
Thierry Carrez <thierry@openstack.org> writes: [...]
See (and add!) other common subject prefixes at: https://etherpad.openstack.org/p/common-openstack-ml-topics
Thanks for your help in making this common list more navigable.
Should we start moving this information into the project team guide?
That was the plan, I just wanted to give people a little more time to add things they thought were relevant before we up the bar for additions to submitting them as code-reviewed changes. The Project Teams Guide seems like the most appropriate place for it (with a link added in the listserv's description text). -- Jeremy Stanley
Sounds good. Feel free to add me as a reviewer to help land the patch. -- Doug
participants (5)
-
Akihiro Motoki
-
Doug Hellmann
-
Jay Pipes
-
Jeremy Stanley
-
Thierry Carrez