meeting 1500 UTC 14 April
by Karsten Wade
Sorry for the late reminder. :)
#fedora-meeting @1500 UTC, see you then.
I didn't create an agenda for this week but it's pretty straight-up --
how are we doing with the FSC2010, what's next?
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years
Alternative schedule(s)
by Ionuț Arțăriși
Hello list,
I'm a final year student in Romania and I've successfully completed a
GSOC on the Fedora Project last year. I'd love to participate in this
year's FSC and have been working on a proposal since before the sad news
about Fedora and GSOC was announced.
There's a bit of an overlap between the FSC/GSOC schedule and the
schedule of Romanian colleges. In Romania, the summer holiday generally
starts in July, with the new school year starting in October. I know
quite a few students who couldn't participate in GSOC in the last years
because of exams. Even so, judging by GSOC statistics, Romania has one
college rated as 4th for number of students last year and another rated
10th for the number of students in 2005-2009 [1].
So I'm wondering if we can tweak FSC's schedule a bit in order to
accommodate more people (and make it less stressful for myself :) ).
I've seen some discussion about an year-round summer coding, but I'm
wondering if we can do anything for this year as well.
Since the ideas/proposal submitting time has already started and this
period is free from exams, everyone could submit their proposals now.
They would get notified of accepted/rejected status by the end of the
month, but start working at different times. Couldn't we have two
different periods: the one we have now, and a delayed one (1 July - 15
September -ish)?
Or if that fails, I know there was talk about bigger and smaller ideas.
Could we have half-proposals, with work starting at midterm evaluation
date and only half the money? I know the RubySOC guys have "Half Project
Sponsors"[2] which probably makes it easier to get more sponsors, though
they probably don't also have half-work proposals.
I'm probably seeing this over-simplified (from the student's POV), but
what are the affected/disadvantaged parties by having two summer coding
periods? Can't we work with them to make this a more flexible SOC? We
could also compete better with other SOCs this way :)
Thanks,
Ionuț
[1]
http://google-opensource.blogspot.com/2009/09/tasty-new-google-summer-of-...
[2] http://rubysoc.org/sponsors
14 years
How to help those who don't make it
by Dhushyanth R
Hi all,
Fedora-Summer-Coding will be an excellent opportunity for students to
spend their summer in a fruitful way. The $Funding$ apart, since many
of the students in their first year or second year here _don't_ have
to do intern for course credit, it will be an excellent opportunity to
rope them into the community.
In this regard, I expect many of the relatively "inexperienced"
students may get rejected.
So can there be a mechanism where we say "Ok. Your proposal didn't get
selected(maybe because of lack of clarity of idea, availability of a
better proposal for the same idea, etc), but you still get to work on
it- or this other alternative" say ask him to package stuff, patch
some non-trivial bugs,etc ; albeit for a T-Shirt or Certificate or
$CheapAlternative.
This "code for cotton/certificate" will ensure that students who are
not selected don't feel that they have to be a genius to get selected,
and that they can help in their own way. Otherwise on the face of
rejection students may often shrink back further in their shell and
fail to open up to the community. Basically we "bait" them with SOC
and if by chance they fall through we route them through our normal
"Join" process. The difference being this time "Join"ing will be
closely monitored, planned and will be coding oriented.
The load on mentors will be the deciding factor whether this can
actually be implemented. Maybe we can ask the "normal" fedora mentors
to help?
Regards
dash123
14 years
Students - You are invited to submit proposals for Fedora Summer Coding 2010
by Karsten Wade
Start here –
https://fedoraproject.org/wiki/Summer_Coding_2010#You_are_a_student
But here is some more, in case you want to read it. (From
http://iquaid.org/2010/04/08/students-you-are-invited-to-submit-proposals...)
We are rapidly constructing this summer coding program. We know what
we are doing, but because of timing, we are building the
infrastructure, process, and requirements as we go. It’s like moving
in to a house while the scaffolding is still outside. The Fedora
Project makes it easy to do stuff like this, since the plumbing and
stuff are already in place. (Enough of that metaphor …)
Since mentors have another week, until 14 April, to finish the ideas
page:
http://fedoraproject.org/wiki/Summer_Coding_2010_ideas
The page is growing and changing until then. Check back often, put a
watch on the page, and immediately begin communicating with the
mentors of any ideas that you are interested in. The best place to
talk with mentors is the discussion list:
http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss
If you can’t participate this year, such as the timing being off for
your summer plans or you want more certainty, good luck to you for
this summer. Check back in; we intend to do this again (and again),
and it is going be better after all this learning we’re doing:
http://iquaid.org/2009/02/28/failure-as-the-secret-of-success/
If you celebrate summer at a different time of the year, such as if
you are in the stunningly huge population of people in the Southern
Hemisphere, do you think we should keep rolling this program to do a
summer-for-the-south version? Stay tuned, or help organize it:
https://fedoraproject.org/wiki/Summer_Coding_SIG#How_can_you_help.3F
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years
#fedora-meeting 1500 UTC Wed. 07 April 2010
by Karsten Wade
All:
We'll have our meeting at 1500 UTC 07 April in #fedora-meeting.
(http://webchat.freenode.net/?channels=fedora-meeting)
https://fedoraproject.org/wiki/Summer_Coding_SIG#Agenda
Summary: we'll review, note for fixing, and remove draft marks on the
various pages involved in the main messaging page
https://fedoraproject.org/wiki/Summer_Coding_2010.
Wed. 2010-04-07
* Goal of measuring all content as defined in Summer Coding 2010
plan:
o Does it make sense for the target audience?
o Is it complete?
o Is it too much?
o What needs fixing?
+ Make actions.
* Review of messaging content - Go/No Go for:
o Category:Summer Coding 2010 -- all pages
+ Summer Coding 2010 plan
+ Category:Summer Coding 2010 ideas
+ How to create an idea page for Summer Coding
+ Summer Coding 2010 schedule
+ Summer Coding 2010 student application
+ Summer Coding 2010 timeline
+ Communication for Summer Coding 2010
o List all actions that can be completed immediately
following the meeting.
o Note other actions to input in Trac for project
management.
o Directly after meeting, finish all changes to program
pages.
o Launch messaging for all audiences via various methods
described in Summer Coding 2010 plan how sections.
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years, 1 month
comparison/analysis of RubySOC and JSOP
by Karsten Wade
(dash123 posted an analysis on these two projects, and I wanted to make
sure it got in to the discussion, being useful stuff.)
Since most of us are familiar with how GSOC works, I thought it better
to compare rubysoc and JSOP in terms of their differences with GSOC.
About RubySOC:
The main highlight of their is that they have an extremely concise and
well-structured site. Everything is neatly divided into students,
Mentors , Sponsors, Community.
1. Mass communication/marketing by using Twitter, Reddit,
digg.(twitter: @rubysoc)
2.For mentoring orgs, the site says: "The number of mentoring
organizations depends on the number of sponsors the program receives;
all funding will go towards adding more mentors and students to the
program."
3. Projects are evaluated by each student's mentor, and then reviewed
by the larger mentor pool.(similar to GSOC)
4. They have given a larger time window for student applications(18
days- 5th Apr to 23rd). This is in contrast to GSOC's 11 days. The
mentor application period has closed already(on 2nd April) so no idea
on how long that lasted.
#
5. Since rubysoc is similar to GSOC's umbrella organisation structure,
they have already given out what the Application questions will
be. This is beneficial as students now know what areas of their
application they have to focus on.
6. The ideas list right now links to only JRuby and Rails wiki(both of
which have long list of ideas).
7. Under their "community" heading they have said that students will
get to receive free admission to RubyConf and a small speaking slot to
showcase their work.
8. Funding source: funding sources include web-service providers(like
Engine Yard), publishers(O'Reilley), IDE(like Aptana). In fact they
are asking for the "common man" to pool in. They then have a nice
"Sponsors" page which lists out all their sponsors(including the
"common man")
We could do something similar by going after sponsors/users who use
JBoss Middleware, RHEL, etc in a big way.
About JSOP(Joomla Student outreach Program):
1. Their main page is at
http://docs.joomla.org/Joomla!_Student_Outreach_Program_Project_Ideas
2. They want to students to take part in larger projects as teams of
students and mentors. This is at variance with GSOC where most of the
students work on a small parts of a big project or on new
projects. Communication across different students is rarely extensive
in GSOC's case.
The idea which we can get from this is to have brownie points for
students applying as teams(or we team them up as part of the
process). This way we ensure cooperation, sharing of code, ideas,
etc. Students get to learn the core values of open source projects
this way.
3. They also talk about Small task projects which can be worked on by
individuals but right now there are no ideas listed under that
heading. So I'm assuming they aren't interested much in "individual"
projects.
4. They don't talk about funding at all. The site says: "we will
figure out some fun rewards, like awarding t-shirts or other Joomla!
stuff. Also, we will issue official certificates to students who
successfully contribute to either program."
5. They haven't announced any dates yet. Also there have been no
discussion on their official discussion group(
http://groups.google.com/group/joomla-student-outreach-program ) since
31st March. The wiki was last edited(by a mentor) on 31st April so
maybe there has been a lull in their enthusiasm.
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years, 1 month
schedule
by Karsten Wade
Mel and I did some work on our schedule:
https://fedoraproject.org/wiki/Summer_Coding_2010_timeline
(The actual page is
https://fedoraproject.org/wiki/Summer_Coding_2010_schedule so it can
be transcluded where needed.)
We could divide the items by audience, or not. We want to do that for
the individual audiences on the [[Summer Coding 2010]] page. Maybe as
part of a step-by-step?
Patrick - the order of audiences on [[Summer Coding 2010]] is the
order of importance for completing step-by-step instructions. If you
get to working on that, please start with "You are a student" and work
your way down. I'll put in a dummy example of how I think we want to
transclude the page.
We should finalize the schedule in tomorrow's meeting. I already
started telling people about the deadline for ideas of this Friday.
Spread the word.
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
14 years, 1 month