<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 9, 2017 at 6:37 PM, Flavio Percoco <span dir="ltr"><<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 09/01/17 17:55 +0200, Andrey Kurilin wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi, Flavio!<br>
<br>
Does it possible to create badges per project release?<br>
</blockquote>
<br></span>
mmh, it's currently not possible.<br>
<br>
Could you elaborate on why you need a specific tag per release? IS it to tag the<br>
releases that were done after the inclusion in the big tent?<br>
<br></blockquote><div><br></div><div>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.<br></div><div>Another one is a "single-vendor" and so on. I think most of tags should be applied per project release.<br><br></div><div>One more "feature request": creation of custom badges(I'm interested in "tested on %(operation_system)s".<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Flavio<div><div class="gmail-h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco <<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Just a heads up!<br>
<br>
There are still unmerged patches on this effort. If you have a couple of<br>
spare<br>
brain cycles, it'd be awesome to get the patches relative to the projects<br>
you've<br>
+2 votes on in.<br>
<br>
I'll proceed to abandon remaining patches in 2 weeks from now assuming that<br>
projects are not interested in having them. As I mentioned in previous<br>
emails,<br>
you're free to update the patches to match your project needs.<br>
<br>
Here's the link to see the remaining patches:<br>
<a href="https://review.openstack.org/#/q/status:open+topic:project-badges" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/q/status:open+topic:project-b<wbr>adges</a><br>
<br>
Thanks a lot,<br>
Flavio<br>
<br>
<br>
On 12/10/16 14:50 +0200, Flavio Percoco wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Greetings,<br>
<br>
One of the common complains about the existing project organization in<br>
the big<br>
tent is that it's difficult to wrap our heads around the many projects<br>
there<br>
are, their current state (in/out the big tent), their tags, etc.<br>
<br>
This information is available on the governance website[0]. Each official<br>
project team has a page there containing the information related to the<br>
deliverables managed by that team. Unfortunately, I don't think this page<br>
is<br>
checked often enough and I believe it's not known by everyone.<br>
<br>
In the hope that we can make this information clearer to people browsing<br>
the<br>
many repos (most likely on github), I'd like to propose that we include<br>
the<br>
information of each deliverable in the readme file. This information<br>
would be<br>
rendered along with the rest of the readme (at least on Github, which<br>
might not<br>
be our main repo but it's the place most humans go to to check our<br>
projects).<br>
<br>
Rather than duplicating this information, I'd like to find a way to just<br>
"include it" in the Readme file. As far as showing the "official" badge<br>
goes, I<br>
believe it'd be quite simple. We can do it the same way CI tags are<br>
exposed when<br>
using travis (just include an image). As for the rest of the tags, it<br>
might<br>
require some extra hacking.<br>
<br>
So, before I start digging more into this, I wanted to get other<br>
opinions/ideas<br>
on this topic and how we can make this information more evident to the<br>
rest of<br>
the community (and people not as familiar with our processes as some of<br>
us are).<br>
<br>
Thanks in advance,<br>
Flavio<br>
<br>
[0] <a href="http://governance.openstack.org/reference/projects/index.html" rel="noreferrer" target="_blank">http://governance.openstack.or<wbr>g/reference/projects/index.htm<wbr>l</a><br>
<br>
--<br>
@flaper87<br>
Flavio Percoco<br>
<br>
</blockquote>
<br>
<br>
<br>
--<br>
@flaper87<br>
Flavio Percoco<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
</blockquote>
<br>
<br>
-- <br>
Best regards,<br>
Andrey Kurilin.<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
-- <br></div></div>
@flaper87<span class="gmail-HOEnZb"><font color="#888888"><br>
Flavio Percoco<br>
</font></span><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Best regards,<br>Andrey Kurilin.<br></div></div>
</div></div>