[openstack-dev] [ironic] Newton priorities and primary contacts

Ruby Loo opensrloo at gmail.com
Wed May 4 18:29:34 UTC 2016


At the Austin summit, we had a session where we discussed and decided on
what the top priorities would be for ironic, in the newton development
cycle. The etherpad [1] captures that discussion, and there is a patch up
to add the newton priorities to our specs [2].

Everyone, and in particular all ironic cores, should take a look at the
priorities [2] because as a community, we should all have the same
understanding and be working towards the same goals. Of course, side goals
are fine too :D

I also wanted to mention the primary contacts for these priorities, because
I'm not sure that I have the same understanding as others, as to what it

My understanding is that the primary contacts are the folks that would take
the lead for an item. Their responsibilities would include knowing the
status of it, and to do their 'best' to get it done, regardless of whether
they themselves did the design, code, documentation, review, etc. Ideally,
I'd prefer to see one primary contact per item, but if people want to work
together, that is fine, as long as it works.

If you are interested in a particular feature on this list, or would like
to contribute code towards that end, or would like to help review, or test,
that is wonderful and I thank you so much for your interest and desire to
contribute. However, I would really like to see primary contacts do more,
as described above. To take responsibility and (try to) commit the
time/effort it will take to see this priority items through.

Is this in line with what others think/expect from the primary contacts?


[1] https://etherpad.openstack.org/p/ironic-newton-summit-priorities
[2] https://review.openstack.org/#/c/311530/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160504/e006287b/attachment.html>

More information about the OpenStack-dev mailing list