Magazine meeting posts

[Chris A. Roberts]

Hi everyone,

In today's meeting we talked about changing how we do meetings from just posting the minutes to the site, to doing a weekly recap. Nirik came up with this awesome suggestion and I +1 it. My thoughts are someone can come in and get a better idea of what has happened that week in just one spot rather than sort through all the meeting notes.

Thoughts or flames?

Chris Roberts 
Fedora Marketing/Websites/Videos/Infrastructure Team 
https://fedoraproject.org/wiki/User:Chrisroberts

[Pete Travis]

On Oct 21, 2013 2:01 PM, "Chris A. Roberts" 
wrote:
> Hi everyone,
>
> In today's meeting we talked about changing how we do meetings from just

posting the minutes to the site, to doing a weekly recap. Nirik came up
with this awesome suggestion and I +1 it. My thoughts are someone can come
in and get a better idea of what has happened that week in just one spot
rather than sort through all the meeting notes.
> Thoughts or flames?
>
> Chris Roberts
> Fedora Marketing/Websites/Videos/Infrastructure Team
> https://fedoraproject.org/wiki/User:Chrisroberts

I think a curated synopsis is a bunch better idea.  There's already a
meeting-minutes list and archive for those that want to slog through it
all, and frankly, posting the raw logs gives the impression of favoring
quantity of content over polish.

Of course, I say this as someone that probably doesn't have a lot of time
for the effort.  I can come up with the copy for meetings I run, I suppose.

--Pete
--

[Adam Williamson]

On Mon, 2013-10-21 at 15:28 -0600, Pete Travis wrote:
> On Oct 21, 2013 2:01 PM, "Chris A. Roberts"
>  wrote:
> > Hi everyone,
> >
> > In today's meeting we talked about changing how we do meetings from
>
> just posting the minutes to the site, to doing a weekly recap. Nirik
> came up with this awesome suggestion and I +1 it. My thoughts are
> someone can come in and get a better idea of what has happened that
> week in just one spot rather than sort through all the meeting notes.
> > Thoughts or flames?
> >
> > Chris Roberts
> > Fedora Marketing/Websites/Videos/Infrastructure Team
> > https://fedoraproject.org/wiki/User:Chrisroberts
>
> I think a curated synopsis is a bunch better idea.  There's already a
> meeting-minutes list and archive for those that want to slog through
> it all, and frankly, posting the raw logs gives the impression of
> favoring quantity of content over polish.
>
> Of course, I say this as someone that probably doesn't have a lot of
> time for the effort.  I can come up with the copy for meetings I run,
> I suppose.

Indeed, it's a nice idea but it is a non-negligible amount of work for a
human to commit to. I used to do something similar for the QA FWN beat,
and it's not a five minute job; it'd probably be a few hours to try and
synthesize elegantly all the stuff that happened in a week of Fedora
project meetings...

[Ruth Suehle]

> > I think a curated synopsis is a bunch better idea.  There's already a
> > meeting-minutes list and archive for those that want to slog through
> > it all, and frankly, posting the raw logs gives the impression of
> > favoring quantity of content over polish.
> >
> > Of course, I say this as someone that probably doesn't have a lot of
> > time for the effort.  I can come up with the copy for meetings I run,
> > I suppose.
>
> Indeed, it's a nice idea but it is a non-negligible amount of work for a
> human to commit to. I used to do something similar for the QA FWN beat,
> and it's not a five minute job; it'd probably be a few hours to try and
> synthesize elegantly all the stuff that happened in a week of Fedora
> project meetings...

Absolutely agreed. It's a wonderful idea if someone can do it, but that's not a trivial undertaking on a weekly basis.

[Gabriele Trombini]

On 10/22/13 00:21, Adam Williamson wrote:

[snip]
> Indeed, it's a nice idea but it is a non-negligible amount of work for a
> human to commit to. I used to do something similar for the QA FWN beat,
> and it's not a five minute job; it'd probably be a few hours to try and
> synthesize elegantly all the stuff that happened in a week of Fedora
> project meetings...

I think it would be nice identify people who wants be the connection 
between groups and marketing before starting doing this.

As Adam said (I can confirm because I did the same in my blog, 
drastically interrupted) it's very difficult taking time for summarize 
the weekly work, we all can do this for few weeks then time will be longer.

Isn't it the case to create a template somewhere in the wiki (or in the 
track) where informations could be filled in? A sort of guided 
information request that someone of the marketing team could then insert 
in the magazine, so the work will be subdivided.

Greetings

Gabri

[Joe Brockmeier]

On Mon, Oct 21, 2013 at 01:01:49PM -0700, Chris A. Roberts wrote:
> Hi everyone,
>
> In today's meeting we talked about changing how we do meetings from just
> posting the minutes to the site, to doing a weekly recap. Nirik came up with
> this awesome suggestion and I +1 it. My thoughts are someone can come in and
> get a better idea of what has happened that week in just one spot rather than
> sort through all the meeting notes.
>
> Thoughts or flames?

Any chance we can get meeting chairs to write a one or two-graf summary
of the meetings they run? That would be the best way to handle it. I
agree that it's a big undertaking to try to go through all the
logs/minutes and write summaries, especially for meetings that the
writer didn't attend.

Best,

jzb

[Zacharias Mitzelos]

I like the idea jzb suggested, but we would have to make it mandatory for all meeting chairs
+1 ;)
> Date: Tue, 22 Oct 2013 09:42:51 +0100
> From: [e-mail]
> To: [e-mail]
> Subject: Re: Magazine meeting posts
>
> On Mon, Oct 21, 2013 at 01:01:49PM -0700, Chris A. Roberts wrote:
> > Hi everyone,
> >
> > In today's meeting we talked about changing how we do meetings from just
> > posting the minutes to the site, to doing a weekly recap. Nirik came up with
> > this awesome suggestion and I +1 it. My thoughts are someone can come in and
> > get a better idea of what has happened that week in just one spot rather than
> > sort through all the meeting notes.
> >
> > Thoughts or flames?
>
> Any chance we can get meeting chairs to write a one or two-graf summary
> of the meetings they run? That would be the best way to handle it. I
> agree that it's a big undertaking to try to go through all the
> logs/minutes and write summaries, especially for meetings that the
> writer didn't attend.
>
> Best,
> jzb
>
> Joe Brockmeier | Open Source and Standards, Red Hat
> [e-mail] | http://community.redhat.com/
> Twitter: @jzb  | http://dissociatedpress.net/
> -- 
> marketing mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/marketing

[Joe Brockmeier]

On Tue, Oct 22, 2013 at 01:08:22PM +0300, Zacharias Mitzelos wrote:
> I like the idea jzb suggested, but we would have to make it mandatory for all
> meeting chairs

Maybe not mandatory, but just say "if you'd like to see your meeting
highlighted on the magazine, can you help us?"

Note, we should be ready to help edit/proofread the summaries for anyone
who asks.

Best,

jzb

[Matthew Miller]

On Tue, Oct 22, 2013 at 01:08:22PM +0300, Zacharias Mitzelos wrote:
> I like the idea jzb suggested, but we would have to make it mandatory for
> all meeting chairs +1 ;)

How would that be enforced?

[Ankur Sinha]

On Tue, 2013-10-22 at 13:16 -0400, Matthew Miller wrote:
> On Tue, Oct 22, 2013 at 01:08:22PM +0300, Zacharias Mitzelos wrote:
> > I like the idea jzb suggested, but we would have to make it
>
> mandatory for
> > all meeting chairs +1 ;)
>
> How would that be enforced?

-1 to making it mandatory. It's our(mktgs) job to keep tabs on what's
going on in the community and filter out what's worth using.

If you've read the recent thread on -devel/-ambassadors about liaisons
from ambassadors in the WGs, we've got to do something similar. Everyone
just pick a team they're interested in and attend the meetings/read
their logs and report it to mktg so they can be published on the
magazine. The only way we'll get anywhere close to covering the entire
community is if we spread out.

I'll try and keep tabs on the Workstation WG. They had their first
meeting recently. I'll have a summary up by tonight. I'm already keeping
tabs on APAC, but we haven't had anything that's really worth putting up
on the magazine yet.

[Chris A. Roberts]

Ankur +1

I am part of a few other teams and have been keeping tabs on their meetings and post summary's to go along with the notes/logs. I will add a table on the magazine wiki page for the different meetings and spot for people to list their names for the groups that they watch. I know a few of us help out in different areas of the project, so that could make the process easier.

- Chris Roberts 
----- Original Message -----

From: "Ankur Sinha"  
To: [e-mail] 
Sent: Wednesday, October 30, 2013 9:09:43 PM 
Subject: Re: Magazine meeting posts

On Tue, 2013-10-22 at 13:16 -0400, Matthew Miller wrote:
> On Tue, Oct 22, 2013 at 01:08:22PM +0300, Zacharias Mitzelos wrote:
> > I like the idea jzb suggested, but we would have to make it
>
> mandatory for
> > all meeting chairs +1 ;)
>
> How would that be enforced?

-1 to making it mandatory. It's our(mktgs) job to keep tabs on what's 
going on in the community and filter out what's worth using.

If you've read the recent thread on -devel/-ambassadors about liaisons 
from ambassadors in the WGs, we've got to do something similar. Everyone 
just pick a team they're interested in and attend the meetings/read 
their logs and report it to mktg so they can be published on the 
magazine. The only way we'll get anywhere close to covering the entire 
community is if we spread out.

I'll try and keep tabs on the Workstation WG. They had their first 
meeting recently. I'll have a summary up by tonight. I'm already keeping 
tabs on APAC, but we haven't had anything that's really worth putting up 
on the magazine yet.

[Matthew Miller]

On Tue, Oct 22, 2013 at 09:42:51AM +0100, Joe Brockmeier wrote:
> Any chance we can get meeting chairs to write a one or two-graf summary
> of the meetings they run? That would be the best way to handle it. I
> agree that it's a big undertaking to try to go through all the
> logs/minutes and write summaries, especially for meetings that the
> writer didn't attend.

Maybe we could encourage a brief summary to be included as part of the
minutes via some zodbot command?