Open Stack

Hi Team - I was reading this over and wonder what you all think about trying to use the Contract tag for high priority User Story capabilities? Seems like a good cross-project way of indicating and linking dependencies.

Thanks
Carol

-----Original Message-----
From: Thierry Carrez [mailto:thierry at openstack.org] 
Sent: Monday, July 27, 2015 7:40 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [tc] [all] thinking additional tags

Thierry Carrez wrote:
> The "next tags" workgroup will be having a meeting this week on Friday 
> at 14:00 UTC in #openstack-meeting. Join us if you're interested !
> 
> In the mean time, we are braindumping at:
> https://etherpad.openstack.org/p/next-tags-wg

The work group met 10 days ago and decided to tackle tags in the following categories:

* Integration tags

Those describe whether the project is integrated with something else.
Sean Dague proposed to kick off this category with "devstack support"
tags, and proposed them at https://review.openstack.org/#/c/203785/

* Team tags

Team tags communicate whether the people behind a given project form a sustainable team. Russell Bryant agreed to draft tags about team size and team monoculture to further improve on our communication there.

* Contract tags

Contract tags are promises that project teams make about their deliverables. For example, I'll draft three tags describing feature/API deprecation policies that projects teams may opt to follow. These communicate clearly what to expect from a given project. In this same category, Zane Bitter will draft a tag about forward-compatible configuration files.

* QA tags

QA tags communicate what a given project actually tests. Does it do full stack testing, upgrade testing, partial upgrade testing ?

* Horizontal team support tags

These communicate which projects are directly supported by horizontal teams. We already have the "release:managed" tag and the "vulnerability:managed" tags to describe which projects are directly supported by the release management or the vulnerability management teams. I'll draft a tag to describe which projects have stable branches that follow the stable branch maintenance team policy.

Sorry for the late report,

--
Thierry Carrez (ttx)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev