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
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 t
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?
Fl
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 pro
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
: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
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 2
our 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
cture 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.openst
; >> 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
/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/9e9e2e2ba
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 mailto:openst...@nemebean.com>> wrote:
On 11/30/2016 10:19 AM, Jason Rist wrote:
On 11/30/2016 11:18 AM, Ben Ne
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:
>
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 T
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
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 wha
//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)
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata
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 th
_
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
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
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.
>
> T
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
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 convinci
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 all
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 her
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,
>
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
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 bi
usage questions)
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 f
edhat.com]
Sent: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
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 mes
t: Thursday, October 13, 2016 7:07 AM
To: OpenStack Development Mailing List (not for usage questions)
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 201
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
@redhat.com]
> Sent: Friday, November 25, 2016 9:00 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
> README files
>
> On 25/11/16 13:46 +, Amrith Kumar wrote:
> >
-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)
Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
README files
On 12/10/16 11:01 -0400,
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.
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)
>
> Subject: Re: [openstack-dev] [all][tc] Exposing project team's metadata in
> README files
>
> On
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[
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
> obvio
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 th
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 imag
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 edite
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'
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 fa
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 he
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 a
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)
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 cu
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 update
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 informa
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)
>
> Subject: Re: [opensta
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
>>
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), thei
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
52 matches
Mail list logo