I'm re-posting this. The previous attempt bounced (which was sent as [email protected]).
-- ralph ---------- Forwarded message ---------- From: Ralph Morelli <[email protected]> Date: Sun, Jan 31, 2010 at 5:48 PM Subject: Re: [TOS] OSCON 2010 : One proposal submitted, and posted in the Wiki To: Luis Ibanez <[email protected]> Cc: Karsten Wade <[email protected]>, [email protected] Luis, Just want to make sure I understand the OSCON proposal process. We should each individually submit proposals to OSCON. So I will go ahead and submit a proposal for the panel on "Teaching FOSS To Undergraduates" (I like that title better than "What should be taught in a FOSS course"). In the proposal itself, do we mention the Education Track proposal, TOS?? Where should we do that? How does that work? I'll get this submitted this evening with the information we have, which is incomplete. I still don't have a name for a representative from IBM and I haven't been able to confirm with Leslie Hawthorn regarding her participation. Do either of you know whether the proposal can be revised once it's been submitted? Thanks, -- ralph On Fri, Jan 29, 2010 at 4:02 PM, Luis Ibanez <[email protected]>wrote: > FYI > > Following Karsten's guidelines, > I just submitted to OSCON 2010 the abstract on: > > "Educating the next generation of FOSS developers" > > http://teachingopensource.org/index.php/OSCON_2010#Educating_the_next_generation_of_FOSS_developers > > and added to the Wiki the exact text of the final proposal: > > http://teachingopensource.org/index.php/OSCON_2010/Educating_the_next_generation_of_FOSS_developers > > > Freel free to use it as a model, but beware that this is > the first time I write a proposal for OSCON.... so if you > have better experience (or better sources of advice), > you may not want to rely too much in these links above. :-) > > > Luis > > > ----------------------------------------------------------------------- > 2010/1/18 Karsten Wade <[email protected]>: > > Below is the information on how to propose an education track. > > > > Let's get all our plans lined up on the wiki within the next week, but > > any of us can begin submitting using the guidelines below. > > > > * Include a link to our central page in "Additional Notes"; > > * Put "Education" in the tags field. > > > > Just so we don't step on each other, shall we at least provide each > > other this: > > > > 1. Title > > 2. Mini-asbtract (~255 characters) > > > > ... by the end of this week (Fri. 22 Jan) > > > > We'll then plan to have the web page tightened up as it can be by the > > following Monday. The main reason to give us until this Friday before > > any (more) of us submit talks is to (i) coordinate complementary > > talks, and (ii) share ideas so we have better abstracts in aggregate. > > > > ----- Forwarded message > > > > The OSCON proposals are reviewed and voted on by a committee of open > > source community members from a broad range of projects. The easiest > > way for us to review an education track is as individual proposal > > submissions, so the committee has a clear idea what each talk is > > about. Include a link to the page you put together in the > > "Additional Notes" field and put "Education" in the tags > > field. (We'll be reviewing the tags people submit to decide which > > should be promoted to tracks.) > > > > -- > > name: Karsten 'quaid' Wade, Sr. Community Gardener > > team: Red Hat Community Architecture > > uri: http://quaid.fedorapeople.org > > gpg: AD0E0C41 > > > > _______________________________________________ > > tos mailing list > > [email protected] > > http://teachingopensource.org/mailman/listinfo/tos > > > > > _______________________________________________ > tos mailing list > [email protected] > http://teachingopensource.org/mailman/listinfo/tos >
_______________________________________________ tos mailing list [email protected] http://teachingopensource.org/mailman/listinfo/tos
