Re: GNOME News



I think we should aim for a minimum of 2 posts a week, and if/when
there is more to post, not hesitate to do so. Whenever big events (ie
GUADEC, GNOME.Asia, etc) occur, its quite likely that we'll have much
more content to publish, and limiting ourselves to 3 or so posts a
week just seems silly. It also sets ourselves up for irrelevance as we
are likely to have time-relative material that only makes sense to
publish around the event. Waiting untill afterwards simply because of
a pre-determined schedule is likely to make it fall into irrelevance
and not get published at all. During GUADEC large portions of our
audience are likely to want releveant and up-to-date posts more so
than at other times.

Using a Google Doc for a rough schedule so as to ensure that we do
have content during the 'dead' periods between releases, conferences,
etc does make sense. I'd be happy to be an editor/reviewer on the site
as I have been doing for the past week or so now. So far its been
great, and everyone I've heard from seems to enjoy them.

I haven't yet committed to any BOF, so the 1st sounds fine to me. What time?

Emily

On Wed, Jul 18, 2012 at 6:18 AM, Allan Day <allanpday gmail com> wrote:
> Emily Gonyer <emilyyrose gmail com> wrote:
>>
>> Meeting at GUADEC sounds like a great idea. When would work for everyone?
>> I don't know of any BOF that I'm 100% attending yet.
>
>
> Yep, a meeting sounds good. I'm fully booked for the first two BoF days
> (30th & 31st of July), but could do the 1st if anyone is free then.
> Otherwise, we can try and organise something informally during the
> conference itself. There should be time.
>
> It might also be good to continue the discussion here - that'll give people
> who won't be at GUADEC (/ME waves to Sri and Christy) a chance to comment,
> and will maybe help to spur discussion when we do meet. So let me sketch a
> rough plan for how news could work...
>
> A key goal here needs to be keeping any system we have a simple and
> lightweight as possible, while still ensuring a regular stream of engaging
> and high-quality posts. Some ideas:
>
>  * We aim to have about three posts a week, including a mix of short and
> long posts on different subjects
>  * We have a set of guidelines on when to post (ie. mid-week, preferably
> during daylight for North America and Europe)
>  * We have a small editorial team consisting of three or four people
>  * The schedule for posts is planned in advance by the editorial team at a
> monthly IRC meeting
>  * Each post has an assigned author and editor. It is the editor's job to
> ensure that the post is delivered on time and that it is checked for quality
> before posting.
>  * If a post does not meet its deadline, we publish something else instead
> (hopefully from a queue of backup material) and keep it in a holding pattern
> until a space in the schedule becomes available
>  * The editors maintain a document containing ideas for content, which
> anyone can add to. This gets reviewed at each monthly editorial meeting
>
> The existing gnome.org site provides almost all the infrastructure we need
> for this to happen. We can use it to store all our queued material (perhaps
> with a separate category for backup posts). We can easily use it to give
> people author and editor roles.
>
> Our list of post ideas can be a simple wiki page on live.gnome.org.
>
> The only infrastructure question is where to keep the publishing schedule.
> My personal view is that something semi-private to the editorial team is
> best for this; a Google Doc would work well, although maybe there's a free
> option that could work?
>
> Thoughts? Opinions?
>
> Allan
> --
> IRC:  aday on irc.gnome.org
> Blog: http://afaikblog.wordpress.com/
>
>
> --
> marketing-list mailing list
> marketing-list gnome org
> https://mail.gnome.org/mailman/listinfo/marketing-list
>



-- 
Whatever you can do, or dream you can, begin it. Boldness has genius,
power and magic in it. -  Goethe

Be who you are and say what you feel because those who mind don't
matter and those who matter don't mind. - Dr.Seuss

Not everything that can be counted counts, and not everything that
counts can be counted. - Albert


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