[Gluster-users] [Gluster-devel] New style community meetings - No more status updates

[Atin Mukherjee]

Its a +1 from me, however this model will be only successful if we
diligently provide component updates.

On Tuesday 25 October 2016, Kaushal M <kshlmster at gmail.com> wrote:

> On Fri, Oct 21, 2016 at 11:46 AM, Kaushal M <kshlmster at gmail.com
> <javascript:;>> wrote:
> > On Thu, Oct 20, 2016 at 8:09 PM, Amye Scavarda <amye at redhat.com
> <javascript:;>> wrote:
> >>
> >>
> >> On Thu, Oct 20, 2016 at 7:06 AM, Kaushal M <kshlmster at gmail.com
> <javascript:;>> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> Our weekly community meetings have become mainly one hour of status
> >>> updates. This just drains the life out of the meeting, and doesn't
> >>> encourage new attendees to speak up.
> >>>
> >>> Let's try and change this. For the next meeting lets try skipping
> >>> updates all together and instead just dive into the 'Open floor' part
> >>> of the meeting.
> >>>
> >>> Let's have the updates to the regular topics be provided by the
> >>> regular owners before the meeting. This could either be through
> >>> sending out emails to the mailing lists, or updates entered into the
> >>> meeting etherpad[1]. As the host, I'll make sure to link to these
> >>> updates when the meeting begins, and in the meeting minutes. People
> >>> can view these updates later in their own time. People who need to
> >>> provide updates on AIs, just update the etherpad[1]. It will be
> >>> visible from there.
> >>>
> >>> Now let's move why I addressed this mail to this large and specific
> >>> set of people. The people who have been directly addressed are the
> >>> owners of the regular topics. You all are expected, before the next
> >>> meeting, to either,
> >>>  - Send out an update on the status for the topic you are responsible
> >>> for to the mailing lists, and then link to it on the the etherpad
> >>>  - or, provide you updates directly in the etherpad.
> >>> Please make sure you do this without fail.
> >>> If you do have anything to discuss, add it to the "Open floor" section.
> >>> Also, if I've missed out anyone in the addressed list, please make
> >>> sure they get this message too.
> >>>
> >>> Anyone else who wants to share their updates, add it to the 'Other
> >>> updates' section.
> >>>
> >>> Everyone else, go ahead and add anything you want to ask to the "Open
> >>> floor" section. Ensure to have your name with the topic you add
> >>> (etherpad colours are not reliable), and attend the meeting next week.
> >>> When your topic comes up, you'll have the floor.
> >>>
> >>> I hope that this new format helps make our meetings more colourful and
> >>> lively.
> >>>
> >>> As always, our community meetings will be held every Wednesday at
> >>> 1200UTC in #gluster-meeting on Freenode.
> >>> See you all there.
> >>>
> >>> ~kaushal
> >>>
> >>> [1]: https://public.pad.fsfe.org/p/gluster-community-meetings
> >>
> >>
> >> I really like this idea and am all in favor of color + liveliness.
> >> Let's give this new format three weeks or so, and we'll review around
> >> November 9th to see if we like this experiment.
> >> Fair?
> >> -- amye
> >
> > Sounds good to me.
> >
>
> Okay. We have one more day to the meeting, but I've yet to see any
> updates from all of you.
> Please ensure that you do this before the meeting tomorrow.
>
> >>
> >> --
> >> Amye Scavarda | amye at redhat.com <javascript:;> | Gluster Community Lead
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org <javascript:;>
> http://www.gluster.org/mailman/listinfo/gluster-devel
>


-- 
--Atin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20161025/11506031/attachment.html>