Open Stack

Now that we have successfully navigated the Pike release and branched
the tree, I would like to restart the conversation about how to revive
and restart the Trove project.

Feedback from the last go around on this subject[1] resulted in a
lively discussion which I summarized in [2]. The very quick summary is
this, there is interest in Trove, there is a strong desire to maintain
a migration path, there is much that remains to be done to get there.

What didn't come out of the email discussion was any concrete and
tangible uptick in the participation in the project, promises
notwithstanding.

There have however been some new contributors who have been submitting
patches and to help channel their efforts, and any additional
assistance that we may receive, I have created the (below) list of
priorities for the project. These will also be the subject of
discussion at the PTG in Denver.

   - Fix the gate

       - Update currently failing jobs, create xenial based images
       - Fix gate jobs that have gone stale (non-voting, no one paying
         attention)

   - Bug triage

       - Bugs in launchpad are really out of date, assignments to
         people who are no longer active, bugs that are really support
         requests, etc.,
       - Prioritize fixes for Queens and beyond

   - Get more active reviewers

       - There seems to still be a belief that 'contributing' means
         'fixing bugs'. There is much more value in actually doing
         reviews.
       - Get at least a three member active core review team by the
         end of the year.

   - Complete Python 3 support

      - Currently not complete; especially on the guest side

   - Community Goal, migrate to oslo.policy

   - Anything related to new features

This is clearly an opinionated list, and is open to change but I'd
like to do that based on the Agile 'stand up' meeting rules. You know, the
chicken and pigs thing :)

So, if you'd like to get on board, offer suggestions to change this
list, and then go on to actually implement those changes, c'mon over.

-amrith



[1] http://openstack.markmail.org/thread/wokk73ecv44ipfjz
[2] http://markmail.org/message/gfqext34xh5y37ir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170815/9c6d7bbc/attachment.html>