On Fri, Dec 18, 2015 at 2:24 PM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On 12/18/2015 04:38 AM, Gabriele Trombini wrote:
> Il giorno gio, 17/12/2015 alle 20.05 -0500, Justin W. Flory ha scritto:
>> On 12/17/2015 04:42 PM, Joe Brockmeier wrote:
>>> On 12/17/2015 02:53 PM, Justin W. Flory wrote:
> Hi guys,
>>>> I see. How often were meetings happening in the past? From my
>>>> perspective, I think maybe the frequency as well as the
>>>> pre-meeting plans could be adjusted. I know for the CommOps
>>>> group, we
>>>> have a very rough outline of "things to cover" in the meetings
>>>> a wiki
>>>> outline. Additionally, having ticket-oriented meetings also seems
>>>> have had decent success with the Design Team. Perhaps we could
>>>> try to
>>>> incorporate tickets as a central part of our meetings?
>>> Tickets wouldn't hurt. It's been a while so I don't recall how
>>> were using Trac at the time, but it couldn't hurt.
>>> It seems to me it was weekly for a while, then bi-weekly. Again,
>>> been a long while (2013, early 2014 maybe?) and a new flock of
>>> to help kickstart.
>> With what you and Ruth said, it seems like it might be a good idea to
>> space meetings on a monthly basis, and maybe increase frequency in
>> month / two months before the release?
>> I think the next step might be to put a potential meeting date and
>> timeslot on the map for 2016.
> I'm ok with a ticket based meetings (in effect I'm using tickets as a
> to do list yet). Let me make some considerations:
> 1) at present few people from magazine is working on marketing as well;
> 2) in these days I'm looking at the wiki and we need a renovation about
> that. There are a lot of pages I didn't know they existed;
Yes. We definitely need to overhaul the wiki...
CommOps will add this to our "WikiGardening" section for our next
meeting (after the new year.) We could still use a battle plan though,
in addition to refreshing and revamping old SoP's, and other mktg
content I we already know to be out of date.
> 3) maybe we should plan meeting time based on our tasks, and
> only for parsing tickets;
Not sure I fully grok what you're suggesting here. I think you're saying
monthly meeting to go through tickets, but no sure about "plan meeting
time based on our tasks."
Ticket based meetings work well for design, and have worked decently
well for CommOps thusfar too. We didn't use this model at first
because our team infrastructure wasn't quite up to speed (people or
tech wise) but I think we've gotten the hang of it now. I would def
recommend bi-weekly, ticket based meetings, at the very least. CommOps
will ship a "whenisgood" poll for this in the near future to nail down
> 4) in order to have a clear marketing meeting I think it
don't have to
> include magazine (magazine meetings can goin'on as usual).
Yeah, I think the magazine folks have a system that's working and don't
want to tamper with that. This would be for all other marketing issues,
and if we have something specific to the magazine we can hit up that
Yes, def agree with jzb here. Magazine is rocking and rolling, and we
want that to continue humming along at full-speed :)
Fedora Community Lead & Council