Fwd: Re: Google Summer of Code press blog
FYI - see below. Short version is that the Marketing team will soon get
to practice its collaborative press release writing skillz with Kara for
the Summer of Code announcement.
-------- Original Message --------
Subject: Re: Google Summer of Code press blog
Date: Fri, 26 Feb 2010 13:54:38 -0500
From: Kara Schiltz <kschiltz(a)redhat.com>
Reply-To: kschiltz(a)redhat.com
Organization: Red Hat
To: Mel Chua <mel(a)redhat.com>
CC: Karsten Wade <kwade(a)redhat.com>, "Paul W. Frields"
<pfrields(a)redhat.com>
This all sounds good to me. I can start working up some questions.
Thanks,
Kara
Mel Chua wrote:
This all sounds totally awesome to me - would it be ok to forward
this
thread to
https://admin.fedoraproject.org/mailman/listinfo/summer-coding to keep
other GSoC organizers/mentors in the loop of what's going on with PR
for this, and to
https://admin.fedoraproject.org/mailman/listinfo/marketing so folks
interested in press release writing can lend a hand?
Re: collaborative writing - breaking it into a list of questions
sounds great, and then maybe we can have a gobby (collaborative text
editor) sprint to weave everything together? This does sound like a
great opportunity for us to try out more collaborative-PR stuff.
--Mel
On 02/25/2010 05:31 PM, Kara Schiltz wrote:
> Thanks, Karsten. This is great. I'll put a placeholder on our PR
> pipeline for a GSoC press blog. I'm thinking we should be ready to go
> with a shell for the blog and then we can just plug in Fedora as a
> mentoring organization once Google makes the announcement on March 14.
> That would allow us to maximize our time during the student application
> window 3/14-3/29.
> I'm up for suggestions on how to make this a collaborative project.
> Maybe we pose a list of questions (who, what, when, where, why, etc) and
> have folks break it up and each take a question to respond to? We can
> then take those responses and weave them together into a press blog. I'm
> open to any suggestions!
>
> Thanks,
> Kara
>
> Karsten Wade wrote:
>> On Thu, Feb 25, 2010 at 01:53:05PM -0500, Kara Schiltz wrote:
>>> Hi Karsten,
>>>
>>> Wanted to follow up on the GSoC Activity Day at SCALE last week. What
>>> are your thoughts on doing a press blog sometime in March that's
>>> focused on Google Summer of Code and what our plans are for 2010? We
>>> could also tie in more about success and participation in prior
>>> years. Let me know if enough details were fleshed out at SCALE to
>>> create a compelling press blog on GSoC.
>>
>> Kara,
>>
>> This sounds like a good idea. We need to wait until at least 14
>> March, after Google announces mentoring organizations. We presume
>> we're natural to be on it, once we've applied, but there is never a
>> guarantee.
>>
>> I'm including Mel on this because she is working on the GSoC project
>> for the next week or so, and can help make sure we get this on the
>> GSoC part of the Fedora Calendar. We could work it up as a next
>> iteration on collaborative press release writing. :)
>>
>> Once we are sure we're in as a mentoring organization, there is a
>> window until 29 March when student applications open. This is a prime
>> time for generating publicity to target audiences:
>>
>> * Educators who can inform their students;
>> * Students to work up quality proposals;
>> * Existing community members to consider being a student in the
>> program;
>> * Existing community sub-projects who work with mentors;
>> * Industry and other mentoring organizatiokns to notice what and how
>> we're doing things while they are still happening.
>>
>> Having the 5-year report I did end of last year[1] is also good
>> material to point at.
>>
>> By focusing on the essential audiences, I can see this being useful to
>> the Fedora and JBoss efforts, all while demonstrating trusted open
>> source leadership in action.
>>
>> - Karsten
>>
>> [1] My post and the report, which was derived from an internal report:
>>
>>
http://iquaid.org/2009/11/04/summer-coding-benefits-to-fedora-project-and...
>>
>>
>> https://fedoraproject.org/wiki/GSoC_report_2009
>>
>