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

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

2017-01-10 Thread Flavio Percoco


On 09/01/17 19:39 +0200, Andrey Kurilin wrote:

On Mon, Jan 9, 2017 at 6:37 PM, Flavio Percoco  wrote:


On 09/01/17 17:55 +0200, Andrey Kurilin wrote:


Hi, Flavio!

Does it possible to create badges per project release?



mmh, it's currently not possible.

Could you elaborate on why you need a specific tag per release? IS it to
tag the
releases that were done after the inclusion in the big tent?



OpenStack has a bunch of different tags. "the inclusion in the big tent" is
one of tags that should not match to all project releases once project did
it.
Another one is a "single-vendor" and so on. I think most of tags should be
applied per project release.


Why do you think it shouldn't match all the releases? Tags like single-vendor
and official impact all the releases regardless what the status was when the
release was cut.


One more "feature request": creation of custom badges(I'm interested in
"tested on %(operation_system)s".



mmh, this will have to be implemented elsewhere since these badges are specific
for governance tags[0]. I'd recommend using shields[1] for this.

Flavio

[0] http://governance.openstack.org/reference/tags/index.html
[1] http://shields.io/




Flavio


On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco  wrote:


Just a heads up!


There are still unmerged patches on this effort. If you have a couple of
spare
brain cycles, it'd be awesome to get the patches relative to the projects
you've
+2 votes on in.

I'll proceed to abandon remaining patches in 2 weeks from now assuming
that
projects are not interested in having them. As I mentioned in previous
emails,
you're free to update the patches to match your project needs.

Here's the link to see the remaining patches:
https://review.openstack.org/#/q/status:open+topic:project-badges

Thanks a lot,
Flavio


On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco





--
@flaper87
Flavio Percoco


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.op
enstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





--
Best regards,
Andrey Kurilin.



__

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
e
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
@flaper87
Flavio Percoco

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





--
Best regards,
Andrey Kurilin.



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



--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:

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

2017-01-09 Thread Andrey Kurilin

On Mon, Jan 9, 2017 at 6:37 PM, Flavio Percoco  wrote:

> On 09/01/17 17:55 +0200, Andrey Kurilin wrote:
>
>> Hi, Flavio!
>>
>> Does it possible to create badges per project release?
>>
>
> mmh, it's currently not possible.
>
> Could you elaborate on why you need a specific tag per release? IS it to
> tag the
> releases that were done after the inclusion in the big tent?
>
>
OpenStack has a bunch of different tags. "the inclusion in the big tent" is
one of tags that should not match to all project releases once project did
it.
Another one is a "single-vendor" and so on. I think most of tags should be
applied per project release.

One more "feature request": creation of custom badges(I'm interested in
"tested on %(operation_system)s".

> Flavio
>
>
> On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco  wrote:
>>
>> Just a heads up!
>>>
>>> There are still unmerged patches on this effort. If you have a couple of
>>> spare
>>> brain cycles, it'd be awesome to get the patches relative to the projects
>>> you've
>>> +2 votes on in.
>>>
>>> I'll proceed to abandon remaining patches in 2 weeks from now assuming
>>> that
>>> projects are not interested in having them. As I mentioned in previous
>>> emails,
>>> you're free to update the patches to match your project needs.
>>>
>>> Here's the link to see the remaining patches:
>>> https://review.openstack.org/#/q/status:open+topic:project-badges
>>>
>>> Thanks a lot,
>>> Flavio
>>>
>>>
>>> On 12/10/16 14:50 +0200, 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

 [0] http://governance.openstack.org/reference/projects/index.html

 --
 @flaper87
 Flavio Percoco

>>>
>>>
>>> --
>>> @flaper87
>>> Flavio Percoco
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>
>> --
>> Best regards,
>> Andrey Kurilin.
>>
>
> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> --
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 
Best regards,
Andrey Kurilin.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2017-01-09 Thread Flavio Percoco


On 09/01/17 17:55 +0200, Andrey Kurilin wrote:

Hi, Flavio!

Does it possible to create badges per project release?


mmh, it's currently not possible.

Could you elaborate on why you need a specific tag per release? IS it to tag the
releases that were done after the inclusion in the big tent?

Flavio


On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco  wrote:


Just a heads up!

There are still unmerged patches on this effort. If you have a couple of
spare
brain cycles, it'd be awesome to get the patches relative to the projects
you've
+2 votes on in.

I'll proceed to abandon remaining patches in 2 weeks from now assuming that
projects are not interested in having them. As I mentioned in previous
emails,
you're free to update the patches to match your project needs.

Here's the link to see the remaining patches:
https://review.openstack.org/#/q/status:open+topic:project-badges

Thanks a lot,
Flavio


On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco





--
@flaper87
Flavio Percoco

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





--
Best regards,
Andrey Kurilin.



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



--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2017-01-09 Thread Andrey Kurilin

Hi, Flavio!

Does it possible to create badges per project release?

On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco  wrote:

> Just a heads up!
>
> There are still unmerged patches on this effort. If you have a couple of
> spare
> brain cycles, it'd be awesome to get the patches relative to the projects
> you've
> +2 votes on in.
>
> I'll proceed to abandon remaining patches in 2 weeks from now assuming that
> projects are not interested in having them. As I mentioned in previous
> emails,
> you're free to update the patches to match your project needs.
>
> Here's the link to see the remaining patches:
> https://review.openstack.org/#/q/status:open+topic:project-badges
>
> Thanks a lot,
> Flavio
>
>
> On 12/10/16 14:50 +0200, 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
>>
>> [0] http://governance.openstack.org/reference/projects/index.html
>>
>> --
>> @flaper87
>> Flavio Percoco
>>
>
>
>
> --
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best regards,
Andrey Kurilin.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2017-01-09 Thread Flavio Percoco


Just a heads up!

There are still unmerged patches on this effort. If you have a couple of spare
brain cycles, it'd be awesome to get the patches relative to the projects you've
+2 votes on in.

I'll proceed to abandon remaining patches in 2 weeks from now assuming that
projects are not interested in having them. As I mentioned in previous emails,
you're free to update the patches to match your project needs.

Here's the link to see the remaining patches:
https://review.openstack.org/#/q/status:open+topic:project-badges

Thanks a lot,
Flavio


On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-12-01 Thread Flavio Percoco

On 30/11/16 08:53 -0800, Michael Johnson wrote:

Hi Flavio,

These tags don't seem to be rendering/laying out well for octavia:
https://github.com/openstack/octavia/blob/master/README.rst

Any pointers to get this corrected or is this part of the backend
rendering work you mentioned in the keystone message above?

This was a bug in the SVG generation. The TL;DR is that the height and width
were not being set for the root SVG. It should now be fixed.

Note that github caches images locally. I wrote a script to purge the cache for
all the badges that have landed already and I've added a cache control rules to
the vhost serving these files now. Once this lands, I'll try purging the cache
from GH again and hopefully it'll stop caching these images, which are not meant
to be cached forever.

https://review.openstack.org/#/c/404683/

If you need to purge the cache yourself, you can do it by issuing this command:

$ curl -x PURGE $THE_GITHUB_IMAGE_URL

Hope this helps,
Flavio

Michael

On Wed, Nov 30, 2016 at 1:34 AM, Flavio Percoco <fla...@redhat.com> wrote:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project but I
find
that at least the ones that were landed for Trove, and a random sampling
of
the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or the
first,
and most prominent heading, would be the existing heading of the document,
and
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.

Hi,

Some fixes landed yesterday to improve the badges layout. For those
interested,
here's an example of what it looks like now:

https://github.com/openstack/keystone

Basically, the horizontal padding was reduced to the minimum needed and the
badges width was set to the total width of the image.

Hope this helps,
Flavio

What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous header, and
the
header "Trove" below that.

In some cases the second header is the same font as the "Team and
repository
tags" header.

I think this change (these 124 changes) as proposed are not consistent
with
the proposal you made below, and certainly seem to be less suitable than
that
proposal. The end product for the four trove repositories [4], [5], [6],
and
[7]

I think we should have a discussion on the ML whether we feel that this
new
structure is the appropriate one, and before some projects approve these
changes and others don't that these be all marked WF-1.

Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata
in
README files

On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> 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 t

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

2016-11-30 Thread Armando M.

On 30 November 2016 at 12:16, Steve Martinelli <s.martine...@gmail.com>
wrote:

> This happened to us for keystone-specs [1]. I settled on removing the
> reference to the README.rst from the doc folder. You can do the same by
> removing [2].
>
> [1] https://review.openstack.org/#/c/402878/
> [2] https://github.com/openstack/neutron-lib/blob/
> master/doc/source/readme.rst
>

Thanks Steve, we'll follow suit!

Cheers,
Armando


>
> On Wed, Nov 30, 2016 at 2:44 PM, Armando M. <arma...@gmail.com> wrote:
>
>>
>>
>> On 30 November 2016 at 08:53, Michael Johnson <johnso...@gmail.com>
>> wrote:
>>
>>> Hi Flavio,
>>>
>>> These tags don't seem to be rendering/laying out well for octavia:
>>> https://github.com/openstack/octavia/blob/master/README.rst
>>>
>>> Any pointers to get this corrected or is this part of the backend
>>> rendering work you mentioned in the keystone message above?
>>>
>>>
>> Actually I just noticed that this may break building docs locally for
>> some envs as I now get in my env:
>>
>> Warning, treated as error:
>> README.rst:None: WARNING: nonlocal image URI found:
>> http://governance.openstack.org/badges/neutron-lib.svg
>>
>> I was aware of [1], and I am unsure on the next steps. Can some advise?
>>
>> Thanks,
>> Armando
>>
>> [1] https://review.openstack.org/#/c/229951/
>>
>>
>>> Michael
>>>
>>> On Wed, Nov 30, 2016 at 1:34 AM, Flavio Percoco <fla...@redhat.com>
>>> wrote:
>>> > On 25/11/16 13:46 +, Amrith Kumar wrote:
>>> >>
>>> >> Flavio,
>>> >>
>>> >> I see a number of patches[1] which have been landed on this project
>>> but I
>>> >> find
>>> >> that at least the ones that were landed for Trove, and a random
>>> sampling
>>> >> of
>>> >> the others all to be different from what you proposed below[2] in one
>>> >> important aspect.
>>> >>
>>> >> In [2] you proposed a structure where the title of the document; or
>>> the
>>> >> first,
>>> >> and most prominent heading, would be the existing heading of the
>>> document,
>>> >> and
>>> >> the tags would be below that. In [2] for example, that was:
>>> >>
>>> >> "kombu - Messaging library for Python"
>>> >>
>>> >> and the tags would be in smaller font below that.
>>> >
>>> >
>>> > Hi,
>>> >
>>> > Some fixes landed yesterday to improve the badges layout. For those
>>> > interested,
>>> > here's an example of what it looks like now:
>>> >
>>> > https://github.com/openstack/keystone
>>> >
>>> > Basically, the horizontal padding was reduced to the minimum needed
>>> and the
>>> > badges width was set to the total width of the image.
>>> >
>>> > Hope this helps,
>>> > Flavio
>>> >
>>> >
>>> >> What I see in [3] the patch for Trove and the proposed example [4] is:
>>> >>
>>> >> "Team and repository tags" as the first, and most conspicuous header,
>>> and
>>> >> the
>>> >> header "Trove" below that.
>>> >>
>>> >> In some cases the second header is the same font as the "Team and
>>> >> repository
>>> >> tags" header.
>>> >>
>>> >> I think this change (these 124 changes) as proposed are not consistent
>>> >> with
>>> >> the proposal you made below, and certainly seem to be less suitable
>>> than
>>> >> that
>>> >> proposal. The end product for the four trove repositories [4], [5],
>>> [6],
>>> >> and
>>> >> [7]
>>> >>
>>> >> I think we should have a discussion on the ML whether we feel that
>>> this
>>> >> new
>>> >> structure is the appropriate one, and before some projects approve
>>> these
>>> >> changes and others don't that these be all marked WF-1.
>>> >>
>>> >> Thanks,
>>> >>
>>> >> -amrith
>>> >>
>>> >> [1] https://review.openstack.org/#/q/topic:project-badges
>>> >> [2] https://github.com/cele

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

2016-11-30 Thread Steve Martinelli

This happened to us for keystone-specs [1]. I settled on removing the
reference to the README.rst from the doc folder. You can do the same by
removing [2].

[1] https://review.openstack.org/#/c/402878/
[2]
https://github.com/openstack/neutron-lib/blob/master/doc/source/readme.rst

On Wed, Nov 30, 2016 at 2:44 PM, Armando M. <arma...@gmail.com> wrote:

>
>
> On 30 November 2016 at 08:53, Michael Johnson <johnso...@gmail.com> wrote:
>
>> Hi Flavio,
>>
>> These tags don't seem to be rendering/laying out well for octavia:
>> https://github.com/openstack/octavia/blob/master/README.rst
>>
>> Any pointers to get this corrected or is this part of the backend
>> rendering work you mentioned in the keystone message above?
>>
>>
> Actually I just noticed that this may break building docs locally for some
> envs as I now get in my env:
>
> Warning, treated as error:
> README.rst:None: WARNING: nonlocal image URI found:
> http://governance.openstack.org/badges/neutron-lib.svg
>
> I was aware of [1], and I am unsure on the next steps. Can some advise?
>
> Thanks,
> Armando
>
> [1] https://review.openstack.org/#/c/229951/
>
>
>> Michael
>>
>> On Wed, Nov 30, 2016 at 1:34 AM, Flavio Percoco <fla...@redhat.com>
>> wrote:
>> > On 25/11/16 13:46 +, Amrith Kumar wrote:
>> >>
>> >> Flavio,
>> >>
>> >> I see a number of patches[1] which have been landed on this project
>> but I
>> >> find
>> >> that at least the ones that were landed for Trove, and a random
>> sampling
>> >> of
>> >> the others all to be different from what you proposed below[2] in one
>> >> important aspect.
>> >>
>> >> In [2] you proposed a structure where the title of the document; or the
>> >> first,
>> >> and most prominent heading, would be the existing heading of the
>> document,
>> >> and
>> >> the tags would be below that. In [2] for example, that was:
>> >>
>> >> "kombu - Messaging library for Python"
>> >>
>> >> and the tags would be in smaller font below that.
>> >
>> >
>> > Hi,
>> >
>> > Some fixes landed yesterday to improve the badges layout. For those
>> > interested,
>> > here's an example of what it looks like now:
>> >
>> > https://github.com/openstack/keystone
>> >
>> > Basically, the horizontal padding was reduced to the minimum needed and
>> the
>> > badges width was set to the total width of the image.
>> >
>> > Hope this helps,
>> > Flavio
>> >
>> >
>> >> What I see in [3] the patch for Trove and the proposed example [4] is:
>> >>
>> >> "Team and repository tags" as the first, and most conspicuous header,
>> and
>> >> the
>> >> header "Trove" below that.
>> >>
>> >> In some cases the second header is the same font as the "Team and
>> >> repository
>> >> tags" header.
>> >>
>> >> I think this change (these 124 changes) as proposed are not consistent
>> >> with
>> >> the proposal you made below, and certainly seem to be less suitable
>> than
>> >> that
>> >> proposal. The end product for the four trove repositories [4], [5],
>> [6],
>> >> and
>> >> [7]
>> >>
>> >> I think we should have a discussion on the ML whether we feel that this
>> >> new
>> >> structure is the appropriate one, and before some projects approve
>> these
>> >> changes and others don't that these be all marked WF-1.
>> >>
>> >> Thanks,
>> >>
>> >> -amrith
>> >>
>> >> [1] https://review.openstack.org/#/q/topic:project-badges
>> >> [2] https://github.com/celery/kombu/blob/master/README.rst
>> >> [3] https://review.openstack.org/#/c/402547/
>> >> [4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
>> >> [5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
>> >> [6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
>> >> [7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258
>> >>
>> >>
>> >>
>> >>
>> >>> -Original Message-
>> >>> From: Flavio Percoco [mailto:fla...@redhat.com]
>> >>> Sent: Thurs

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

2016-11-30 Thread Armando M.

On 30 November 2016 at 08:53, Michael Johnson <johnso...@gmail.com> wrote:

> Hi Flavio,
>
> These tags don't seem to be rendering/laying out well for octavia:
> https://github.com/openstack/octavia/blob/master/README.rst
>
> Any pointers to get this corrected or is this part of the backend
> rendering work you mentioned in the keystone message above?
>
>
Actually I just noticed that this may break building docs locally for some
envs as I now get in my env:

Warning, treated as error:
README.rst:None: WARNING: nonlocal image URI found:
http://governance.openstack.org/badges/neutron-lib.svg

I was aware of [1], and I am unsure on the next steps. Can some advise?

Thanks,
Armando

[1] https://review.openstack.org/#/c/229951/


> Michael
>
> On Wed, Nov 30, 2016 at 1:34 AM, Flavio Percoco <fla...@redhat.com> wrote:
> > On 25/11/16 13:46 +, Amrith Kumar wrote:
> >>
> >> Flavio,
> >>
> >> I see a number of patches[1] which have been landed on this project but
> I
> >> find
> >> that at least the ones that were landed for Trove, and a random sampling
> >> of
> >> the others all to be different from what you proposed below[2] in one
> >> important aspect.
> >>
> >> In [2] you proposed a structure where the title of the document; or the
> >> first,
> >> and most prominent heading, would be the existing heading of the
> document,
> >> and
> >> the tags would be below that. In [2] for example, that was:
> >>
> >> "kombu - Messaging library for Python"
> >>
> >> and the tags would be in smaller font below that.
> >
> >
> > Hi,
> >
> > Some fixes landed yesterday to improve the badges layout. For those
> > interested,
> > here's an example of what it looks like now:
> >
> > https://github.com/openstack/keystone
> >
> > Basically, the horizontal padding was reduced to the minimum needed and
> the
> > badges width was set to the total width of the image.
> >
> > Hope this helps,
> > Flavio
> >
> >
> >> What I see in [3] the patch for Trove and the proposed example [4] is:
> >>
> >> "Team and repository tags" as the first, and most conspicuous header,
> and
> >> the
> >> header "Trove" below that.
> >>
> >> In some cases the second header is the same font as the "Team and
> >> repository
> >> tags" header.
> >>
> >> I think this change (these 124 changes) as proposed are not consistent
> >> with
> >> the proposal you made below, and certainly seem to be less suitable than
> >> that
> >> proposal. The end product for the four trove repositories [4], [5], [6],
> >> and
> >> [7]
> >>
> >> I think we should have a discussion on the ML whether we feel that this
> >> new
> >> structure is the appropriate one, and before some projects approve these
> >> changes and others don't that these be all marked WF-1.
> >>
> >> Thanks,
> >>
> >> -amrith
> >>
> >> [1] https://review.openstack.org/#/q/topic:project-badges
> >> [2] https://github.com/celery/kombu/blob/master/README.rst
> >> [3] https://review.openstack.org/#/c/402547/
> >> [4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
> >> [5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
> >> [6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
> >> [7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258
> >>
> >>
> >>
> >>
> >>> -Original Message-
> >>> From: Flavio Percoco [mailto:fla...@redhat.com]
> >>> Sent: Thursday, October 13, 2016 7:07 AM
> >>> To: OpenStack Development Mailing List (not for usage questions)
> >>> <openstack-dev@lists.openstack.org>
> >>> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata
> >>> in
> >>> README files
> >>>
> >>> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
> >>> >Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> >>> >> 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
>

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

2016-11-30 Thread Michael Johnson

Hi Flavio,

These tags don't seem to be rendering/laying out well for octavia:
https://github.com/openstack/octavia/blob/master/README.rst

Any pointers to get this corrected or is this part of the backend
rendering work you mentioned in the keystone message above?

Michael

On Wed, Nov 30, 2016 at 1:34 AM, Flavio Percoco <fla...@redhat.com> wrote:
> On 25/11/16 13:46 +, Amrith Kumar wrote:
>>
>> Flavio,
>>
>> I see a number of patches[1] which have been landed on this project but I
>> find
>> that at least the ones that were landed for Trove, and a random sampling
>> of
>> the others all to be different from what you proposed below[2] in one
>> important aspect.
>>
>> In [2] you proposed a structure where the title of the document; or the
>> first,
>> and most prominent heading, would be the existing heading of the document,
>> and
>> the tags would be below that. In [2] for example, that was:
>>
>> "kombu - Messaging library for Python"
>>
>> and the tags would be in smaller font below that.
>
>
> Hi,
>
> Some fixes landed yesterday to improve the badges layout. For those
> interested,
> here's an example of what it looks like now:
>
> https://github.com/openstack/keystone
>
> Basically, the horizontal padding was reduced to the minimum needed and the
> badges width was set to the total width of the image.
>
> Hope this helps,
> Flavio
>
>
>> What I see in [3] the patch for Trove and the proposed example [4] is:
>>
>> "Team and repository tags" as the first, and most conspicuous header, and
>> the
>> header "Trove" below that.
>>
>> In some cases the second header is the same font as the "Team and
>> repository
>> tags" header.
>>
>> I think this change (these 124 changes) as proposed are not consistent
>> with
>> the proposal you made below, and certainly seem to be less suitable than
>> that
>> proposal. The end product for the four trove repositories [4], [5], [6],
>> and
>> [7]
>>
>> I think we should have a discussion on the ML whether we feel that this
>> new
>> structure is the appropriate one, and before some projects approve these
>> changes and others don't that these be all marked WF-1.
>>
>> Thanks,
>>
>> -amrith
>>
>> [1] https://review.openstack.org/#/q/topic:project-badges
>> [2] https://github.com/celery/kombu/blob/master/README.rst
>> [3] https://review.openstack.org/#/c/402547/
>> [4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
>> [5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
>> [6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
>> [7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258
>>
>>
>>
>>
>>> -Original Message-
>>> From: Flavio Percoco [mailto:fla...@redhat.com]
>>> Sent: Thursday, October 13, 2016 7:07 AM
>>> To: OpenStack Development Mailing List (not for usage questions)
>>> <openstack-dev@lists.openstack.org>
>>> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata
>>> in
>>> README files
>>>
>>> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>>> >Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>>> >> 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

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

2016-11-30 Thread Ben Nemec




On 11/30/2016 10:39 AM, Steve Martinelli wrote:

Refresh (not from cache)?


Ugh, yeah that was it.  Sorry for the noise.



On Wed, Nov 30, 2016 at 11:23 AM, Ben Nemec > wrote:



On 11/30/2016 10:19 AM, Jason Rist wrote:

On 11/30/2016 11:18 AM, Ben Nemec wrote:



On 11/30/2016 03:34 AM, Flavio Percoco wrote:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed
on this project
but I find
that at least the ones that were landed for Trove,
and a random
sampling of
the others all to be different from what you
proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of
the document; or
the first,
and most prominent heading, would be the existing
heading of the
document, and
the tags would be below that. In [2] for example,
that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.


Hi,

Some fixes landed yesterday to improve the badges
layout. For those
interested,
here's an example of what it looks like now:

https://github.com/openstack/keystone


Basically, the horizontal padding was reduced to the
minimum needed
and the
badges width was set to the total width of the image.


Any idea why there is so much vertical whitespace after the
badges in
https://github.com/openstack/instack-undercloud
 ?  It's
all clickable so
I'm thinking it must be coming from the badge image for some
reason.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


How much is 'so much'? I see at most 50 pixels?


Strange, I see almost 200 pixels.  I also don't see the same thing
on the keystone readme Flavio linked.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





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



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

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

2016-11-30 Thread Steve Martinelli

Refresh (not from cache)?

On Wed, Nov 30, 2016 at 11:23 AM, Ben Nemec  wrote:

>
>
> On 11/30/2016 10:19 AM, Jason Rist wrote:
>
>> On 11/30/2016 11:18 AM, Ben Nemec wrote:
>>
>>>
>>>
>>> On 11/30/2016 03:34 AM, Flavio Percoco wrote:
>>>
 On 25/11/16 13:46 +, Amrith Kumar wrote:

> Flavio,
>
> I see a number of patches[1] which have been landed on this project
> but I find
> that at least the ones that were landed for Trove, and a random
> sampling of
> the others all to be different from what you proposed below[2] in one
> important aspect.
>
> In [2] you proposed a structure where the title of the document; or
> the first,
> and most prominent heading, would be the existing heading of the
> document, and
> the tags would be below that. In [2] for example, that was:
>
> "kombu - Messaging library for Python"
>
> and the tags would be in smaller font below that.
>

 Hi,

 Some fixes landed yesterday to improve the badges layout. For those
 interested,
 here's an example of what it looks like now:

 https://github.com/openstack/keystone

 Basically, the horizontal padding was reduced to the minimum needed
 and the
 badges width was set to the total width of the image.

>>>
>>> Any idea why there is so much vertical whitespace after the badges in
>>> https://github.com/openstack/instack-undercloud ?  It's all clickable so
>>> I'm thinking it must be coming from the badge image for some reason.
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> How much is 'so much'? I see at most 50 pixels?
>>
>>
> Strange, I see almost 200 pixels.  I also don't see the same thing on the
> keystone readme Flavio linked.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-30 Thread Jason Rist

On 11/30/2016 11:18 AM, Ben Nemec wrote:
>
>
> On 11/30/2016 03:34 AM, Flavio Percoco wrote:
> > On 25/11/16 13:46 +, Amrith Kumar wrote:
> >> Flavio,
> >>
> >> I see a number of patches[1] which have been landed on this project
> >> but I find
> >> that at least the ones that were landed for Trove, and a random
> >> sampling of
> >> the others all to be different from what you proposed below[2] in one
> >> important aspect.
> >>
> >> In [2] you proposed a structure where the title of the document; or
> >> the first,
> >> and most prominent heading, would be the existing heading of the
> >> document, and
> >> the tags would be below that. In [2] for example, that was:
> >>
> >> "kombu - Messaging library for Python"
> >>
> >> and the tags would be in smaller font below that.
> >
> > Hi,
> >
> > Some fixes landed yesterday to improve the badges layout. For those
> > interested,
> > here's an example of what it looks like now:
> >
> > https://github.com/openstack/keystone
> >
> > Basically, the horizontal padding was reduced to the minimum needed
> > and the
> > badges width was set to the total width of the image.
>
> Any idea why there is so much vertical whitespace after the badges in
> https://github.com/openstack/instack-undercloud ?  It's all clickable so
> I'm thinking it must be coming from the badge image for some reason.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
How much is 'so much'? I see at most 50 pixels?

-- 
Jason E. Rist
Senior Software Engineer
OpenStack User Interfaces
Red Hat, Inc.
Freenode: jrist
github/twitter: knowncitizen

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

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

2016-11-30 Thread Ben Nemec




On 11/30/2016 10:19 AM, Jason Rist wrote:

On 11/30/2016 11:18 AM, Ben Nemec wrote:



On 11/30/2016 03:34 AM, Flavio Percoco wrote:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project
but I find
that at least the ones that were landed for Trove, and a random
sampling of
the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or
the first,
and most prominent heading, would be the existing heading of the
document, and
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.


Hi,

Some fixes landed yesterday to improve the badges layout. For those
interested,
here's an example of what it looks like now:

https://github.com/openstack/keystone

Basically, the horizontal padding was reduced to the minimum needed
and the
badges width was set to the total width of the image.


Any idea why there is so much vertical whitespace after the badges in
https://github.com/openstack/instack-undercloud ?  It's all clickable so
I'm thinking it must be coming from the badge image for some reason.

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

How much is 'so much'? I see at most 50 pixels?



Strange, I see almost 200 pixels.  I also don't see the same thing on 
the keystone readme Flavio linked.


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

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

2016-11-30 Thread Ben Nemec




On 11/30/2016 03:34 AM, Flavio Percoco wrote:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project
but I find
that at least the ones that were landed for Trove, and a random
sampling of
the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or
the first,
and most prominent heading, would be the existing heading of the
document, and
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.


Hi,

Some fixes landed yesterday to improve the badges layout. For those
interested,
here's an example of what it looks like now:

https://github.com/openstack/keystone

Basically, the horizontal padding was reduced to the minimum needed and the
badges width was set to the total width of the image.


Any idea why there is so much vertical whitespace after the badges in 
https://github.com/openstack/instack-undercloud ?  It's all clickable so 
I'm thinking it must be coming from the badge image for some reason.


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

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

2016-11-30 Thread Flavio Percoco

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project but I find
that at least the ones that were landed for Trove, and a random sampling of
the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or the first,
and most prominent heading, would be the existing heading of the document, and
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.

Hi,

Some fixes landed yesterday to improve the badges layout. For those interested,
here's an example of what it looks like now:

https://github.com/openstack/keystone

Basically, the horizontal padding was reduced to the minimum needed and the
badges width was set to the total width of the image.

Hope this helps,
Flavio

What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous header, and the
header "Trove" below that.

In some cases the second header is the same font as the "Team and repository
tags" header.

I think this change (these 124 changes) as proposed are not consistent with
the proposal you made below, and certainly seem to be less suitable than that
proposal. The end product for the four trove repositories [4], [5], [6], and
[7]

I think we should have a discussion on the ML whether we feel that this new
structure is the appropriate one, and before some projects approve these
changes and others don't that these be all marked WF-1.

Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
README files

On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> 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
>>
>> [0] http://governance.openstack.org/reference/projects/index.html
>>
>
>Is your proposal that a tag like release:cycle-with-milestones would
>result in a badge being added when the README.rst is rendered on
>github.com? Would that work for git.openstack.org, too?

I don't think it'd work for git.openstack.org because it doesn't render the
README's[0] like github does. One thing I'd like to avoid is for this
information to result in new changes to the README file everytime the tags
are updated because I'd like for this information to not be duplicated and
to
make it clear that this informati

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

2016-11-28 Thread Flavio Percoco


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


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,
Cheers,



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. :)

Flavio


Thomas Goirand (zigo)


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


--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-28 Thread Flavio Percoco


On 28/11/16 03:31 +, joehuang wrote:

Hello, Flavio,

Thank you to move this forward. Is it possible to put the badges at the bottom 
of README.rst file? Just from the code contributors point of view.



Hi :D

You're free to move it at the bottom if that's the preference for your project.
There's no restriction as to where the tags should be, although I'd prefer
readme's to be consistent.

They are not and I think it'll be hard to make them consistent in this round,
Thanks a bunch,
Flavio


Best Regards
Chaoyi Huang (joehuang)


From: Flavio Percoco [fla...@redhat.com]
Sent: 25 November 2016 20:26
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in  
README files

On 25/11/16 13:16 +0100, Flavio Percoco wrote:

On 25/11/16 12:38 +0100, Flavio Percoco wrote:

Greetings,

Just a heads up for everyone. The work on this front has moved forward and the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite obvious, the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of "viral
changes" but I've done my best to explain what's changing, provide references
and examples on the commit message. These changes are being submitted using the
tag 'project-badges'[2].


I also wanted to add that these patches are just for projects that are using rst
for their README files (sorry markdown) and that each commit has a preview link
that you can go and look at.

If the layout doesn't look perfect and the whitespace under the svg image
annoyes you, let me tell you that it was improved in the new layout, which is
under review. Also, Github does some funky things to the svg when it renders the
README file, hence the whitespace that was added for the first layout.


One last thing. You may/may not like the placement of these badges in the README
file. It's fine if you don't. The reason they are at the top is because they
normally are at the top :) Putting them at the top also made it simple to
automate the process accross all the *very* (trust me VERY) different README
files across the community.

If you don't like the placement of these badges, you're free to move them around
as prefer. I've done the job to help pushing the first patch, you're all free to
take it over, modify it, reject it or just merge it as is.

Hope this helps,
Flavio


Flavio


Note that these badges are *JUST* a graphical representation of what's in the
governance repo. If you don't want to have them in the README file, I guess it's
fine. I'd, however, encourage everyone to add them to provide consistency and a
more immediate information of what the project is about, what some of the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well but I'll
leave that to every team to do.

Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better ideas please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/

On 12/10/16 14:50 +0200, 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

[0] http://gove

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

2016-11-27 Thread joehuang

Hello, Flavio,

Thank you to move this forward. Is it possible to put the badges at the bottom 
of README.rst file? Just from the code contributors point of view.

Best Regards
Chaoyi Huang (joehuang)


From: Flavio Percoco [fla...@redhat.com]
Sent: 25 November 2016 20:26
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in  
README files

On 25/11/16 13:16 +0100, Flavio Percoco wrote:
>On 25/11/16 12:38 +0100, Flavio Percoco wrote:
>>Greetings,
>>
>>Just a heads up for everyone. The work on this front has moved forward and the
>>badges are now being generated as part of the governance CI[0].
>>
>>You can find the list of badges here[1] and the pattern is quite obvious, the
>>name of the image is based on the project repo name.
>>
>>I've edited the README files for all repositories listed in the projects.yaml
>>file and I've started to submit these patches[2]. I'm not a fan of "viral
>>changes" but I've done my best to explain what's changing, provide references
>>and examples on the commit message. These changes are being submitted using 
>>the
>>tag 'project-badges'[2].
>
>I also wanted to add that these patches are just for projects that are using 
>rst
>for their README files (sorry markdown) and that each commit has a preview link
>that you can go and look at.
>
>If the layout doesn't look perfect and the whitespace under the svg image
>annoyes you, let me tell you that it was improved in the new layout, which is
>under review. Also, Github does some funky things to the svg when it renders 
>the
>README file, hence the whitespace that was added for the first layout.

One last thing. You may/may not like the placement of these badges in the README
file. It's fine if you don't. The reason they are at the top is because they
normally are at the top :) Putting them at the top also made it simple to
automate the process accross all the *very* (trust me VERY) different README
files across the community.

If you don't like the placement of these badges, you're free to move them around
as prefer. I've done the job to help pushing the first patch, you're all free to
take it over, modify it, reject it or just merge it as is.

Hope this helps,
Flavio

>Flavio
>
>>Note that these badges are *JUST* a graphical representation of what's in the
>>governance repo. If you don't want to have them in the README file, I guess 
>>it's
>>fine. I'd, however, encourage everyone to add them to provide consistency and 
>>a
>>more immediate information of what the project is about, what some of the
>>project capabilities are and what its status is.
>>
>>Ideally this should also be added in projects documentation as well but I'll
>>leave that to every team to do.
>>
>>Happy to answer questions,
>>Flavio
>>
>>P.S: The current layout is being improved[3], if you have better ideas please
>>help out.
>>
>>[0] https://review.openstack.org/#/c/391588/
>>[1] http://governance.openstack.org/badges/
>>[2] https://review.openstack.org/#/q/topic:project-badges
>>[3] https://review.openstack.org/#/c/399278/
>>
>>On 12/10/16 14:50 +0200, 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,

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

2016-11-27 Thread Thomas Goirand

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

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,
Cheers,

Thomas Goirand (zigo)


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

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

2016-11-25 Thread Zara Zaimeche




On 25/11/16 17:51, Jeremy Stanley wrote:

On 2016-11-25 17:41:07 + (+), Miles Gould wrote:

I don't think this is an insurmountable problem: it should be possible to
allow users to switch between "code view" and "rendered view" for file-types
that support rendering.


Yes, it's "just" a matter of writing some code (and convincing cgit
upstream to support it). However, we already have automation to
continuously deploy rendered readme files and any other
documentation you want to write on docs.openstack.org or
readthedocs.org. Why would having a rendered readme at
http://git.openstack.org/cgit/openstack-infra/bindep/tree/README.rst
be a better user experience than
http://docs.openstack.org/infra/bindep/readme.html ?


Hi,

To add some detail, if you wanted to patch cgit, I believe you would 
need to extend the filter API, to include something between about-filter 
(https://git.zx2c4.com/cgit/tree/cgitrc.5.txt#n666 ; this renders a 
specific file differently in the 'about' tab of the repo) and 
source-filter (https://git.zx2c4.com/cgit/tree/cgitrc.5.txt#n690 ; this 
renders all source code with a particular extension, in-place ), and 
then patch the specific cgit instance config to use the new filter. I 
don't know whether cgit upstream would be receptive to this change, and 
I think OpenStack's existing infrastructure for documentation means 
there's little gain from doing it.


Best Wishes,

Zara

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

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

2016-11-25 Thread Jeremy Stanley

On 2016-11-25 17:41:07 + (+), Miles Gould wrote:
> I don't think this is an insurmountable problem: it should be possible to
> allow users to switch between "code view" and "rendered view" for file-types
> that support rendering.

Yes, it's "just" a matter of writing some code (and convincing cgit
upstream to support it). However, we already have automation to
continuously deploy rendered readme files and any other
documentation you want to write on docs.openstack.org or
readthedocs.org. Why would having a rendered readme at
http://git.openstack.org/cgit/openstack-infra/bindep/tree/README.rst
be a better user experience than
http://docs.openstack.org/infra/bindep/readme.html ?
-- 
Jeremy Stanley

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

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

2016-11-25 Thread Miles Gould


On 25/11/16 17:12, Jeremy Stanley wrote:


It came down less to safety and more to the fact that if you force
cgit to present rendered content then you lose the ability to
reference the source code for the same files.


I don't think this is an insurmountable problem: it should be possible 
to allow users to switch between "code view" and "rendered view" for 
file-types that support rendering.


Miles

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

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

2016-11-25 Thread Flavio Percoco


On 25/11/16 09:15 -0800, Christopher Aedo wrote:

On Fri, Nov 25, 2016 at 3:38 AM, Flavio Percoco  wrote:

Greetings,

Just a heads up for everyone. The work on this front has moved forward and
the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite obvious,
the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the
projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of "viral
changes" but I've done my best to explain what's changing, provide
references
and examples on the commit message. These changes are being submitted using
the
tag 'project-badges'[2].

Note that these badges are *JUST* a graphical representation of what's in
the
governance repo. If you don't want to have them in the README file, I guess
it's
fine. I'd, however, encourage everyone to add them to provide consistency
and a
more immediate information of what the project is about, what some of the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well but I'll
leave that to every team to do.


Thanks for doing the work to get this automated Flavio!  As a few
others have noted, I did not like the placement at the very top but I
understand it's not reasonably possible to automate this in a way that
find the idea insertion point.  For me at any rate, I've moved them
down to just under the first paragraph explaining the project.


This sounds perfect, thanks for doing that :)


One other important thing that's missing however is the :alt: tag
underneath the image.  For accessibility purposes (and considering
this is all automated anyway) I don't think these badges should be
merged without text describing the image.


Gosh, I thought I had added the :alt: tag. FWIW, I did remember this, freudian
slip, I guess.

Flavio


-Christopher


Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better ideas
please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/


On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco





--
@flaper87
Flavio Percoco

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



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


--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Christopher Aedo

On Fri, Nov 25, 2016 at 3:38 AM, Flavio Percoco  wrote:
> Greetings,
>
> Just a heads up for everyone. The work on this front has moved forward and
> the
> badges are now being generated as part of the governance CI[0].
>
> You can find the list of badges here[1] and the pattern is quite obvious,
> the
> name of the image is based on the project repo name.
>
> I've edited the README files for all repositories listed in the
> projects.yaml
> file and I've started to submit these patches[2]. I'm not a fan of "viral
> changes" but I've done my best to explain what's changing, provide
> references
> and examples on the commit message. These changes are being submitted using
> the
> tag 'project-badges'[2].
>
> Note that these badges are *JUST* a graphical representation of what's in
> the
> governance repo. If you don't want to have them in the README file, I guess
> it's
> fine. I'd, however, encourage everyone to add them to provide consistency
> and a
> more immediate information of what the project is about, what some of the
> project capabilities are and what its status is.
>
> Ideally this should also be added in projects documentation as well but I'll
> leave that to every team to do.

Thanks for doing the work to get this automated Flavio!  As a few
others have noted, I did not like the placement at the very top but I
understand it's not reasonably possible to automate this in a way that
find the idea insertion point.  For me at any rate, I've moved them
down to just under the first paragraph explaining the project.

One other important thing that's missing however is the :alt: tag
underneath the image.  For accessibility purposes (and considering
this is all automated anyway) I don't think these badges should be
merged without text describing the image.

-Christopher

> Happy to answer questions,
> Flavio
>
> P.S: The current layout is being improved[3], if you have better ideas
> please
> help out.
>
> [0] https://review.openstack.org/#/c/391588/
> [1] http://governance.openstack.org/badges/
> [2] https://review.openstack.org/#/q/topic:project-badges
> [3] https://review.openstack.org/#/c/399278/
>
>
> On 12/10/16 14:50 +0200, 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
>>
>> [0] http://governance.openstack.org/reference/projects/index.html
>>
>> --
>> @flaper87
>> Flavio Percoco
>
>
>
>
> --
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

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

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

2016-11-25 Thread Jeremy Stanley

On 2016-11-25 11:37:02 -0500 (-0500), Paul Belanger wrote:
[...]
> We do have an abandoned path in gerrit to support this[3], but
> infra decided to abandon it since it wasn't very safe. So, it is
> possible to render markdown in cgit, we just need to confirm how
> safe it is today.
[...]

It came down less to safety and more to the fact that if you force
cgit to present rendered content then you lose the ability to
reference the source code for the same files.

Ultimately we decided we have a place to display rendered documents
already (docs.openstack.org), and so should leave the source code
browser configured for what it does best: browsing source code.
-- 
Jeremy Stanley

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

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

2016-11-25 Thread Paul Belanger

On Thu, Oct 13, 2016 at 01:06:43PM +0200, Flavio Percoco wrote:
> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
> > Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> > > 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
> > > 
> > > [0] http://governance.openstack.org/reference/projects/index.html
> > > 
> > 
> > Is your proposal that a tag like release:cycle-with-milestones would
> > result in a badge being added when the README.rst is rendered on
> > github.com? Would that work for git.openstack.org, too?
> 
> I don't think it'd work for git.openstack.org because it doesn't render the
> README's[0] like github does. One thing I'd like to avoid is for this
> information to result in new changes to the README file everytime the tags are
> updated because I'd like for this information to not be duplicated and to make
> it clear that this information is not meant to be updated manually.
> 
We do have an abandoned path in gerrit to support this[3], but infra decided to
abandon it since it wasn't very safe. So, it is possible to render markdown in
cgit, we just need to confirm how safe it is today.

[3] https://review.openstack.org/#/c/60375/

> Here's[1] an example of what it would look like (or kinda).
> 
> [0] http://git.openstack.org/cgit/openstack/glance/tree/README.rst
> [1] https://github.com/celery/kombu/blob/master/README.rst
> 
> 
> > I agree that the governance site is not the best place to put the
> > info to make it discoverable. Do users look first at the source
> > repository, or at some other documentation?
> 
> The feedback* I've gotten is that users normally look at repos first and they 
> go
> from there to docs (which are normally linked in the README file).
> 
> * Neither based on a survey nor on any empirical research. This is based on
>  hallway talks.
> 
> Flavio
> 
> -- 
> @flaper87
> Flavio Percoco



> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


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

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

2016-11-25 Thread Flavio Percoco

On 25/11/16 14:35 +, Amrith Kumar wrote:

Thanks Flavio,

I've logged https://bugs.launchpad.net/trove/+bug/1644851 for this and I
assume that other projects which want to do this kind of manual cleanup can
either use this bug or create their own.

Thanks Amrith, I think this is the right approach for teams that prefer to
modify the README further. Do you intend to land the patches as they are and
modify the README with follow-up patches? or are you going to wait for the
patches to be updated? I would advise for the former but I'm biased :D

Also, https://review.openstack.org/#/c/399278/ landed. I'll be improving the
layout a bit better based on the feedback from your email.

Thanks,
Flavio

-amrith

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Friday, November 25, 2016 9:00 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
README files

On 25/11/16 13:46 +, Amrith Kumar wrote:
>Flavio,
>
>I see a number of patches[1] which have been landed on this project but
>I find that at least the ones that were landed for Trove, and a random
>sampling of the others all to be different from what you proposed
>below[2] in one important aspect.
>
>In [2] you proposed a structure where the title of the document; or the
>first, and most prominent heading, would be the existing heading of the
>document, and the tags would be below that. In [2] for example, that was:
>
>"kombu - Messaging library for Python"
>
>and the tags would be in smaller font below that.

Hey Amrith,

One reason it's different from Kombu is because Kombu uses shields as a
backend for this SVGs, whereas we don't. We generate the badges
ourselves[0], which probably ended up in some differences.

The other main difference in the kombu case, there are multiple images in
the README, wherease in our case there's one SVG containing multiple svgs.
The motivation behind this is being able to update the badges without
sending patches to projects everytime the governance repo is modified.

This layout and format can of couse be modified, the font size and family
can
be changed, etc. See[1].

>What I see in [3] the patch for Trove and the proposed example [4] is:
>
>"Team and repository tags" as the first, and most conspicuous header,
>and the header "Trove" below that.
>
>In some cases the second header is the same font as the "Team and
>repository tags" header.

I explained this a bit here[2]. The reason for prepending these secion to
the
README's instead of finding a good place in it is that READMEs throughout
OpenStack are quite different from each other and putting this at the top
helped in making the process of adding the badges simpler.

>I think this change (these 124 changes) as proposed are not consistent
>with the proposal you made below, and certainly seem to be less
>suitable than that proposal. The end product for the four trove
>repositories [4], [5], [6], and [7]
>
>I think we should have a discussion on the ML whether we feel that this
>new structure is the appropriate one, and before some projects approve
>these changes and others don't that these be all marked WF-1.

I honestly don't think the current proposal is bad, it's different from
Kombu
for the reasons I mentioned above but it can be improved. Not that
improving the badges and their layout doesn't require submitting these
patches again. It'll be enough to modify the governance repo that generates
these images.

Hope this helps,
Flavio

[0]
http://git.openstack.org/cgit/openstack/governance/tree/doc/source/_exts
/badges.py
[1] https://review.openstack.org/#/c/399278/
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-
November/107969.html

>Thanks,
>
>-amrith
>
>[1] https://review.openstack.org/#/q/topic:project-badges
>[2] https://github.com/celery/kombu/blob/master/README.rst
>[3] https://review.openstack.org/#/c/402547/
>[4]
https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
>[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
>[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
>[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258
>
>
>
>
>> -Original Message-
>> From: Flavio Percoco [mailto:fla...@redhat.com]
>> Sent: Thursday, October 13, 2016 7:07 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>> <openstack-dev@lists.openstack.org>
>> Subject: Re: [openstack-dev] [all][tc] Exposing project team's
>> metadata in README files
>>
>> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>> >Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> >> Gree

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

2016-11-25 Thread Flavio Percoco


On 25/11/16 23:49 +0900, Ian Y. Choi wrote:

Hello Flavio,

I have two questions on this thread:

1) I have just written my review on training-guides repository
: https://review.openstack.org/#/c/402607/1 .
Then would you revise your initialized patchset by yourself? Or Your 
intention
would be to discuss more on each repository team members and revise 
patch(es) by themselves?


Each team is free to modify the patch as they want but I'd prefer there to be
consistency across README files. Putting it at the top was simply more
convinient for me doing the job and I also believe it's better for people that
land on the README.

By all means, feel free to modify it if you think it's not ok to have it there.

2) Can I18n team (openstack/i18n and openstack/i18n-specs) have such 
image tag? :)


Yes, these are coming :D

Thanks for reviewing and reaching out,
Flavio

P.S: The commit message b and \n was just me being bitten by python 3.5. I fixed
that for other commits but it's harmless to have it in yours. :D



With many thanks,

/Ian

Flavio Percoco wrote on 11/25/2016 11:00 PM:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this 
project but I find
that at least the ones that were landed for Trove, and a random 
sampling of

the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; 
or the first,
and most prominent heading, would be the existing heading of the 
document, and

the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.


Hey Amrith,

One reason it's different from Kombu is because Kombu uses shields 
as a backend
for this SVGs, whereas we don't. We generate the badges 
ourselves[0], which

probably ended up in some differences.

The other main difference in the kombu case, there are multiple 
images in the
README, wherease in our case there's one SVG containing multiple 
svgs. The

motivation behind this is being able to update the badges without sending
patches to projects everytime the governance repo is modified.

This layout and format can of couse be modified, the font size and 
family can be

changed, etc. See[1].


What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous 
header, and the

header "Trove" below that.

In some cases the second header is the same font as the "Team and 
repository

tags" header.


I explained this a bit here[2]. The reason for prepending these 
secion to the

README's instead of finding a good place in it is that READMEs throughout
OpenStack are quite different from each other and putting this at 
the top helped

in making the process of adding the badges simpler.

I think this change (these 124 changes) as proposed are not 
consistent with
the proposal you made below, and certainly seem to be less 
suitable than that
proposal. The end product for the four trove repositories [4], 
[5], [6], and

[7]

I think we should have a discussion on the ML whether we feel that 
this new

structure is the appropriate one, and before some projects approve these
changes and others don't that these be all marked WF-1.


I honestly don't think the current proposal is bad, it's different 
from Kombu
for the reasons I mentioned above but it can be improved. Not that 
improving the
badges and their layout doesn't require submitting these patches 
again. It'll be

enough to modify the governance repo that generates these images.

Hope this helps,
Flavio


[0] 
http://git.openstack.org/cgit/openstack/governance/tree/doc/source/_exts/badges.py
[1] https://review.openstack.org/#/c/399278/
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107969.html


Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258





-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's 
metadata in

README files

On 12/10/16 11:01 -0400, Doug Hellmann wrote:

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:

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

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

2016-11-25 Thread Ian Y. Choi

Hello Flavio,

I have two questions on this thread:

1) I have just written my review on training-guides repository
: https://review.openstack.org/#/c/402607/1 .
Then would you revise your initialized patchset by yourself? Or Your 
intention
would be to discuss more on each repository team members and revise 
patch(es) by themselves?

2) Can I18n team (openstack/i18n and openstack/i18n-specs) have such 
image tag? :)

With many thanks,

/Ian

Flavio Percoco wrote on 11/25/2016 11:00 PM:

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project 
but I find
that at least the ones that were landed for Trove, and a random 
sampling of

the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or 
the first,
and most prominent heading, would be the existing heading of the 
document, and

the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.

Hey Amrith,

One reason it's different from Kombu is because Kombu uses shields as 
a backend
for this SVGs, whereas we don't. We generate the badges ourselves[0], 
which

probably ended up in some differences.

The other main difference in the kombu case, there are multiple images 
in the
README, wherease in our case there's one SVG containing multiple svgs. 
The

motivation behind this is being able to update the badges without sending
patches to projects everytime the governance repo is modified.

This layout and format can of couse be modified, the font size and 
family can be

changed, etc. See[1].

What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous header, 
and the

header "Trove" below that.

In some cases the second header is the same font as the "Team and 
repository

tags" header.

I explained this a bit here[2]. The reason for prepending these secion 
to the

README's instead of finding a good place in it is that READMEs throughout
OpenStack are quite different from each other and putting this at the 
top helped

in making the process of adding the badges simpler.

I think this change (these 124 changes) as proposed are not 
consistent with
the proposal you made below, and certainly seem to be less suitable 
than that
proposal. The end product for the four trove repositories [4], [5], 
[6], and

[7]

I think we should have a discussion on the ML whether we feel that 
this new

structure is the appropriate one, and before some projects approve these
changes and others don't that these be all marked WF-1.

I honestly don't think the current proposal is bad, it's different 
from Kombu
for the reasons I mentioned above but it can be improved. Not that 
improving the
badges and their layout doesn't require submitting these patches 
again. It'll be

enough to modify the governance repo that generates these images.

Hope this helps,
Flavio

[0] 
http://git.openstack.org/cgit/openstack/governance/tree/doc/source/_exts/badges.py

[1] https://review.openstack.org/#/c/399278/
[2] 
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107969.html

Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's 
metadata in

README files

On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> 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

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

2016-11-25 Thread Andrey Kurilin

The same for Rally project...

On Thu, Oct 13, 2016 at 2:56 PM, Qiming Teng 
wrote:

> project-navigator? http://www.openstack.org/software/
>
> It is often misinterpreted as: OpenStack has 6 core services which are
> all mandatory (because they are *core* services) plus 13 optional
> services that can be selectively installed.
>
> I tried hard to find out how the lists are generated, but I failed.
> There are at least the following projects which are neither *core* nor
> *optional* services:
>
> cloudkitty
> dragonflow
> freezer
> karbor
> kolla
> kuryr
> mistral
> monasca
> searchlight
> senlin
> solum
> tacker
> vitrage
> watcher
>
> Looks like this is something causing some confusions. Should/can we fix
> that?
>
> Regards,
>   Qiming
>
>
> On Wed, Oct 12, 2016 at 02:43:45PM -0700, Mike Perez wrote:
> > On 14:50 Oct 12, 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.
> >
> > Besides the governance site, there is also the project navigator [1]
> which is
> > a more friendly landing page on projects and their tags. Although it
> does not
> > today capture separate deliverables.
> >
> > Assuming the README files aren't being manually updated, I don't have a
> problem
> > with this idea.
> >
> > [1] - https://www.openstack.org/software/project-navigator/
> >
> > --
> > Mike Perez
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Best regards,
Andrey Kurilin.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Amrith Kumar

Thanks Flavio,

I've logged https://bugs.launchpad.net/trove/+bug/1644851 for this and I 
assume that other projects which want to do this kind of manual cleanup can 
either use this bug or create their own.

-amrith

> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Friday, November 25, 2016 9:00 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
> README files
>
> On 25/11/16 13:46 +, Amrith Kumar wrote:
> >Flavio,
> >
> >I see a number of patches[1] which have been landed on this project but
> >I find that at least the ones that were landed for Trove, and a random
> >sampling of the others all to be different from what you proposed
> >below[2] in one important aspect.
> >
> >In [2] you proposed a structure where the title of the document; or the
> >first, and most prominent heading, would be the existing heading of the
> >document, and the tags would be below that. In [2] for example, that was:
> >
> >"kombu - Messaging library for Python"
> >
> >and the tags would be in smaller font below that.
>
> Hey Amrith,
>
> One reason it's different from Kombu is because Kombu uses shields as a
> backend for this SVGs, whereas we don't. We generate the badges
> ourselves[0], which probably ended up in some differences.
>
> The other main difference in the kombu case, there are multiple images in
> the README, wherease in our case there's one SVG containing multiple svgs.
> The motivation behind this is being able to update the badges without
> sending patches to projects everytime the governance repo is modified.
>
> This layout and format can of couse be modified, the font size and family 
> can
> be changed, etc. See[1].
>
> >What I see in [3] the patch for Trove and the proposed example [4] is:
> >
> >"Team and repository tags" as the first, and most conspicuous header,
> >and the header "Trove" below that.
> >
> >In some cases the second header is the same font as the "Team and
> >repository tags" header.
>
> I explained this a bit here[2]. The reason for prepending these secion to 
> the
> README's instead of finding a good place in it is that READMEs throughout
> OpenStack are quite different from each other and putting this at the top
> helped in making the process of adding the badges simpler.
>
> >I think this change (these 124 changes) as proposed are not consistent
> >with the proposal you made below, and certainly seem to be less
> >suitable than that proposal. The end product for the four trove
> >repositories [4], [5], [6], and [7]
> >
> >I think we should have a discussion on the ML whether we feel that this
> >new structure is the appropriate one, and before some projects approve
> >these changes and others don't that these be all marked WF-1.
>
> I honestly don't think the current proposal is bad, it's different from 
> Kombu
> for the reasons I mentioned above but it can be improved. Not that
> improving the badges and their layout doesn't require submitting these
> patches again. It'll be enough to modify the governance repo that generates
> these images.
>
> Hope this helps,
> Flavio
>
>
> [0]
> http://git.openstack.org/cgit/openstack/governance/tree/doc/source/_exts
> /badges.py
> [1] https://review.openstack.org/#/c/399278/
> [2] http://lists.openstack.org/pipermail/openstack-dev/2016-
> November/107969.html
>
> >Thanks,
> >
> >-amrith
> >
> >[1] https://review.openstack.org/#/q/topic:project-badges
> >[2] https://github.com/celery/kombu/blob/master/README.rst
> >[3] https://review.openstack.org/#/c/402547/
> >[4]
> https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
> >[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
> >[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
> >[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258
> >
> >
> >
> >
> >> -Original Message-
> >> From: Flavio Percoco [mailto:fla...@redhat.com]
> >> Sent: Thursday, October 13, 2016 7:07 AM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> <openstack-dev@lists.openstack.org>
> >> Subject: Re: [openstack-dev] [all][tc] Exposing project team's
> >> metadata in README files
> >>
> >> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
> >> >Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> >

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

2016-11-25 Thread Flavio Percoco

On 25/11/16 13:46 +, Amrith Kumar wrote:

Flavio,

I see a number of patches[1] which have been landed on this project but I find
that at least the ones that were landed for Trove, and a random sampling of
the others all to be different from what you proposed below[2] in one
important aspect.

In [2] you proposed a structure where the title of the document; or the first,
and most prominent heading, would be the existing heading of the document, and
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.

Hey Amrith,

One reason it's different from Kombu is because Kombu uses shields as a backend
for this SVGs, whereas we don't. We generate the badges ourselves[0], which
probably ended up in some differences.

The other main difference in the kombu case, there are multiple images in the
README, wherease in our case there's one SVG containing multiple svgs. The
motivation behind this is being able to update the badges without sending
patches to projects everytime the governance repo is modified.

This layout and format can of couse be modified, the font size and family can be
changed, etc. See[1].

What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous header, and the
header "Trove" below that.

In some cases the second header is the same font as the "Team and repository
tags" header.

I explained this a bit here[2]. The reason for prepending these secion to the
README's instead of finding a good place in it is that READMEs throughout
OpenStack are quite different from each other and putting this at the top helped
in making the process of adding the badges simpler.

I think this change (these 124 changes) as proposed are not consistent with
the proposal you made below, and certainly seem to be less suitable than that
proposal. The end product for the four trove repositories [4], [5], [6], and
[7]

I think we should have a discussion on the ML whether we feel that this new
structure is the appropriate one, and before some projects approve these
changes and others don't that these be all marked WF-1.

I honestly don't think the current proposal is bad, it's different from Kombu
for the reasons I mentioned above but it can be improved. Not that improving the
badges and their layout doesn't require submitting these patches again. It'll be
enough to modify the governance repo that generates these images.

Hope this helps,
Flavio

[0] 
http://git.openstack.org/cgit/openstack/governance/tree/doc/source/_exts/badges.py
[1] https://review.openstack.org/#/c/399278/
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-November/107969.html

Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258

-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
README files

On 12/10/16 11:01 -0400, Doug Hellmann wrote:
>Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> 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
>> t

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

2016-11-25 Thread Julien Danjou

On Fri, Nov 25 2016, Amrith Kumar wrote:

> I see a number of patches[1] which have been landed on this project but I 
> find 
> that at least the ones that were landed for Trove, and a random sampling of 
> the others all to be different from what you proposed below[2] in one 
> important aspect.
>
> In [2] you proposed a structure where the title of the document; or the 
> first, 
> and most prominent heading, would be the existing heading of the document, 
> and 
> the tags would be below that. In [2] for example, that was:
>
> "kombu - Messaging library for Python"
>
> and the tags would be in smaller font below that.
>
> What I see in [3] the patch for Trove and the proposed example [4] is:
>
> "Team and repository tags" as the first, and most conspicuous header, and the 
> header "Trove" below that.
>
> In some cases the second header is the same font as the "Team and repository 
> tags" header.

Just FTR, this also is why I -1ed the Telemetry patches.

Cheers,
-- 
Julien Danjou
// Free Software hacker
// https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Amrith Kumar

Flavio,

I see a number of patches[1] which have been landed on this project but I find 
that at least the ones that were landed for Trove, and a random sampling of 
the others all to be different from what you proposed below[2] in one 
important aspect.

In [2] you proposed a structure where the title of the document; or the first, 
and most prominent heading, would be the existing heading of the document, and 
the tags would be below that. In [2] for example, that was:

"kombu - Messaging library for Python"

and the tags would be in smaller font below that.

What I see in [3] the patch for Trove and the proposed example [4] is:

"Team and repository tags" as the first, and most conspicuous header, and the 
header "Trove" below that.

In some cases the second header is the same font as the "Team and repository 
tags" header.

I think this change (these 124 changes) as proposed are not consistent with 
the proposal you made below, and certainly seem to be less suitable than that 
proposal. The end product for the four trove repositories [4], [5], [6], and 
[7]

I think we should have a discussion on the ML whether we feel that this new 
structure is the appropriate one, and before some projects approve these 
changes and others don't that these be all marked WF-1.

Thanks,

-amrith

[1] https://review.openstack.org/#/q/topic:project-badges
[2] https://github.com/celery/kombu/blob/master/README.rst
[3] https://review.openstack.org/#/c/402547/
[4] https://gist.github.com/anonymous/4ccf1cc6e531bb50e78cb4d64dfe1065
[5] https://gist.github.com/1f38def1c65c733b7e4cec3d07399e99
[6] https://gist.github.com/2f1c6e9b800db6d4a49d46f5b0623c1d
[7] https://gist.github.com/9e9e2e2ba4ecfdece7827082114f8258




> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Thursday, October 13, 2016 7:07 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
> README files
>
> On 12/10/16 11:01 -0400, Doug Hellmann wrote:
> >Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> >> 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
> >>
> >> [0] http://governance.openstack.org/reference/projects/index.html
> >>
> >
> >Is your proposal that a tag like release:cycle-with-milestones would
> >result in a badge being added when the README.rst is rendered on
> >github.com? Would that work for git.openstack.org, too?
>
> I don't think it'd work for git.openstack.org because it doesn't render the
> README's[0] like github does. One thing I'd like to avoid is for this
> information to result in new changes to the README file everytime the tags
> are updated because I'd like for this information to not be duplicated and 
> to
> make it clear that this information is not meant to be updated manually.
>
> Here's[1] an example of what

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

2016-11-25 Thread Flavio Percoco


On 25/11/16 12:33 +, Dulko, Michal wrote:

On Fri, 2016-11-25 at 12:38 +0100, Flavio Percoco wrote:

Greetings,

Just a heads up for everyone. The work on this front has moved
forward and the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite
obvious, the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the
projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of
"viral
changes" but I've done my best to explain what's changing, provide
references
and examples on the commit message. These changes are being submitted
using the
tag 'project-badges'[2].


Looks like Cinder patch is missing there?


Probably still loading it! I got a bit ahead of the submission process because I
didn't want it to catch everyone by surprise. I'll let you know when the command
is done submitting patches.

Thanks for reaching out,
Flavio



Note that these badges are *JUST* a graphical representation of
what's in the
governance repo. If you don't want to have them in the README file, I
guess it's
fine. I'd, however, encourage everyone to add them to provide
consistency and a
more immediate information of what the project is about, what some of
the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well
but I'll
leave that to every team to do.

Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better
ideas please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/

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


--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Dulko, Michal

On Fri, 2016-11-25 at 12:38 +0100, Flavio Percoco wrote:
> Greetings,
> 
> Just a heads up for everyone. The work on this front has moved
> forward and the
> badges are now being generated as part of the governance CI[0].
> 
> You can find the list of badges here[1] and the pattern is quite
> obvious, the
> name of the image is based on the project repo name.
> 
> I've edited the README files for all repositories listed in the
> projects.yaml
> file and I've started to submit these patches[2]. I'm not a fan of
> "viral
> changes" but I've done my best to explain what's changing, provide
> references
> and examples on the commit message. These changes are being submitted
> using the
> tag 'project-badges'[2].

Looks like Cinder patch is missing there?

> 
> Note that these badges are *JUST* a graphical representation of
> what's in the
> governance repo. If you don't want to have them in the README file, I
> guess it's
> fine. I'd, however, encourage everyone to add them to provide
> consistency and a
> more immediate information of what the project is about, what some of
> the
> project capabilities are and what its status is.
> 
> Ideally this should also be added in projects documentation as well
> but I'll
> leave that to every team to do.
> 
> Happy to answer questions,
> Flavio
> 
> P.S: The current layout is being improved[3], if you have better
> ideas please
> help out.
> 
> [0] https://review.openstack.org/#/c/391588/
> [1] http://governance.openstack.org/badges/
> [2] https://review.openstack.org/#/q/topic:project-badges
> [3] https://review.openstack.org/#/c/399278/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Flavio Percoco


On 25/11/16 13:16 +0100, Flavio Percoco wrote:

On 25/11/16 12:38 +0100, Flavio Percoco wrote:

Greetings,

Just a heads up for everyone. The work on this front has moved forward and the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite obvious, the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of "viral
changes" but I've done my best to explain what's changing, provide references
and examples on the commit message. These changes are being submitted using the
tag 'project-badges'[2].


I also wanted to add that these patches are just for projects that are using rst
for their README files (sorry markdown) and that each commit has a preview link
that you can go and look at.

If the layout doesn't look perfect and the whitespace under the svg image
annoyes you, let me tell you that it was improved in the new layout, which is
under review. Also, Github does some funky things to the svg when it renders the
README file, hence the whitespace that was added for the first layout.


One last thing. You may/may not like the placement of these badges in the README
file. It's fine if you don't. The reason they are at the top is because they
normally are at the top :) Putting them at the top also made it simple to
automate the process accross all the *very* (trust me VERY) different README
files across the community.

If you don't like the placement of these badges, you're free to move them around
as prefer. I've done the job to help pushing the first patch, you're all free to
take it over, modify it, reject it or just merge it as is.

Hope this helps,
Flavio


Flavio


Note that these badges are *JUST* a graphical representation of what's in the
governance repo. If you don't want to have them in the README file, I guess it's
fine. I'd, however, encourage everyone to add them to provide consistency and a
more immediate information of what the project is about, what some of the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well but I'll
leave that to every team to do.

Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better ideas please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/

On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Flavio Percoco


On 25/11/16 12:38 +0100, Flavio Percoco wrote:

Greetings,

Just a heads up for everyone. The work on this front has moved forward and the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite obvious, the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of "viral
changes" but I've done my best to explain what's changing, provide references
and examples on the commit message. These changes are being submitted using the
tag 'project-badges'[2].


I also wanted to add that these patches are just for projects that are using rst
for their README files (sorry markdown) and that each commit has a preview link
that you can go and look at.

If the layout doesn't look perfect and the whitespace under the svg image
annoyes you, let me tell you that it was improved in the new layout, which is
under review. Also, Github does some funky things to the svg when it renders the
README file, hence the whitespace that was added for the first layout.

Flavio


Note that these badges are *JUST* a graphical representation of what's in the
governance repo. If you don't want to have them in the README file, I guess it's
fine. I'd, however, encourage everyone to add them to provide consistency and a
more immediate information of what the project is about, what some of the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well but I'll
leave that to every team to do.

Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better ideas please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/

On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-11-25 Thread Flavio Percoco


Greetings,

Just a heads up for everyone. The work on this front has moved forward and the
badges are now being generated as part of the governance CI[0].

You can find the list of badges here[1] and the pattern is quite obvious, the
name of the image is based on the project repo name.

I've edited the README files for all repositories listed in the projects.yaml
file and I've started to submit these patches[2]. I'm not a fan of "viral
changes" but I've done my best to explain what's changing, provide references
and examples on the commit message. These changes are being submitted using the
tag 'project-badges'[2].

Note that these badges are *JUST* a graphical representation of what's in the
governance repo. If you don't want to have them in the README file, I guess it's
fine. I'd, however, encourage everyone to add them to provide consistency and a
more immediate information of what the project is about, what some of the
project capabilities are and what its status is.

Ideally this should also be added in projects documentation as well but I'll
leave that to every team to do.

Happy to answer questions,
Flavio

P.S: The current layout is being improved[3], if you have better ideas please
help out.

[0] https://review.openstack.org/#/c/391588/
[1] http://governance.openstack.org/badges/
[2] https://review.openstack.org/#/q/topic:project-badges
[3] https://review.openstack.org/#/c/399278/

On 12/10/16 14:50 +0200, 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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-10-17 Thread Hugh Blemings


On 12/10/2016 23:50, 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.

[...]


For what it's worth while I lack depth of knowledge to speak to the
veracity of the solution proposed, I can say it'd be grand to have this
in some sort of single canonical reference point.  The project navigator
gets close but as others have observed it doesn't have every project
necessarily.

So a +1 from me for something along these lines, ideally automagically 
updated/aggregated from the project source trees itself would be my guess.


Cheers,
Hugh




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

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

2016-10-13 Thread Qiming Teng

project-navigator? http://www.openstack.org/software/

It is often misinterpreted as: OpenStack has 6 core services which are
all mandatory (because they are *core* services) plus 13 optional
services that can be selectively installed.

I tried hard to find out how the lists are generated, but I failed.
There are at least the following projects which are neither *core* nor
*optional* services:

cloudkitty
dragonflow
freezer
karbor
kolla
kuryr
mistral
monasca
searchlight
senlin
solum
tacker
vitrage
watcher

Looks like this is something causing some confusions. Should/can we fix
that?

Regards,
  Qiming


On Wed, Oct 12, 2016 at 02:43:45PM -0700, Mike Perez wrote:
> On 14:50 Oct 12, 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.
> 
> Besides the governance site, there is also the project navigator [1] which is
> a more friendly landing page on projects and their tags. Although it does not
> today capture separate deliverables.
> 
> Assuming the README files aren't being manually updated, I don't have a 
> problem
> with this idea.
> 
> [1] - https://www.openstack.org/software/project-navigator/
> 
> -- 
> Mike Perez


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

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

2016-10-13 Thread Flavio Percoco


On 13/10/16 13:06 +0200, Flavio Percoco wrote:

On 12/10/16 11:01 -0400, Doug Hellmann wrote:

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:

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

[0] http://governance.openstack.org/reference/projects/index.html



Is your proposal that a tag like release:cycle-with-milestones would
result in a badge being added when the README.rst is rendered on
github.com? Would that work for git.openstack.org, too?


I don't think it'd work for git.openstack.org because it doesn't render the
README's[0] like github does. One thing I'd like to avoid is for this
information to result in new changes to the README file everytime the tags are
updated because I'd like for this information to not be duplicated and to make
it clear that this information is not meant to be updated manually.

Here's[1] an example of what it would look like (or kinda).

[0] http://git.openstack.org/cgit/openstack/glance/tree/README.rst
[1] https://github.com/celery/kombu/blob/master/README.rst


Just wanted to add one more thing. This badges can be generated automatically
and there's a small project that does this already[0][1]. We can host it or use
it. We do need, however, a small API that will generate the list of "badges".

[0] http://shields.io/
[1] https://img.shields.io/badge/release-cycle--with--milestones-blue.svg

Flavio




I agree that the governance site is not the best place to put the
info to make it discoverable. Do users look first at the source
repository, or at some other documentation?


The feedback* I've gotten is that users normally look at repos first and they go
from there to docs (which are normally linked in the README file).

* Neither based on a survey nor on any empirical research. This is based on
hallway talks.

Flavio

--
@flaper87
Flavio Percoco




--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-10-13 Thread Flavio Percoco


On 12/10/16 15:13 +, Hayes, Graham wrote:

On 12/10/2016 16:08, Doug Hellmann wrote:

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:

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

[0] http://governance.openstack.org/reference/projects/index.html



Is your proposal that a tag like release:cycle-with-milestones would
result in a badge being added when the README.rst is rendered on
github.com? Would that work for git.openstack.org, too?

I agree that the governance site is not the best place to put the
info to make it discoverable. Do users look first at the source
repository, or at some other documentation?

Doug


I like this idea.

I know when I am looking at software, I look at the source repo
initially.

We could do it in the readme, and maybe re-use it in the docs as well?


Yup! Re-using this in the docs is definitely part of the plan.


I would be willing to dig in and help if needed.


Might take your word on this :D

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-10-13 Thread Flavio Percoco


On 12/10/16 14:43 -0700, Mike Perez wrote:

On 14:50 Oct 12, 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.


Besides the governance site, there is also the project navigator [1] which is
a more friendly landing page on projects and their tags. Although it does not
today capture separate deliverables.

Assuming the README files aren't being manually updated, I don't have a problem
with this idea.


Yeah, not manually updated and I'd go as far as saying that I'd prefer the info
to not be duplicated. That is, I'd prefer to not have a bot copying from the
governance repo to the project's README but rather have this info populated at
render time.

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-10-13 Thread Flavio Percoco


On 12/10/16 11:01 -0400, Doug Hellmann wrote:

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:

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

[0] http://governance.openstack.org/reference/projects/index.html



Is your proposal that a tag like release:cycle-with-milestones would
result in a badge being added when the README.rst is rendered on
github.com? Would that work for git.openstack.org, too?


I don't think it'd work for git.openstack.org because it doesn't render the
README's[0] like github does. One thing I'd like to avoid is for this
information to result in new changes to the README file everytime the tags are
updated because I'd like for this information to not be duplicated and to make
it clear that this information is not meant to be updated manually.

Here's[1] an example of what it would look like (or kinda).

[0] http://git.openstack.org/cgit/openstack/glance/tree/README.rst
[1] https://github.com/celery/kombu/blob/master/README.rst



I agree that the governance site is not the best place to put the
info to make it discoverable. Do users look first at the source
repository, or at some other documentation?


The feedback* I've gotten is that users normally look at repos first and they go
from there to docs (which are normally linked in the README file).

* Neither based on a survey nor on any empirical research. This is based on
 hallway talks.

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-10-12 Thread gordon chung



On 12/10/16 05:43 PM, Mike Perez wrote:
> Besides the governance site, there is also the project navigator [1] which is
> a more friendly landing page on projects and their tags. Although it does not
> today capture separate deliverables.
>
> Assuming the README files aren't being manually updated, I don't have a 
> problem
> with this idea.
>
> [1] - https://www.openstack.org/software/project-navigator/

sorry, unrelated to thread, but is that page manually updated? i noticed 
the Telemetry project is still not sync'd in terms of what is in 
projects.yaml[1] and the page. i imagine it was updated recently since 
i'm correctly not PTL anymore.

[1] 
http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

cheers,

-- 
gord

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

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

2016-10-12 Thread Mike Perez

On 14:50 Oct 12, 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.

Besides the governance site, there is also the project navigator [1] which is
a more friendly landing page on projects and their tags. Although it does not
today capture separate deliverables.

Assuming the README files aren't being manually updated, I don't have a problem
with this idea.

[1] - https://www.openstack.org/software/project-navigator/

-- 
Mike Perez

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

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

2016-10-12 Thread Amrith Kumar

I've been interacting recently with several new contributors (to Trove) and I 
can certainly attest to the fact that people appear to browse the source 
repository and read the README's.

Flavio makes a good point that it would be good to provide a short summary of 
the project's capabilities in some common place for all projects, and it may 
then be easy to automate the generation of a single webpage for all of the 
projects that one could treat as a landing page.

To Doug's point about tags; I would recommend that the tags be used to also 
indicate which section of the main landing page the project should land. For 
example, does the project fall under "compute", "storage", or "networking" or 
some such suitable taxonomy of projects that will help to render a meaningful 
top level (landing page) for all projects in some intuitive organization for 
potential contributors and users.

-amrith 

> -Original Message-
> From: Hayes, Graham [mailto:graham.ha...@hpe.com]
> Sent: Wednesday, October 12, 2016 11:14 AM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
> README files
> 
> On 12/10/2016 16:08, Doug Hellmann wrote:
> > Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> >> 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
> >>
> >> [0] http://governance.openstack.org/reference/projects/index.html
> >>
> >
> > Is your proposal that a tag like release:cycle-with-milestones would
> > result in a badge being added when the README.rst is rendered on
> > github.com? Would that work for git.openstack.org, too?
> >
> > I agree that the governance site is not the best place to put the
> > info to make it discoverable. Do users look first at the source
> > repository, or at some other documentation?
> >
> > Doug
> 
> I like this idea.
> 
> I know when I am looking at software, I look at the source repo
> initially.
> 
> We could do it in the readme, and maybe re-use it in the docs as well?
> 
> I would be willing to dig in and help if needed.
> 
> - Graham
> 
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-
> requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

2016-10-12 Thread Hayes, Graham

On 12/10/2016 16:08, Doug Hellmann wrote:
> Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
>> 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
>>
>> [0] http://governance.openstack.org/reference/projects/index.html
>>
>
> Is your proposal that a tag like release:cycle-with-milestones would
> result in a badge being added when the README.rst is rendered on
> github.com? Would that work for git.openstack.org, too?
>
> I agree that the governance site is not the best place to put the
> info to make it discoverable. Do users look first at the source
> repository, or at some other documentation?
>
> Doug

I like this idea.

I know when I am looking at software, I look at the source repo
initially.

We could do it in the readme, and maybe re-use it in the docs as well?

I would be willing to dig in and help if needed.

- Graham

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


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

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

2016-10-12 Thread Doug Hellmann

Excerpts from Flavio Percoco's message of 2016-10-12 14:50:03 +0200:
> 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
> 
> [0] http://governance.openstack.org/reference/projects/index.html
> 

Is your proposal that a tag like release:cycle-with-milestones would
result in a badge being added when the README.rst is rendered on
github.com? Would that work for git.openstack.org, too?

I agree that the governance site is not the best place to put the
info to make it discoverable. Do users look first at the source
repository, or at some other documentation?

Doug

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

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

2016-10-12 Thread Flavio Percoco


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

[0] http://governance.openstack.org/reference/projects/index.html

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

52 matches

Mail list logo