My tool of choice is vagrant - it's super easy to create a Vagrantfile,
write a quick shell script that idempotently installs any required puppet
modules, and then run puppet itself. An older example is the
puppet-storyboard module: git checkout, vagrant up, and you're off to the
races.
On Fri, Jul 10, 2015 at 8:29 AM Michael Krotscheck krotsch...@gmail.com
wrote:
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.
I stand corrected on this (via
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
This proposal is all well and good, however (no offense intended) Monty's
got a history of putting out neat proposals and leaving someone else to
support it. Without identifying a dedicated person/resource that will
maintain phabricator, any discussion is moot.
Michael
On Fri, Apr 3, 2015 at
Hey everyone!
It's quite rough to realize that the thing you've been advocating, working
on, and desperately trying to recruit contributors for is DoA, and that's
what I've been struggling with for the past few weeks. Even so, I was part
and parcel to coming up with Monty's recommendation, so
Hello everyone!
StoryBoard is the much anticipated successor to Launchpad, and is a
component of the Infrastructure Program. The storyboard-core group is
intended to be a superset of the infra-core group, with additional
reviewers who specialize in the field.
Yolanda has been working on
Hey there, Jay-
The use case is telling someone where they are in a result set, not
necessarily the ability to jump pages. Say, for example, a PTL who is
reviewing all the stories in their project to determine which of them are
no longer relevant. To them, a very simple You are on #X of #YYY
For API clients that require access to large parts of the data set, I've
actually proposed a solution that doesn't involve the REST API at all. It's
likely that this particular spec will also be the backbone of storyboard's
federation (assuming we don't argue it into oblivion).
The OpenStack Infrastructure team has successfully migrated all of the
openstack-infra project bugs from LaunchPad to StoryBoard. With the exception
of openstack-ci bugs tracked by elastic recheck, all bugs, tickets, and work
tracked for OpenStack Infrastructure projects must now be submitted
Jay-
My own UX tests have demonstrated a need for both page jumping, and being
able to communicate to a user where they are in their list. I'd be happy to
show you the videos if you have a few hours.
Michael
___
OpenStack-Infra mailing list
On Sep 29, 2014, at 3:24 PM, Monty Taylor mord...@inaugust.com wrote:
I am a big fan of the tooling pattern in storyboard-webclient - since
it's very much aimed at solving this. Some combination of krotscheck and
I will make an example patch we can all point at.
I’ve added a WIP patch that
11 matches
Mail list logo
