SoC Team Sign-Up Wiki Page-O-Rama

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Here's a description of the various roles that need filling during SoC, what needs to be done, and a place for people to sign themselves up for it. Please feel free to sign yourself up for multiple roles, but please don't try and do all of them or you'll end up as insane as webchick. ;)

Let's rock this!

People we need ASAP
* Organization Administrators
* Mentor Recruiters
* Official Project Idea List Curators
* Project Idea Thinker Uppers

People we need before we submit a mentoring application (~Late Feb - Early March)
* Mentoring Application Writers
* Mentors
* Backup Mentors

People we need before student applications start coming in (~Late March - Mid-April)
* Welcome Wagon
* Student Application Vetters
* Student Application Rankers

People we need before community bonding period (~Mid-April - Late May)
* Community Bonding Time Team
* Planet SoC

People we need during Summer of Code starts (~Late May - Early September)
* Whip Crackers

People we need before SoC ends (Early September and beyond)
* Post-SoC Team

People we need ASAP

Organization Administrators

These people will be Google's primary point of contact for discussing anything with us regarding SoC administrative stuff (slot allocation, mentors/students not turning in surveys on time, student/mentor complaints, etc.). Day-to-day duties include relaying messages from Google as announcements to the rest of the mentoring team/students, being the initial point of contact in case any students/mentors need higher-level guidance, poking teams to make sure they're staying on track, and just generally keeping a good "bird's eye" picture of what's going on and making sure nothing's falling through the cracks.

Your Bible is http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors.

NOTE: If at all possible, I'd recommend that these people should NOT try and be mentors at the same time. It's perfectly fine to pull in mentors for discussion about what to do or whatever, but in general it's best if mentors can focus on mentoring and org admins can focus on administering since they're very different tasks.

  • Skills required: Good reading/communication skills, diplomacy and patience, access to e-mail/IRC. Familiarity/experience with past SoCs a plus, but there are enough people w/ SoC experience who you can ask for help if needed. Extra bonus if Leslie Hawthorn at Google knows who you are, as that makes it easier on their end for communication.
  • Number of volunteers required: 1 is required, 2-3 would be nice though as long as they can stay in communication.
  • Time required: Solid availability (5 hrs/week or so) from February -> September. A vacation here or there is fine if one of the other org admins can cover you, but if you're planning to be on a beach in Greece without access to e-mail for the entire month of June, this role is probably not a good fit for you.

Who's doing it:
[Post your usernames here!]
Alex UA
EmmaJane
Shannon Hinshaw
Fabiano Sant'Ana

Mentor Recruiters

We need a team to go and find mentors who:
a) Are either competent / advanced Drupal developers, OR have strong expertise in a specific area of interest (for example, usability, translations, etc.)
b) Have availability over the summer months (May - September), better still if it's more like from February-September.
c) Are kind, patient, and good at explaining things.
d) Extra bonus if they've mentored a successful student before

The more mentors, and the more diverse our mentor pool, the more interesting projects we can take on, and generally the more slots we're allocated.

  • Skills required: The ability to ask favours from Drupal developers without being punched ;), enthusiasm about SoC and the ability to "sell" it to people (extra bonus if you're a successful former mentor/student speaking on personal experience).
  • Number of volunteers required: 1-2. Want to make sure we don't spam our contributors.
  • Time required: If all goes well, then hopefully not more than 5-10 hrs/week for a couple of weeks until a nice list gets built up. After that, maybe 1-2 hrs/week during the application period to try and recruit more mentors for specific high-quality applications that come in.

Who's doing it:
[Post your usernames here!]
Alex UA
msapega
gusaus
Shannon Hinshaw
kleinmp
jtsnow
Jody Lynn
acouch
justinrandell
oweno

Official Project Idea List Curators

One of the things we're required to submit with our mentoring application is a list of "official" project ideas. Your job is to take the crazy, far-out list of project ideas that the Project Idea Thinker Uppers come up with and whittle it down to the ones that:

  • Have good, solid community support behind them.
  • Are scoped properly -- not too easy, not too hard.
  • Have someone who could reasonably act as a mentor on the project (preferably more than one)

See http://drupal.org/google-summer-of-code/2008/ideas-list for last year's list.

Last year we posted ideas to the SoC group, but this was a bit messy. Not sure if it's worth setting up an issue queue for this, or something more organized...

  • Skills required: A critical eye, and a love for consistency.
  • Number of volunteers required: 1-2. Don't want too many cooks in this kitchen.
  • Time required: Around ~.5 hour per project idea.

Who's doing it:
[Post your usernames here!]
Alex UA
kleinmp
jtsnow
Jody Lynn
acouch
justinrandell
oweno
heinzmilitar
sumitk

Project Idea Thinker Uppers

Is there something you always wished Drupal could do, or that you yourself wanted to do for Drupal, but could never find the time? Would it keep a student busy for 3 months over the summer and be valuable to other people in the Drupal community? Can you spec your idea out so that mere mortals can understand? If so, this is the job for you!

See http://drupal.org/google-summer-of-code/2008/ideas-list for last year's list. Wait on word from the Official Project List Curator on how to properly submit ideas.

  • Skills required: An itch, and the ability to communicate how you want it scratched.
  • Number of volunteers required: As many as possible!
  • Time required: ~2-3 hours per proposal

Who's doing it:
[Post your usernames (and a brief description of your idea) here!]

Ambrose - AS3Template/FlexTemplate: build a theme engine that outputs AS3 (ActionScript3) and/or Flex instead of HTML. Pages will display through a Flash screen which can optionally display is full screen mode. Carefully emulate the PHPTemplate theme engine so that existing PHPTemplate themes do not require modification. After 100% emulation is achieved then add at least two Flash dependent features (with Graceful Degradation of course) to demonstrate the many potential advantages of this theme engine.
Ambrose - PCD: "Precision Calendar Display" module providing easy configuration menus for EVERY element of a calendar display. Like how certain publication software lets you set-up multi-label size and positioning parameters but much more than just that.
gusaus - have a few ideas in the 'media' space referenced here; will work with Aaron and other mentors to properly spec out
Alex UA
kleinmp
jtsnow
Jody Lynn
acouch
justinrandell
oweno
heinzmilitar
sumitk
gordon - Allow comments to be attached to any type of object. Make changes to the comment module so that at the code level comments can be attached to any type of object. An example is to create a facebook type wall, user could be easily modified to allow comments to be posted directly to the user. Doing this will allow a minimal amount of code to attach comments to api objects http://drupal.org/node/101308. All the comment functionality comes along with it, with just a few lines of code.

Goal of this would be for inclusion in Durpal 7

People we need before we submit a mentoring application (~Late Feb - Early March)

Mentoring Application Writers

Once Google starts taking mentoring applications, we need a person or a couple of people to head up writing our application and submitting it to Google. Here is our Mentoring Application for 2008, for reference. Questions include stuff like why we want to participate in SoC, how we plan on handling AWOL students/mentors, who our mentor list is, etc. It would be very good to have answers to these questions nailed down far in advance. Feel free to borrow from the previous mentoring application for any overlapping items.

  • Skills required: English (good spelling/grammar; we want this to be professional), familiarity/experience with past SoCs (or finding someone with said experience who you can pump for information ;))
  • Number of volunteers required: Just one or two.
  • Time required: Maybe 5 hours at the end of Feb/Early March.

Who's doing it:
[Post your usernames here!]
Alex UA
msapega
acouch

Mentors

As a mentor, it's your job to be a resource person for your assigned student, helping them to scope out their project, making sure it's staying on track, and communicating with the organization administrators. On a day-to-day basis, you might be doing code reviews, helping the student to find resources that will help them over hurdles, or helping to shepherd a young contributor in the ways of the Drupal Ninjas.

Oh, another thing. You can't ALSO be a SoC student. You have to pick one or other other. Sorry. :(

Check out http://groups.drupal.org/node/10218 for some tips contributed by veteran SoC mentor ben_c!

  • Skills required: Competent/Advanced Drupal development skills (and/or expertise in a specific area such as usability, translations, etc.), kindness, patience, and being good at explaining things. (Extra bonus if you've mentored a successful student before!)
  • Number of volunteers required: As many as possible!
  • Time required: Solid availability from May to September (extra bonus if you're available March - September). Actual time requirement will vary dramatically by student/project. But plan on roughly ~10 hrs/week from the beginning to middle of SoC, ~5 hrs/week from the middle to the end.

Who's doing it:
dmitrig01
grndlvl
aaron
kleinmp
jtsnow
Jody Lynn (Drupal development skills, no specific area)
Shannon Lucas (usability, development)
Todd Nienkerk (theming, design, and development)
houndbee
sugree (development, translation)
acouch
justinrandell
oweno
Bojhan Somers(usability)
narres (Thomas Narres)(semantic clouds)
Roger Filomeno(development)
Howard Tyson(General development)
Greg Knaddison (greggles) (General development)
Owen Barton (grugnog) (General development)
CrookedNumber (General Development)
Jakob Petsovits (jpetso) (Version Control API / Project* / Drupal Pipes related, only available until mid July)
Fabiano Sant'Ana
rwohleb (Robert Wohleb) (general development, learning management systems, web-services)

[Post your usernames (and what you consider yourself qualified in) here!]

Backup Mentors

Fit the profile for a mentor, but don't have the availability? It would be great to have a large pool of backup mentors that can be called on in case one of the assigned mentors is unavailable (vacations, etc.), or if they hit a snag they're not sure how to solve. If this sounds like something you'd be interested in, sign up!

  • Skills required: See Mentors
  • Number of volunteers required: As many as possible!
  • Time required: Highly variable. Could be nothing, could be 10 hrs/week for one or two weeks, etc.

Who's doing it:
dmitrig01
heyrocker
grndlvl
aaron
kleinmp
deekayen
sumitk
[Post your usernames here! (along with qualifications/availability)]

People we need before student applications start coming in (~Late March - Mid-April)

Welcome Wagon

Enthusiastic about Drupal? Like helping new people find their way? Join the Welcome Wagon team! This team hangs out in #drupal, on the forums, on the SoC group, and on the SoC mailing list and helps guide students who look a little lost and direct them to the proper resources.

  • Skills required: Friendliness, knowledge of "who's who" in the community
  • Number of volunteers required: 3-5. Don't want to overwhelm people with too much enthusiasm. ;)
  • Time required: 5-10 hrs/week for the 2 weeks during the student application period (~mid-March - early April)

Who's doing it:
dmitrig01
sumitk
Howard Tyson
[Post your usernames here!]

Student Application Vetters

Last year, we required students to "vet" their applications publicly in the SoC group before they submitted them as applications. I think this was a pretty good idea, so we should probably do it again this year.

Your job here is to find faults (in a nice way) with student applications. If what they propose duplicates another project or is too vague, let them know, and give advice on how they might change it to fit in more with the community's needs.

  • Skills required: Kindness, patience, a critical eye
  • Number of volunteers required: As many as possible!
  • Time required: .5 hour per application

Who's doing it:
[Post your usernames here!]
heyrocker
Shannon Lucas
Todd Nienkerk
sugree
deekayen
sumitk

Student Application Rankers

Description.

  • Skills required:
  • Number of volunteers required:
  • Time required:

Who's doing it:
dmitrig01
heyrocker
Shannon Lucas
sugree
deekayen
sumitk
[Post your usernames here!]

People we need before community bonding period (~Mid-April - Late May)

Community Bonding Time Team

Description.

  • Skills required:
  • Number of volunteers required:
  • Time required:

Who's doing it:
[Post your usernames here!]

Planet SoC Team

Dedicated to maintaining the official SoC site.

  • Skills required:
  • Number of volunteers required:
  • Time required:

Who's doing it:
skiquel - (I'm known to blog and microblog my commits.:D)
sugree
[Post your usernames here!]

** Ideas we want to get started now **

  • Using public repositories so we can see your program. (GITHub, Google Code)
  • We're interested in creating a grand central station of all SoC project commits. Many sites (such as Drupal.org, Google Code and GIThub) offer RSS support for commits to versioning systems.

People we need during Summer of Code (~Late May - Early September)

Whip Crackers

Description.

  • Skills required:
  • Number of volunteers required:

  • Time required:

Who's doing it:
dmitrig01
msapega
[Post your usernames here!]

People we need before SoC ends (Early September)

Post-SoC Team

Description.

  • Skills required:
  • Number of volunteers required:
  • Time required:

Who's doing it:
[Post your usernames here!]

Comments

Table for DrupalCon?

Alex UA's picture

In regards to the mentor recruiting- would it be possible to get a table in the Job fair room for the GSoC? I don't know what the real estate is going to be like in there, but if it's not possible I'd be happy to donate most of our table for it...u

...I can reach out to Development seed if that makes sense.

--
Alex Urevick-Ackelsberg
ZivTech: Illuminating Technology

Alex Urevick-Ackelsberg
ZivTech: Illuminating Technology

Yes! Reaching out to Dev Seed is a great idea...

webchick's picture

I know they've accumulated a fair number of former GSoC students, so I bet they would be willing to figure out something. :)

Planet SoC

tonyn's picture

I feel as if I was one of the only ones who blogged about SoC. I think it would be impressive to see if SoC contributers for all projects and their coders signed up for Planet SoC. Furthermore, use a public versioning system like GIThub, google code, launchpad, or DO so they can provide an additional RSS information for their commits. Then we can track all these students, almost live, as their project builds.

I am excited and frankly, prepared to kick major ass. You can click on me like a starcraft sprite, and I'll make a sound effect, "I'm here, officer!"

YAY!! :D

webchick's picture

SO excited to find someone excited about PlanetSoC! :) That commit log-per-student stuff sounds awesome! I can't wait for you to take this ball and run with it.

Step 0 is probably securing hosting, since the place where PlanetSoC is currently hosted is only temporary. You should touch base with David Strauss, who mentioned in the other thread that he would be willing to host the site. Once you get that worked out, ping Robert Douglass and ask him to point the domain over there. Feel free to CC me on any of these e-mails so they know it's legit (or point them at this reply :)).

Another thing that we've traditionally done every year is basically wipe the database and start over, make all the students/mentors register (or re-register) new accounts, check them against Google's accepted list and manually approve them, etc. This is a lot of work, and I'm not sure if it's worth continuing to do this. But again, totally up to you on whatever you think is best.

If you want, I can give you a dump of last year's site (and possibly earlier years' sites, if I still have them), but I'm not sure how useful that would be. It sounds like you have tons of great ideas, so it might be more interesting to see what you came up with if you start from scratch. But let me know what would be easiest for you.

Also! Don't hesitate to ask around in #gsoc on irc.freenode.net for input/feedback from students/mentors on the site. Last year they were very keen to come up with suggestions. Although I never got around to filling it with anything, I started http://code.google.com/p/planetsoc/ last year as a public repository to store the website files in the hopes of attracting a few developers from other projects to hack on Drupal to add in a feature or two (you never know! :)). I've just added you as a project owner there. Feel free to use it or not.

Let me know what you need from me to get you started on your way, and I'll make it happen. :)

As for registration, it's

tonyn's picture

As for registration, it's looking that way, unless we can get a copy of the emails/names from Leslie and run a special script to create users/send users passwords. This likely would be a privacy issue. Perhaps Leslie can communicate with projects about the idea of using public repos (for organization purposes and the commit RSS feed) and Planet-SoC registration. It's important we get that going, we're going to essentially have a twitter-like section for commits, where people can drill down by project and user. WE ARE GOING TO DO THIS AND MAKE IT SUPER ULTRA COOL. We are freaking awesome.

I was thinking, we can keep the old archive of Planet SoC at 2006.planet-soc.com! looks Yep we already do that. Where is 2007? Can we find it and put it up? I like keeping things in order :D

Btw, if I can see the 2007 source for the config/modules/etc so I can get working on this thing locally. Just give me a db dump and the customizations. :D

Yeah, there are definitely privacy concerns...

webchick's picture

I begged and pleaded to Leslie for an export of names/e-mail addresses last year to help alleviate this, but no dice. And I fully understand. If suddenly someone other than Google.com suddenly got ahold of private information I had entered into Google.com, regardless of how noble the cause, I would be really freaking out. :P So, yep. It needs to remain opt-in. But! Leslie was very cool last year about mentioning Planet SoC as the "official" community site for SoC, so that was great.

But what I meant was more "do we care if someone other than SoC students / mentors uses the site." But my guess is that we do, especially given all the spam that the site accumulates... One idea is perhaps adding some sort of validation to the registration form that pings the external URL for whatever mentoring organization they choose and confirms that student's name shows up on the list? Not sure. All I know is doing this manually is really tedious and eats up a good chunk of my days around mid-April to mid-May. :P

Another idea to take some time-consumingness out of running Planet SoC is making this year the last year we wipe the database and put up a new site. Basically, make Planet SoC a site for any SoC alumni, but specially mark the content of students who are active during this year so their stuff can be featured in some way. This would make it a useful resource year-round and would eliminate a bunch of boot-strapping each year.

In terms of the 2007 site, I will go through my backups this weekend (and also ping Robert) and see what I can dig up.

Commit RSS

jpetso's picture

Using a contrib module whose name shall remain uncalled, it's also possible to import the commit histories of external repositories (not hosted on any of the mentioned ones where RSS is automatically provided) into a Drupal site and that provides the feeds by itself. That works well at least for CVS at the moment - SVN import is a bit slow currently, Git/Hg have not yet been ported to the new API, and bzr has not yet been written :P (...I think the situation can improve a lot until May in this regard.)

I guess there should also be other (probably more specialized) software creating RSS feeds out of any public repository, we should probably look out for that stuff. Forcing the students to code on either of the "big" sites is going to be difficult as that depends a lot on organization policies rather than student choice.

Quick research

jpetso's picture

For Mercurial, RSS support is built into hgweb (I couldn't find something more lightweight). For git, there's a neat small git2rss script, and for Bazaar as well. For SVN, as one would expect, there are already several solutions out there. For CVS, I'm convinced that Version Control API / CVS backend will do the job, and do it well. (Although I'm not sure if any organization except Drupal is still using CVS.)

Good finds by jpetso!

tonyn's picture

Good finds by jpetso!

Excited about GSOC 2009!

aaron's picture

Thanks for the great organizational wiki! Added my name to the Mentor list. I'd be glad to help out with any media projects, particularly if they involve the ongoing Media Sprint (but obviously, not limited to that).

Aaron Winborn
Drupal Multimedia (book, in October!)
AaronWinborn.com (blog)
Advomatic (work)

Aaron Winborn
Drupal Multimedia (my book, available now!)
AaronWinborn.com
Advomatic

Leverage the Drupal Dojo

gusaus's picture

The Drupal Dojo has a solid platform that allows you to share your desktop, show slides, collaborate, chat, talk and broadcast via webcam. Yesterdays 'Media Code Sprint Recap' gave us a chance to kick the tires a bit and it worked just as advertised.

There should be many ways to leverage the platform from planning/promotional sessions, discussing/demoing ideas, to live collaboration and mentoring. Possibly we can create a regular set of SoC sessions similar to what we've started with Media, and the Dojo redesign/Open learning portal. I'd be very interested in helping facilitate and produce.

Gus Austin
PepperAlley Productions

Gus Austin

I filled in the list a bit...

Alex UA's picture

A bunch of our staff signed up in places, but since I'll be assigning tasks to people at our firm (part of their job this summer will be helping out with the GSoC) in multiple areas, I signed them up in many places I thought appropriate.

Alex Urevick-Ackelsberg
ZivTech: Illuminating Technology

Alex Urevick-Ackelsberg
ZivTech: Illuminating Technology

Im back for round 2

rpfilomeno's picture

Hi guys!

A bit late joining in the group but I'm ready for round 2 as a mentor this year!

Im preparing some new ideas (still on the realm of social networking) as well as the continuation of last year's project - embed widgets (waves at Alex UA, AAron & JtSnow).

Lastly I have made a new year's resolution that I will need less whippin from webchick as mentor this year :D

Cheers.

sumitk is back too :) same as student

sumitk's picture

Hi all

I am a bit late in joining the group ;) I was hoping it will start late feb but it is already here
So I will be applying as a student for SoC-2009 but will be very happy to help you all in early preparations
very exited to do some big thing with drupal this SoC as I have spent a lot of time in past year doing all kind of crazy stuff

sumitk joining in

sumit kataria
www.sumitk.net

Join with Drupal

aroshthilanka's picture

Hi all,

I also join with you for Soc-2009 as a student and very have to help for the community specially in mobile web development integration.