GSoC ’17 with Sugar Labs – 1

Hello people,

For the next three months, I will be in constant touch with you , sharing my experience as a Google Summer of Code’ 17 participant with Sugar Labs.

I can’t express how happy I was when I got to know I have been selected for GSoC’17 and also in Outreachy’17 as a GSoC participant( I was upgraded to GSoC in Outreachy according to their policy). Ecstasy due to happiness hit me so hard after seeing this :

sl

I got selected for the project “Timbre Widget for Music Blocks”  under the mentor-ship of two highly skilled people , Devin Ulibarri and Walter Bender. Sugar Labs community is very supportive and we all like to work as a team and help others . You can know more about Sugar Labs here.
I have been an active contributor to Music Blocks since December’16 and been in constant touch with the community. Right now, We are into the Community Bonding period . All the GSoC participants meet weekly and Walter Bender makes sure that nobody is encountering an problem regarding anything . Moreover, all the mentors as well as the students working on Music Blocks related projected have decided to meet twice a week to keep everyone updated with the progress.

Updates till now , i.e. 21st May ’17 :

  • Attended Regular weekly meetings on Monday with other GSoC participants.
  • Attended meetings for Music Blocks related projects twice a week.
  • Exploring Tone.js to increase the efficiency of Timbre Widget.
  • Worked on Distortion as well as Tremolo Effect.
  • Currently working on effects such as Chorus and phaser.
  • Made changes to existing “set synth” block to inculcate the functionality of AMSynth , FMSynth , etc.

Target to be achieved until the end of Community Bonding Period :

  • Get ready with Tone.js interface with all the effects as well as the synths.
  • Get a clear idea of the UI for the widget which will commence with the coding period.
  • Keep everyone updated with my progress via mail.
  • I will also be fixing some minor bugs during this period.

Looking forward to an awesome summers with Sugar Labs and my new found Love, Javascript !

Meet you all again in the next post soon !

Beginning with Open Source

Almost six months ago, I was introduced to the world of Open Source. It is intriguing yet intimidating at first if you jump into the large code bases of open source projects. As a newbie,it gets utterly confusing when you try to answer the question, “How shall  I begin?”  .My article is for all the newbies who want to contribute to open source in general .

Firstly, if you want to contribute to an organization’s product, it is very important that you are a user of that product because as a user you can figure out on what aspects the product can be improved  and then as a contributor, you can make the improvements.

Secondly, before you begin contributing, you need to go through the documentation of the project you want to contribute to. It will give you an overview of what the project maintainers expect from you and how you can contribute to the project. Moreover , you should have a good knowledge of the code stack the project is based upon and git.

Now, you should start with your first contribution. To begin , look for an issue or a bug (preferably easy bug for beginners) in the project’s bug/issue tracker which you find easy to solve.Many organizations either have a bug tracker such as Mozilla uses Bugzilla or they have their Issues section in the github repository.

One of the most important things in Open Source is to always interact with the project maintainers and the project’s community in general. It’s a vital part of Open Source, to communicate with people living in different parts of the world and gaining knowledge from awesome developers and talented people excelling in their fields who devote their time for the benefit of society. Once you get interested to work on project, it is quite important that you interact with the community. Generally, Internet Relay Chat (IRC) or Slack is preferred mode of communication . When you interact, your doubts are solved and new ideas emerge. Moreover, the mentors guide you how to approach a particular problem if you are stuck. You learn here and you help others too which is definitely the best part !

Once you successfully solve the bug , you need to create a Pull Request. Once you make  a Pull Request, assuming you have a good knowledge of Git and Github, it will be reviewed by the project maintainers. A key rule : Don’t get disappointed or feel dejected if your pull request is not merged at once, it opens up the gate to learning when you work through the suggestions provided by the mentors as they know how the pull request can be improved. Once your pull request is updated and merged,the momentary sense of achievement you get is a bliss !

The world of open source is intimidating at first as I said earlier,but it is quite exciting and opens up a  number of possibilities . You should not get scared but learn as many things by contributing and interacting with community 🙂

Good luck 🙂