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 Research note
As an open source community, we believe in open licensing of content so that other members of the community can leverage your work legally -- with attribution, of course. By joining the Public Lab site, you agree to release the content you post here under a Creative Commons Attribution Sharealike license, and the hardware designs you post under the CERN Open Hardware License 1.1 (full text). This has the added benefit that others must share their improvements in turn with you.
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.
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.
Post a proposal for comment
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:
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!
Reply to this comment...
Fixed a date - GSoC student proposals are due by April 3, not 30!
Reply to this comment...
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?
@inzamam , by removing ruby version line in Gemfile this problem can be solved.
Reply to this comment...
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
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.
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!
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.