osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ironic] Moving to office hours as opposed to weekly meetings for the next month


Hi Julia,

Thank you for your email and apologies for delayed response on my side.

It is tricky indeed. I see two potential ways going forward:

- going back to the weekly meeting convention and alternating between two
time slots (similarly to what Scientific SIG and Neutron folks do)
- an additional "sync up" time for the APACs, as you suggested. It could be
a smaller weekly meeting or just an agreed time window (or windows) when
the APAC contributors can reach out to the key team members for direction
etc. From my perspective the key bit is being able to reach out to someone
who will be able to guide me on how best go about the work packages I've
taken up etc.

What are your thoughts on these?

Best Regards,
Jacob

On Mon, Jul 29, 2019 at 9:56 PM Julia Kreger <juliaashleykreger at gmail.com>
wrote:

> Hi Jacob,
>
> Sorry for the delay. My hope was that APAC contributors would coalesce
> around a time, but it really seems that has not happened, and I am
> starting to think that the office hours experiment has not really
> helped as there has not been a regular reminder each week. :(
>
> Happy to discuss more, but perhaps a establishing a dedicated APAC
> sync-up meeting is what is required?
>
> Thoughts?
>
> -Julia
>
> On Wed, Jul 17, 2019 at 5:44 AM Jacob Anders <jacob.anders.au at gmail.com>
> wrote:
> >
> > Hi Julia,
> >
> > Do we have more clarity regarding the second (APAC) session? I see the
> polls have been open for some time, but haven't seen a mention of a
> specific time.
> >
> > Thank you,
> > Jacob
> >
> > On Wed, Jul 3, 2019 at 9:39 AM Julia Kreger <juliaashleykreger at gmail.com>
> wrote:
> >>
> >> Greetings Everyone!
> >>
> >> This week, during the weekly meeting, we seemed to reach consensus that
> >> we would try taking a break from meetings[0] and moving to orienting
> >> around using the mailing list[1] and our etherpad "whiteboard" [2].
> >> With this, we're going to want to re-evaluate in about a month.
> >> I suspect it would be a good time for us to have a "mid-cycle" style
> >> set of topical calls. I've gone ahead and created a poll to try and
> >> identify a couple days that might be ideal for contributors[3].
> >>
> >> But in the mean time, we want to ensure that we have some times for
> >> office hours. The suggestion was also made during this week's meeting
> >> that we may want to make the office hours window a little larger to
> >> enable more discussion.
> >>
> >> So when will we have office hours?
> >> ----------------------------------
> >>
> >> Ideally we'll start with two time windows. One to provide coverage
> >> to US and Europe friendly time zones, and another for APAC contributors.
> >>
> >> * I think 2-4 PM UTC on Mondays would be ideal. This translates to
> >>   7-9 AM US-Pacific or 10 AM to 12 PM US-Eastern.
> >> * We need to determine a time window that would be ideal for APAC
> >>   contributors. I've created a poll to help facilitate discussion[4].
> >>
> >> So what is Office Hours?
> >> ------------------------
> >>
> >> Office hours are a time window when we expect some contributors to be
> >> on IRC and able to partake in higher bandwidth discussions.
> >> These times are not absolute. They can change and evolve,
> >> and that is the most important thing for us to keep in mind.
> >>
> >> --
> >>
> >> If there are any questions, Please let me know!
> >> Otherwise I'll send a summary email out on next Monday.
> >>
> >> -Julia
> >>
> >> [0]:
> http://eavesdrop.openstack.org/meetings/ironic/2019/ironic.2019-07-01-15.00.log.html#l-123
> >> [1]:
> http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007038.html
> >> [2]: https://etherpad.openstack.org/p/IronicWhiteBoard
> >> [3]: https://doodle.com/poll/652gzta6svsda343
> >> [4]: https://doodle.com/poll/2ta5vbskytpntmgv
> >>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190806/3cfdf514/attachment-0001.html>