Open Stack

I think we need to actually define the project's relationship to OpenStack
first. As of Vancouver, there was no decision made on whether to move
forward on StoryBoard, Maniphest, or something else. This lack of any kind
of forward commitment, both in resources and mandate, or even the lack of
ability of anyone to make a decision on this, is exactly why I left in
disgust.

So let me rehash the questions that were left unanswered in Vancouver.

- Is OpenStack going to use StoryBoard? If not, where is the alternative
and who is working on it?
- Who is actually going to work on storyboard?
- Is StoryBoard going to continue under infra?

It is quite telling (and I predicted this, just check the storyboard
meeting logs form last April) that there has been zero progress on any
storyboard alternatives since Vancouver.

So: If StoryBoard is not going to be used for OpenStack moving forward,
then no: We should not approve new cores, instead we should move the
project to the attic. Since OpenStack isn't using it, we should not waste
cycles or resources on it, though I encourage the CodeThink team to fork
their own.

If StoryBoard _is_ going to be used for OpenStack, then I personally feel
it should NOT be under the infra program, as membership of that program has
done nothing but slow down progress. In fact, I'm pretty certain that had
StoryBoard been incubated in stackforge instead, it would have make much
more progress, and I would still be working on it.

Michael

On Fri, Jul 10, 2015 at 7:10 AM Thierry Carrez <thierry at openstack.org>
wrote:

> Hi!
>
> As you know, StoryBoard development was mostly abandoned by its original
> development team, following the Infra team decision to no longer make it
> its long-term strategy for OpenStack task tracking.
>
> However, development was recently rebooted by two new contributors: Adam
> Coldrick (SotK) and Zara Zaimeche (Zara_). Their contributions are now
> blocked by the lack of core reviewers. I approved what I could (in
> openstack-infra/storyboard). Their changes and reviews sound solid. But
> that is not really the question: since they are the only two active
> developers on StoryBoard today, I think both should be core reviewers
> for those repositories.
>
> The alternative is to put them into a world of change approval misery as
> they try to convince people who have moved away from StoryBoard to pay
> enough attention to it to allow them to merge their changes. There is
> only so much pain you can endure: it will ultimately result in them
> forking their future development on another platform. To avoid that, I'd
> rather reboot the team completely and give them the keys.
>
> Thoughts ?
>
> --
> Thierry Carrez (ttx)
>
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20150710/ae4c7056/attachment.html>