Contribution, a word a I first heard in 2004. I was a student back then. I first contribution was to the KDE l10n project with help from Ankur Bangla project. More than anything else it was fun. All the people I first met were already doing many things, they used to do more work than talking, they still do a lot more work than many people I know.
Over the last 10 years the scenario of FOSS movement in India has changed. Contributors used to be the rock stars. The people just starting always wanted to become contributors. But a new word has taken the place, evangelist. Now everyone wants to become an evangelist. Most of the students I meet during conferences come to me and introduce themselves as evangelists of either Open Source or some other FOSS project, they do only talking and all of them want to change the world. But sadly, none of them seem to want to contribute back.
I can understand, contributing is difficult in many cases. One needs some amount of preparation and some commitment to contribute to any project. That takes time, cannot be done overnight.
To begin with, you have to spend more time in reading than anything else. Read more documentation, read more source code, read more meeting minutes of the project you want to contribute in. Remember one thing, one always reads more source code than writing. But if you are just starting, you can spend more time in writing code too.
Try to get involved in the discussions of the project. Join the IRC channel, stay there. In the beginning you may not understand all the conversations in the channel, but keep a note of the things people are discussing. You can read about them later, use a tiny and shiny site called google.com :)
I know new students have a tendency of trying to solve non-programming bugs. But as most of you are in Engineering background, you should focus in programming more than anything else.
At home, try to find the things you do in computer in steps and repeatedly/regularly. Try to write small programs which can do those tasks for you. One of my first proper project was a small GUI application using which I used to upload photos to flickr.com, via emails.
When working on some other big project, try to solve easy bugs at first. These days all projects somehow mark easy bugs in their bug tracker. In case you can not find one, ask in the IRC channel for help. Remember that IRC is asynchronous, you may not get the answer right away. If someone is helping you, you may want to ask their timezone.
I am not saying doing work in other parts of the project is less meaningful. I personally want you to write more code than anything else. That way we will get more developers from India.
If you look at the people who contribute with translations or documentation, you will find few common things. Like they all love their language, they love writing. As I said before even my first contributions were translations. But neither me or any anyone else that time used to do this for some goodies or ticket to any conference. We love our mother tongue and we love to use the computer in our language, period. If you are doing translations, then do it for the love of the language and fun. Please do not do this for some stickers or release parties.
Before you start calling yourself an evangelist, you should learn about that project. You will have to spend a lot of time to learn about the technology behind, you will have to learn why some decisions were taken. The evangelist is a person who cares and believes in the project and most importantly, knows the project intimately. [S]he knows the developers behind the project, constantly talk, blog and spread the news about the project. If you look at the established evangelists, you will find mostly veterans who spent a lot of time contributing to the project first. It is not about the age of the person, but more about the time [s]he spent in the project. Btw, if you want to call yourself a developer evangelist, first become a developer of that project. That means some real code, not some examples.
I always wanted to write more, but I did not. Last year I spent some time thinking why I don’t. One of the major reason used to be formatting but that issue was solved with my markdown based posts. Markdown is much easier and I can concentrate on the content rather than formatting. But I am still not writing enough.
I generally use vim to write my blog posts in a terminal but I do press Alt+Tab many times to move to the other windows (mostly browser) to read other random things. For me it is much easier to concentrate while writing code but not that easy to do while writing a blog post. That is why it generally takes a lot more time to write a blog post. While discussing this with my friend over phone a simple term came up self discipline or the lack of it in my case. As I wrote before, I can do this well for programming or reading but not that good when writing things on a computer.
What I am planning (with a great hope) is to move out of X for writing the blog posts. I will have only one terminal and nothing else at that time. This is still an idea and I have to do that for some time before judging if it is a good idea or not. May be it will work, may be it will not.
Right now I am writing this post in Evernote in my super old iPad. Applications in any such device is nice in that way, by default you can run only one app at one time. This will help you to concentrate in an easier way. Of course there are apps like ia writer which focuses on distraction free writing (or sublime text in distraction free mode in desktop), one can try those too. I am yet to spend enough time in writing to come to a conclusion.
I would prefer to use my mechanical keyboards any given day. May be that is why I am superbly excited about the Hemingwrite device. Less than 36 hours and it exceeded the kickstarter goal. I can see why so many people are so excited about this device. Though I have to wait till next September to get one.
Please share your ideas on the same in the comments. I really want to know how people managed to solved this issue.
Two weeks back I did an one day workshop in Bethune college, Kolkata. Had around 20 students as participants. The goal of this work was to introduce Fedora as an alternative OS for the students.
The students were from the following departments.
So you can easily understand that these are not our topical engineering college students. They use computers to do some particular tasks other than programming. We also made a list of those tasks (major ones)
At the starting of the workshop, we just looked into a Gnome3 desktop and students kept clicking randomly to explore the system. We saw Firefox as the default browser, which most of them were already knew. Evince as PDF reader, and then just went through LibreOffice suite for documents and standard presentations. We also learned “How to learn touch typing” using gtypist package. The classroom was full with excitement, everyone was trying to type better than their friends.
Next we learned the basics of reStructuredText, and how to create presentations from them using rst2s5. The studentsliked this part of the workshop as everyone were doing things in their laptop and the results were visible within a second. Instant feedback is important to keep the new people going and when the feedback is coming from the computer they simply liked it. I already told them the biggest problem for most people is typing mistake(s). It was again proved to be right during this workshop :)
After the lunch we resumed with sphinx. Using sphinx-quickstart we started a new project, and started writing our first book/report. The PDF output using pdflatex command showed them how easy it is to create a professional looking document at home without any paid software. I also demoed vim as editor. We then moved into l10n and everyone logged into their system using bn_IN as the system language. The students were quick to find few translation issues in couple of the major applications. I will write about them in a different post. We ended the workshop while chatting about different aspects of FOSS and how they all can contribute to make their own life better. I will be going back to Bethune again to help them with installation and any other issues.
Setting up the laptops were the easier part of this workshop, which generally takes a lot more time. We took few seconds for each computer. How? Liveusb images. Using livecd-creator I created an image which had all the required packages for our workshop. So we never had to configure anything, things just worked out of the box, no missing packages.
I will be doing similar kind of workshops in few of the other biggest colleges in Kolkata, where the students will be from different streams than engineering. I also thank Assistant Professor Shuchismita Mitra for arranging this workshop.
Last week roshi mailed the new release criteria to the test list. Not much reply in that thread. He will bring this point again to the QA meeting on next Monday (2014-11-24). We also need more hands for testing the images. If you want to help please ping us in the #fedora-cloud channel on freenode.
jzb will publish the magazine story on Fedora Cloud. It is ready and will be pushed very soon.
During the openfloor, dustymabe informed that he will be going to the Digital Ocean office and get some more information on how easily we can have released Fedora Cloud images there.
I have updated my worknotes so that anyone can run my small test suite. You will find more details in this link.
I will be working as FESCO liaison from the Fedora Cloud SIG, my first duty is to update the Governance page with the current team members.
On a side note, the third meeting of the CentOS Cloud SIG will happen at around 3pm today, meet us at #centos-devel. The log from the last meeting is already available.
I am keeping all my worknotes in a git repo and the same is getting rendered in readthedocs. I will try to explain the processes and tools involved in the Fedora Cloud SIG. The notes started with imagefactory project as we use the same to build the cloud base images in koji.
I am also having a faq section where I am putting up all the random questions coming in my mind.
If you have any questions related to the notes, feel free to ask me on IRC or you can create an issue in github, as usual patches are most welcome :D