[openstack-dev] [all][tc] Exposing project team's metadata in README files

Flavio Percoco flavio at redhat.com
Mon Nov 28 12:26:27 UTC 2016

On 27/11/16 23:54 +0100, Thomas Goirand wrote:
>On 10/12/2016 02:50 PM, Flavio Percoco wrote:
>> Greetings,
>> One of the common complains about the existing project organization in
>> the big
>> tent is that it's difficult to wrap our heads around the many projects
>> there
>> are, their current state (in/out the big tent), their tags, etc.
>> This information is available on the governance website[0]. Each official
>> project team has a page there containing the information related to the
>> deliverables managed by that team. Unfortunately, I don't think this
>> page is
>> checked often enough and I believe it's not known by everyone.
>> In the hope that we can make this information clearer to people browsing
>> the
>> many repos (most likely on github), I'd like to propose that we include the
>> information of each deliverable in the readme file. This information
>> would be
>> rendered along with the rest of the readme (at least on Github, which
>> might not
>> be our main repo but it's the place most humans go to to check our
>> projects).
>> Rather than duplicating this information, I'd like to find a way to just
>> "include it" in the Readme file. As far as showing the "official" badge
>> goes, I
>> believe it'd be quite simple. We can do it the same way CI tags are
>> exposed when
>> using travis (just include an image). As for the rest of the tags, it might
>> require some extra hacking.
>> So, before I start digging more into this, I wanted to get other
>> opinions/ideas
>> on this topic and how we can make this information more evident to the
>> rest of
>> the community (and people not as familiar with our processes as some of
>> us are).
>> Thanks in advance,
>> Flavio
>While your work seem a good idea to me, you may have been a bit too
>quick editing the deb-* repos. Let me explain.
>You've opened hundreds of change requests on the openstack/deb-* Gerrit
>repository. They are all failing the gate, which is expected.
>1/ These changes have nothing to do there, they are to be done on
>upstream code.
>2/ Never one should touch the master branch of these repositories (only
>debian/* are to be edited).
>Please abandon all of your changes for the deb-* Gerrit repos.
>Thanks for that work anyway,

Hey Thomas,

I actually wanted to reach out to you since I noticed the failures and I was
wondering what the right thing to do there is. Consider these patches abandoned
and thanks for reaching out. :)


>Thomas Goirand (zigo)
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 862 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161128/8a641f07/attachment.pgp>

More information about the OpenStack-dev mailing list