[core-workflow] Tracker workflow proposal

Barry Warsaw barry at python.org
Mon Apr 21 20:43:30 CEST 2014


On Apr 21, 2014, at 12:04 PM, R. David Murray wrote:

>All of the other values are informational-only, and in some cases
>redundant.  If we want informational keywords, IMO we should do a full
>user-accessible tagging system.  That would be a separate proposal,
>though.

Launchpad has a nice approach here.   Tags are free-form and anybody can enter
whatever they want, but a particular project[*] can define "official" tags
that show up boldfaced when autocompleted.  It allows a project to assert that
certain tags have meaning to them, while preserving the freedom for more
global searches based on free-form tags.  Often, tags have a direct effect on
workflow process and tooling, e.g. duplicate-check-needed, fix-verified,
ci-passes, etc.

(And of course, any tag can be promoted to or demoted from being official.)

[*] I'm not sure the concept of per-project tags makes sense when we have a
tracker essentially devoted to a single project, but a global
official/unofficial designation on tags could still make sense.

Cheers,
-Barry


More information about the core-workflow mailing list