RGSoC and GSoC
We're part of two different summer fellowship programs this year, Rails Girls Sum...
Public Lab is an open community which collaboratively develops accessible, open source, Do-It-Yourself technologies for investigating local environmental health and justice issues.
Public Lab chatroom
Reset your password
Read more: publiclab.org/n/13975
We're part of two different summer fellowship programs this year, Rails Girls Summer of Code (#RGSoC) and Google Summer of Code (#GSoC) -- both recruit software contributors to work on open source projects, and both provide a scholarship or stipend for a summer's work.
We've done GSoC for a few years now, and are really excited to be part of RGSoC this year. They write:
All people with non-binary gender identities or who identify as women (transgender or cisgender) are welcome to apply.
Learn more about the program and get involved! They are also seeking coaches to help teams out over the course of the summer -- learn more about coaching here.
So, we're asking students from both programs to start posting their proposals for comment, here. Read on!
RGSoC's application deadline is the 8th of March. GSoC's is April 3rd.
Once you've gotten a bit familiar with our project (see our welcome page here), the first step is to look over our ideas page, which you can find here. (Also see last year's, here!) Please feel free to ask questions in the comments below, or to join our Gitter channel at https://gitter.im/publiclab/soc
Also, take a look at our newcomer welcoming page, which will help you understand how we collaborate. And try tackling a first-timers-only issue, to get an idea of how to become a contributor!
Please ask questions! We're very friendly and we love welcoming new people into our community.
Once you've read through some of these ideas and become a bit more familiar with our projects, it's time to post a proposal of your own.
You don't need to have a complete or even concrete idea -- share your thoughts early and we'll help you refine your proposal, and help you choose something that's the right difficulty level as well as being something our project really needs.
We've created a template for you to post a proposal here. Click this button to begin:
Start drafting a proposal
Before or after you post your own draft, read through others' listed below. Your best comments and input may come from other applicants!
Hi, all -- just a note, after speaking with some potential RGSoC applicants (and I'm happy to get on Skype with folks if it's helpful, please feel free to ask) --
RGSoC's official application is directly to the RGSoC organization, through their website. But we would like all RGSoC applicants to post a proposal here as well, because:
@warren , I am interested in tagging Interface project for GSOC 2017. Can u please share the description.
And for GSoC students, we know you'll be submitting through the GSoC website, but please develop your proposals here, and then copy them over -- for the reasons listed above. Thank you!
Fixed a date - GSoC student proposals are due by April 3, not 30!
Hi, I'm Inzamam Iqbal. when i setting up for the first time, I get this error "Your Ruby version is 2.3.3, but your Gemfile specified 2.1.2" when bundle install. Shall I change the gem file version? can someone help me to resolve this?
Is this a question? Click here to post it to the Questions page.
Hi, Inzamam - thanks, have you tried installing RVM, to manage your gem versions? However you may also be able to change the Gemfile -- just don't commit those changes when pushing up new code!
RVM is no working on my PC. Can anyone help me ?
When i m going to use it, then it show "rvm command not found"
Now other issue created, I changed the rails version using rvm but when i m going to run the server then it again shows "Your Ruby version is 2.3.3, but your Gemfile specified 2.1.2"
Hi, you may need to open a new shell to get RVM to have all the right environment variables set.
OK @warren , thanks
Yeah , problem has been solved and now I m working on issue
Oh, super, good to hear!
@warren , i think we need to solve this ruby version problem, because it creates many problem for first timers.
@warren I submitted an issue for this problem and also I have solution for this , can I send a pull request for this problem
Yes, please do submit a pull request, thank you!
@warren What is the solution for windows users? there is no stable solution to use RVM in windows
@inzamam , by removing ruby version line in Gemfile this problem can be solved.
I'm using windows. i get the error while bundle install. can anyone please help me?
Compiling v8 for ia32
Using python 2.7.12
Using compiler: g++ (GCC version 4.7.2)
Beginning compilation. This will take some time.
Building v8 with env CXX=g++ LINK=g++ make ia32.release
extconf failed, exit code 1
Gem files will remain installed in
Results logged to
An error occurred while installing libv8 (22.214.171.124), and Bundler cannot
Hi, @ccpandhare, @siaw23, @mkashyap354, @Ashan, @Khamba, @mridulnagpal, @ryzokuken, @inzamam - Thanks for all your submissions; I'm going through them today and will leave some feedback; I appreciate your patience!
Great, thank you, all -
I do want to say, when it comes to scheduling your work, we ask students to submit new code in small chunks which are self-contained and tested, once or twice per week, for comment and (if ready) for merging into the master branch.
This is faster than many projects, and it means that we ask you to aggressively break up your work into small pieces, rather than work for weeks on a big project in one big chunk. This helps us provide good feedback, encourages modular code that's easy to read and is independently testable, and ensures you keep a rigorous schedule.
As you're revising your proposals, please think about how to break up big projects. Even one like upgrading the Rails version could be broken up if you think about what we could change in the codebase to make it compatible even before we do the switch. And if you're changing a major interface, consider developing it alongside the existing one by "hiding" the new version as an optional beta, until we're more sure that it's ready, and then "switching it to default" after, rather than breaking a working system before we're sure it's all ready. I'm happy to help you figure out how to break up your work.
You can read about how we do this here: https://opensource.googleblog.com/2016/12/google-summer-of-code-2016-wrap-up_21.html
Hi, @ccpandhare, @siaw23, @mkashyap354, @Ashan, @Khamba, @mridulnagpal, @ryzokuken, @inzamam, @bansal_sidharth2996, @ashwinvasudevan -- just a note to look at my last comment, and reply that you understand, or ask questions.
I hope to leave comments on everybody's work today but we'll see how far I get. Please also read through my comments on each others' proposals, leave your own, and see the kinds of things I ask people to provide -- it may be relevant input for your proposals as well. I'm often asking for how we can break projects up into smaller, testable parts that can be completed in less than a week, and for how you plan to write tests for parts of the code. If I don't get to commenting on your proposal, please bear those general comments in mind!
@ccpandhare, @siaw23, @mkashyap354, @Ashan, @Khamba, @mridulnagpal, @ryzokuken, @inzamam, @bansal_sidharth2996, @ashwinvasudevan --
Also please "like" or "star" this post so that you receive email notifications for it!
Thanks,@jwarren for the comment for general instructions
Hi, all -- @ccpandhare, @siaw23, @mkashyap354, @Ashan, @Khamba, @mridulnagpal, @ryzokuken, @inzamam, @bansal_sidharth2996, @ashwinvasudevan please be aware that you'll have to submit a final proposal also on the GSoC website -- it can be a copy-paste of the final version of your proposal from this page. I see some of you have done so, but not all -- thanks, and I appreciate your willingness to work on this site where we can discuss things, and do a second copy in the GSoC website for the formal application.
I'm not going to post the list just yet, as announcements may still be getting discovered :-)
I want to especially thank students who submitted proposals and contributed to our software already, but who we were not able to accept this year. Public Lab's Web Working Group is pretty small and we have only so much capacity to support students, but we hope you'll consider working with us again!
Finally, thanks and congratulations to the students who've been accepted this year.
You must be logged in to comment.