Re: Marketing Tasks

[Claus Schwarm <clschwarm googlemail com>]

I'm not saying we should use the template of the release team -- that's
clearly over-engineered. :-)

A simple list like the one for the GnomeWeb is sufficient. Headers and
bullet points. Shouldn't take more than an hour or two to move your
contents.

(But yes, it would be nice if someone could volunteer for this.)

I think it would also work for campaigns. The beginning of a new
campaign is usually the end of the old one, if they both use the same
resource. If they don't, a clean-up day for the old campaign needs to be
scheduled, anyway.


Best regards,
Claus

On Thu, 2009-06-25 at 10:53 -0500, Paul Cutler wrote:
> 
> Two things - I looked at the wiki markup and ran away as fast as I
> could.  I need help with this, I'm not an expert MoinMoin user, and
> even though we have a template for this from the Release & Web teams,
> it's going to take someone a few hours to get this done.  You're right
> though, it would be a good thing to be consistent with what the
> Release & Web teams are using.  The second question I had was would
> this work for campaigns?  I'm thinking we have to clearly define the
> time period when we do the work, as well as the beginning and end of a
> campaign.  Or am I overthinking this?
> 
> Any volunteers?  This needs to be more than a one person job.
> 
> Paul
> 
> On Thu, Jun 25, 2009 at 5:25 AM, Claus Schwarm
> <clschwarm googlemail com> wrote:
>         I like your idea of organizing tasks due to due dates.
>         
>         But why don't we just sync with the regular release schedule?
>         I've seen
>         something like this for the GnomeWeb here:
>         
>         http://live.gnome.org/GnomeWeb/TwoPointTwentyseven
>         
>         And I like it. It's easy to pick the dates one wants to care
>         about.
>         
>         
>         This gives us also the opportunity to have a sort of template,
>         so making
>         a new schedule for the next release is simply a matter of
>         copy'n'paste
>         instead of having someone re-collect all the data every year.
>         For
>         example, I didn't see the dates for making the release notes
>         in your
>         task calender.
>         
>         So, I'd suggest we drop
>         
>         http://live.gnome.org/GnomeMarketing/Tasks/MarketingTasks2009
>         
>         
>         and start something like this
>         
>         http://live.gnome.org/GnomeMarketing/Schedule/TwoPointTwentyseven
>         http://live.gnome.org/GnomeMarketing/Schedule/TwoPointTwentynine
>         http://live.gnome.org/GnomeMarketing/Schedule/ThreePointOne
>         
>         This may also help us to figure out what tasks need to be done
>         before
>         other tasks. Maybe we can use colors to distinguish between
>         certain
>         classes of tasks if that's needed.
>         
>         I'd also suggest to delete items on the task list that are
>         done. For
>         example, the brochure for sponsors is done, AFAIK. There's no
>         need to
>         keep it one the list, then.
>         
>         
>         Best regards,
>         Claus
>         
>         
>         
>         
>         
>         On Wed, 2009-06-24 at 22:12 -0500, Paul Cutler wrote:
>         > Hi Marketing Team,
>         >
>         > I don't know if anyone has had an opportunity lately to
>         review the
>         > list of Tasks on the Marketing page on live.gnome.org at
>         > http://live.gnome.org/GnomeMarketing/Tasks.  There are a lot
>         of great
>         > ideas, and it's organized by active tasks, non-active and
>         then by
>         > one-time tasks and ongoing tasks.
>         >
>         > It can be a bit overwhelming browsing through everything we
>         want to
>         > do!
>         >
>         > I don't know about you, but I organize stuff a little
>         differently, and
>         > I'm a little more goal oriented, so I re-organized some of
>         the tasks
>         > and tried to assign due dates.  You can review at
>         >
>         http://live.gnome.org/GnomeMarketing/Tasks/MarketingTasks2009
>         >
>         > I've also continued to work on GNOME 3.0 Marketing.  A
>         couple days ago
>         > I posted a link to some potential campaign ideas, and that
>         ties to
>         > marketing calendar I've started in OpenOffice.org.  It
>         includes
>         > potential marketing vehicles and outlines development time
>         for the
>         > various vehicles and launch dates.  The download link is
>         posted on
>         > http://live.gnome.org/GnomeThreeBrainstorming
>         >
>         > Help I need from the marketing team:
>         >
>         > * Review the marketing campaign ideas and give feedback
>         > (http://live.gnome.org/GnomeThreeBrainstorming)
>         > * Review the marketing calendar and give feedback
>         > (http://live.gnome.org/GnomeThreeBrainstorming) (What is
>         missing?  Do
>         > we have enough time built in for planning and developing
>         these
>         > activities?  Are they the right activities, and what you
>         recommend?)
>         > * Review the current task list
>         > (http://live.gnome.org/GnomeMarketing/Tasks)  (Is it up to
>         date?  If
>         > your name is on something, are you still working on it?
>          What else
>         > should we be thinking about?)
>         > * Review the 2009 tasks
>         >
>         (http://live.gnome.org/GnomeMarketing/Tasks/MarketingTasks2009) (Are
>         > they prioritized correctly, or should some tasks move
>         months?  What
>         > else would you want to add?  Change?)
>         >
>         > They're wiki pages, so please feel free to edit, or give
>         feedback via
>         > email.
>         >
>         > Thanks!
>         >
>         > Paul
>         
>         
>         > --
>         > marketing-list mailing list
>         > marketing-list gnome org
>         > http://mail.gnome.org/mailman/listinfo/marketing-list
>         
>         
>