Open Stack

On Thu, Mar 16, 2017 at 8:19 AM, Jim Rollenhagen <jim at jimrollenhagen.com>
wrote:

> On Thu, Mar 16, 2017 at 5:17 AM, Thierry Carrez <thierry at openstack.org>
> wrote:
>
>> Jim Rollenhagen wrote:
>> > On Wed, Mar 15, 2017 at 8:15 AM, John Garbutt <john at johngarbutt.com
>> > <mailto:john at johngarbutt.com>> wrote:
>> >>     In the absence of tooling, could we replace the meeting with weekly
>> >>     email reporting current working streams, and whats planned next?
>> That
>> >>     would include fixing any problems we face trying to work well
>> >>     together.
>> >
>> > This is a good idea, I've quite liked cdent's weekly placement update,
>> > maybe something similar, and others can chime in with their own
>> updates/etc.
>>
>> I was thinking we could use a status board to track the various
>> activities / objectives / threads. As part of the status board the
>> leader of each thread would provide a $time_interval update by a given
>> deadline, and the workgroup chair would collect them all and post them
>> (to a single email) on the ML.
>>
>
> ++
>
>

I'm fine with this - I actually think it would be helpful for me, since
it's more likely I'll make an hour of time here and there throughout a week
to get work and updates done. I'm especially fine with it if it means more
participation in the SWG from the community because we move towards other
ways of collaborating that allow for time zone/scheduling differences.



>
>> The update could have predetermined sections: current status / progress,
>> assigned actions, open questions... If the open questions can't get
>> solved in the ML thread resulting from the $time_interval update, *then*
>> schedule an ad-hoc discussion on #openstack-swg between interested
>> parties.
>>
>> In terms of tooling, we can start by using a wiki page for tracking and
>> updates snippets. We can use framadate.org for ad-hoc discussion
>> scheduling.
>>
>
> Any reason not to just use storyboard for tracking? AIUI, it gives us a
> status
> board for free.
>
> // jim
>

I'm fine with trying whatever the group prefers for a couple of weeks,
assessing, and then continuing with something else or trying a different
tool.


I think we should probably just cancel today's meeting, though, since it
seems like most people are pretty booked anyhow.


-colette



>
>
>>
>> Combined with extra activity on the channel, I think that would preserve
>> all 3 attributes of the meeting (especially the $time_interval regular
>> kick in the butt to make continuous progress).
>>
>> --
>> Thierry Carrez (ttx)
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170316/c4fd7dde/attachment.html>