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 <fla...@redhat.com> 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
