press release for GSoC participation

wonderer wonderer4711 at
Fri Mar 12 15:06:54 UTC 2010

Hy all,

as I had some time before MKTG FAD starts I take that opportunity to
write some "howto write presstext SOP" (see ) in order
to improve our procedure of marketing / strategics.
So in the future (and also in the past) was such things as "I have a new
spin / event / thingy ... please write some about that..." and I think
we can structurize that process some more.

But now I will get some coffee at the coffee-bar and I hope you fuínd
that helpfull.

mit freundlichen Grüßen / best regards
Henrik Heigl - wonderer at

PGP/GnuPG: 8237 D432 0616 D567 DBC6  3FE3 0D52 B374 F468 A5F0

Am 12.03.2010 19:35, schrieb Karsten Wade:
> Yesterday we turned in our mentoring organization application[1] for
> the 2010 Google Summer of Code[2].  We won't know until next week if
> our umbrella organization is accepted, but we'd like to get ahead on
> preparing a press release.  This idea came from a side discussion with
> Kara, Mel, Paul, and myself.
> The idea is to have a press release to out via the Red Hat press blog
> (, and have it be usable by Fedora and
> Below is the background, and here are some relevant pages.
> This is our plan:  
> This is the in-progress page with information for students, mentors,
> sub-projects, upstreams, and admins:
> Fedora Project and have submitted together as a single
> umbrella organization, which was Google's preference in the past.
> We've worked up some new ideas and plans to fix problems from the
> past, and our goal is to increase both the quantity and quality of
> student projects.
> Bottom line is this: more quality proposals means more that we like
> and rank, which increases the quantity of student slots from Google.
> The better we can simplify and amplify our message, the more of that
> goodness we'll all get to enjoy.
> == Background ==
> I'm working on this because last fall I wrote up a report[3] that
> revealed some surprising and pleasing results.  After that, our
> team[4] agreed it was worth a portion of my time ongoing if we could
> accomplish several goals: improve 2010 GSoC as a proving ground; help
> push out the framework/methods to other projects (such as what RIT is
> doing with our assistance); take lessons and apply them to a larger
> idea of improving mentoring and our ability to take in new
> contributors in a similar way to students.
> For the last few GSoC years Fedora Project has been paired with
> under a single "Red Hat umbrella"; this was Google's choice,
> and reasonable from the perspective of their watching the program's
> size and budget.  Our experience was mixed for two main reasons: no
> previous communication channels between Fedora and JBoss that didn't
> go through Red Hat; different community types and styles.
> is more like the Apache project - a series of upstreams, loosely or
> tightly coupled, that all sit on top of a large number of OSes.
> For this year, the already collected mentors began last fall in
> working out differences and laying plans for resolving previous
> problems.  One example is that we are having mentors and associated
> sub-projects compete directly for student slots based on the strength
> of the student proposal.  I.e., there is no direct attempt to divide
> the slots, some to Fedora, some to JBoss, to create an artificial
> fairness.
> A few of our mentors, Toshio Kuratomi and Yaakov Neemoy, attended the
> Mentor Summit last fall, and brought back ideas and specific plans
> from other umbrella organizations that have had greater success than
> ours has.  For example, KDE has managed around 40 student projects for
> the last few years, compared to our average of 10.
> All of that has brought us to this point, where we need to broadly
> explain to various target audiences the value of working with our
> umbrella organization.
> - Karsten
> [1]
> [2]
> [3]
> [4]

More information about the marketing mailing list