[openstack-tc] Designate one TC member to follow each candidate project
Sean Dague
sean at dague.net
Fri Nov 6 14:07:35 UTC 2015
On 11/06/2015 09:00 AM, Monty Taylor wrote:
> On 11/06/2015 08:49 AM, Thierry Carrez wrote:
>> Russell Bryant wrote:
>>>> [...]
>>>> We also said we should reconsider Monasca ASAP, anyone volunteering to
>>>> dive into that and confirm it's ready for reconsideration ?
>>>>
>>>> The others are likely to take a bit more time, but would still benefit
>>>> greatly from having a TC mentor following them up starting now. I can
>>>> take Juju charms (since I already asked for legal feedback on the
>>>> licensing there). Anyone volunteering for Compass, Kiloeyes or Kosmos ?
>>>
>>> I'd be happy to follow Kosmos.
>>
>> I added Monasca to next meeting agenda (time permitting) so maybe we
>> don't need a mentor for that one (unless it gets delayed again).
>>
>> Still missing volunteers for Compass and Kiloeyes. Is it that people
>> think it's a bad idea, or that people just don't have the time ? If the
>> latter, we could expand mentors beyond the TC (although mentors need to
>> have a pretty good grip on governance and TC rules).
>>
>
> I do not think kiloeyes needs a mentor. It has 6 commits. It's not
> actually a thing. thinking about it is a waste of our time until such a
> future time when it is actually a thing (which is a time I hope does not
> come, btw, because they should just be collaborating with monasca)
I think this has been my frustration with assuming TC mentoring of
not-yet-openstack projects is a thing we should sign up for. The goal
isn't to grow OpenStack to a 100 projects. The goal is that projects
that work like the rest of the OpenStack community get recognized as such.
The TC energy seems much better spent on key cross project issues
affecting our existing ecosystem and users.
-Sean
--
Sean Dague
http://dague.net
More information about the OpenStack-TC
mailing list