Fedora Activity Day(FAD) 2014, Pune

Last Saturday i.e. on 23rd August, 2014, i had participated in FAD

                    >>> https://fedoraproject.org/wiki/FAD_Pune_Aug_2014

at Red Hat, Pune (India) office. The day started with testing of Fedora 21 workstation alpha iso image (it contains GNOME as a default desktop). I had installed F21 alpha image in my vm. During installation, while adding a user step, my screen started flickering. Here is the attached video of screen flickering in a known bug in anaconda (Thanks to siddhesh for pointing out that bug.). I have learnt to use recordmydesktop app from Amit Shah.

Later on i also got another bug, in Date and Time screen, when we on or off the Network Time button, the Date and Time Button or applets were disabled always. Here is the bug link for Date and time buttons are disabled while doing on and off the network time.

After the lunch, i have learned about creating virtual machine snapshot using virsh snapshot. Here is the list of commands to create VM snapshot . Creating a snapshot of virtual machine saves our development work and if anythings went wrong while testing and deployment, we can revert back to previous snapshot. virt-builder is a great tool for creating virtual machines.

pjp taught us how to configure and test the local DNSSEC resolver configuration on fedora 21 and also learned how to review packags and give karma to that and earn badges using Bodhi web interface or by fedora_easy_karma tool. I have reviewed the package and gave karma to the package python-gevent through a FAS2 login.

Finally, it ended and i learned lots of things. Hope to see another FAD soon :).

The day when I hunted down 14 bugs myself on #openstack-Doc Bug’s Day.

The Documentation of any project is the best place to learn about their components especially its working and hacking on it.On 20th Dec, 2013 The OpenStack Documentation team had organized the OpenStack-Doc Bug’s Day. The OpenStack Documenatation consists of OpenStack Manuals and API-site Bugs (more than 450 in number). The day started as usual just like any other day. But the motive was different today. We had to achieve a Goal. The goal was to hunt down 100 bugs at least. I had a target for myself to solve 10 bugs in 24 hours. My first bug hunting started at 11:00 A:M (IST). Solving a bug is not so easy, it requires information gathering and searching for appropriate contents to fix the bug and finally test and verify on the system while submitting. The bug squashing already had started by Anne Gentle, Tom Fifield, Lana, Matt and Nermina. As the day passed, with every successful hunting process the bug numbers went on decreasing. Due to this tough bug hunting, I have learnt a lot of things related to Installation and Configuration of OVS Plug in, neutron, Keystone and Nova. I have also learnt how to write documentation from reviews and updates in the particular components and plug ins configuration like KVS. I have also learnt how to display questions and answers in doc book from Anne. After lunch, Andreas started reviewing the patch. By the evening I have had solved 7 bugs and was still in search to solve more. After that I started reviewing the reviews submitted by others. I also got the help of Tim Bell, Scott Radvan, Deepti Navale, Brucer, Diane Fleming during bug solving. Just before the first light of Dec 21, I was able to solve 14 bugs out of which 9 of them are now merged and 5 are still in progress. During that day, I also made a small contribution to keystone, Thanks to Tom Fifield and Morgan Fainberg for this. And Finally, the toll was 100 squashed Bugs. The day was totally awesome for me and we achieved the Goal. Congratulations to all of them for making this happen. It was a great day for me while hunting bugs in a virtual battle through learning and getting lots of strategic approaches from great OpenStack Doc leaders (Tom, Anne and Andreas). After this day, now I have 50 commits for Icehouse release in OpenStack under my name.
My OpenStack Review-board and Stackalytics report is here. Bug’s Day status is here.

Thanks for reading.

One Month! 12 commits and 82 reviews in OpenStack.

One month earlier, i had submitted my first patch to OpenStack through OpenStack-Manuals with the help of Tom and by the encouragement of Kushal Das and Sankarshan to dive deep into the system and learn more about OpenStack. After first patch, Anne and Ajaeger taught me to search bugs and assign it to myself and submit the patches. Many times i got -1 on my reviews but Lana Nermina, Gpocentek, Slong and Sarob encouraged me to go ahead and fix the Review and get +1 on the review and get it merged. After submission of three patches, Anne has taught me to “How to Review the Openstack-Manuals Review?”. From there my new journey to OpenStack begins. While solving bugs and submitting review, i got a chance to interact with lots of OpenStack core contributors (Steve Baker, Mrunge, Emilien Macchi, Koolhead17, Daine Fleming, Steve gordon) guiding and teaching me lots of things related to different component starting from Heat, Swift, Horizon, Nova etc. During this period, I have made 12 Commits and 82 reviews in OpenStack-Manuals till today i.e.20th Nov, 2013. The reviews and commits are found on Stackalytics. It is very less. I have to work hard and learn more in order to contribute more. Thank you all the peoples who helped me to reach that stage.

RDO-havana on Fedora 19.

This week, i was trying to solve a bug in openstack-manuals related to heat component of Openstack. It propels me to try heat on RDO. RDO is an OpenStack distribution for deployment on RHEL and related linux distro. For that, I have created a VM of Fedora 19 with 2GB RAM, 2 CPUs and 50GB hard disk space. Below are the following steps that i have documented during my successful installation of RDO-Havana on Fedora 19.

  • Set the Hostname to openstack : – $ sudo hostname openstack
  • Install the latest RDO Havana Repo: – $ sudo yum install -y http://rdo.fedorapeople.org/openstack-havana/rdo-release-havana.rpm
  • Do a system Update on Fedora 19: – $ sudo yum -y update
  • Install the packstack installer: – $ sudo yum install -y openstack-packstack
  • For a single node OpenStack deployment of RDO using packstack: – $ packstack –allinone 

It will install all the components of Openstack in 15 Minutes and generates an answer file packstack –answer-file packstack-answers-20131114-143042.txt (it is different for others.) in that current directory. During installation i have got two errors, which is finally resolved.

  • ERROR : Error appeared during Puppet run:
    Error: /usr/sbin/tuned-adm profile virtual-host returned 2 instead of one of [0]  

The Following error is solved by running the following command and again running the answer file.

  1. $ sudo systemctl restart tuned
  2. Re-run the answer file: – $ packstack –answer-file packstack-answers-20131114-143042.txt
  • ERROR : Error appeared during Puppet run:
    Error: Could not start Service[openvswitch]: Execution of ‘/sbin/service openvswitch start’ returned 1:  

The reason behind this error is: Openvswitch service is dead. To fix it, run the following command and re-run the answer file.

  1. $ sudo mkdir /var/lock/subsys
  2. Re-run the answer file: – $ packstack –answer-file packstack-answers-20131114-143042.txt

And finally, openstack is installed successfully after fixing these errors. After that i checked the status of different openstack component using the command. $ openstack-status and found that openstack-dashboard is showing 500 and my dashbaord in the browser is showing “Something went wrong!. An unexpected error has occured.”. To fix this problem, i have runned the following commands:

  • Edit /etc/openstack-dashboard/local_settings and add one of the following in the end: – ALLOWED_HOSTS = [‘*’]
  • # systemctl disable firewalld
  • # systemctl enable iptables
  • # systemctl restart iptables
  • # service httpd restart

Finally i am logged in to the openstack-dashboard by using username and password. Here the OpenStack fun begins. Thanks to Praveenkumar, KushalDas, Mrunge, Sankarshan, xqueralt, red_trela and SteveBaker for helping me in successful installation.



My first patch to Openstack

Last Week, i was going through the OpenStack Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora  – havana. In the Chaptor 2 “Basic Operating System Configration“, under “Messaging Server” topic , I found that the command used for disabling Qpid Authentication in /etc/qpidd.conf file “# echo “auth=no” >> /etc/qpidd.conf“. But while running that command, it is appending an newline “auth=no” in the fie without modifying the value of auth which is required to be done. I found it wrong. So, i have contacted Tom Fifield on #openstack-doc channel on Freenode server. It was an error in the openstack-manuals. With the help of Tom, i have filed a bug #1239977 on launchpad and got assigned it to myself.
Tom, Andreas Jaeger, Summer Long and Sean Roberts helped me to setting the environment for fixing that bug by following the steps on #howtocontribute. With in 2 hour of work, i have prepared my patch and sent it for review. I have just added following lines “Disable Qpid authentication by editing /etc/qpidd.conf file and changing the auth option to no, “auth=no” ” and my patch is ready. Here is my patch #51810. For acceptance of the patch, it requires the approval of two main core developers. Thanks to Anne Gentle, Tom Fifield and Diane Fleming for approving my patch. The changes appears on openstack-manual. It was an awesome experience.

Recent developments in LTMT

LTMT stands for Localization Team Management Tool which will be an extension of present KDE Localization Website.

It consists of two parts:

  1. Integration of KDE Localization website with KDE Identity for unique authentication system for all KDE localizers as well as for newcomers.
  2. A Booking system for all translators in order to ask a file / give up a file for translation.

As a part of my gsoc project, Below is the updates:

  • The kde identity authentication side is faked with solena functions to return registered users.
  • A new registered user under KDE identity can join any language team by clicking join Team button.
  • If the user has already placed his request for team joining, if his request is not approved, he will greeted with previous request message.
  • The join team button will be visible to users who are not the member of the language.
  • The Site administrator can view all the language team join request as a translate for for all languages.
  • coordinator of one language or more than one languages can view all the language team join request as a translate for all the respective associated language.
  • Site Admin/coordinator can approve or deny user’s language team join request.
  • on denial, the user can again view join team button.

The Drafted documentation for setting up the http:l10n.kde.org locally is here.The project code is here.

Currently, i am working on Booking System for all translators. Thanks to tosky who helped me in each and every point of difficulties.


Localization Hackathon @wfs-india 20th May, 2013

WFS-india is a volunteered organization created by some intelligent and innovative minds like: Satabdi Das (A OPW- Gnome intern and FOSS enthusiast) few months ago. The main motto of this organization is to create awareness among women towards free and open source software in India  For this , they have started conducting meetings on #wfs-india channel on freenode server in order to plan an event for increasing participation of women in free and open source software movement. In a short span of time, finally they decided to organize an event named “Localization Hackathon” on the eve of cultural freedom day on 20th may, 2013 from 08:00 p:m to 09:30 p:m at wfs-india channel on freenode server.

The whole event is supported by Mozilla, Fedora and Videolan (The creater of VLC Media Player). This event provides two reasons to join it and hack while learning. First is “Want to see your name the next time anybody installs fedora, Mozilla and VLC Media Player?” and the second one is “Want to add some special skills to your resume?”. The whole session of Localization Hackathon is started by me and finally backened by Biraj karmakar and Runa Bhattacharjee. We have got seven participants across the globe <holingpoon, erry, sunu, Anupam, shweta, anexasajoop, sri_c>. The more details about the participants are given below in the chat list. The guest persons who are helping backend are Amani_glugcal, kaustavdm, Priyankanag. The whole event is coordinated by Satabdi Das.

The hackathon starts with a formal introduction of all the participants followed by a simple question “Why do you want to contribute to foss?”. The above question extends and arouse a new question, “if i donot know programming, how will i contribute?”. After that we explained the definition of localization followed by internationalization and related mother tongue with software localization. From there, we have taken the help of Transifex and mozilla pootle server to get started with localization of mozilla, Fedora and vlc media player. All the participants have created their account on pootle server and transifex also. Erry found his language 100% completed in mozilla so she switched to VLC and there she found that greek is not available for VLC, so he requested for the creation of new language. Sri_c has successfully joined on kannada language team on mozilla pootle server and for VLC on transifex. sunu has started for oriya localization, so he contacted the videolan language co-ordinator in order to get approved and he joined oriya localization team on transifex.Holingpoon is successfully registered on mozilla pootle server. But during loging she is getting 500 internal server error from mozilla pootle server. I request mozilla to please sort out this problem. Each one has got their tool to translate. from that people actually entered into the field from where they start translating. Biraj is helping the Bangla people to get into the translation.From there people understand what they have to do for software localization. Due to very short span of time and after facing lots of problem, this hackathon has ended by 09:30 p:m. Due to that we have chosen to take input from Google transliterate but found that i doesnot support some scripts of various languages like: oriya.
The output of the hackathon are as follows:

  1. in a short span of time, people get charged and comes forward to support wfs-india.
  2. People actually learnt what localization is and how to get started in any language by using transifex and pootle server.
  3.  On founding any problem during localization, they can contact to language co-rodinator through mailing lists.
  4. faces some problems during hackathon on pootle server needs to short out.
  5. more things on localization will be introduced in the upcoming event.

Following features needs to be added in the pootle server:

  1.  Test the working of mozilla locamotion on al different available browsers.
  2. Show language code against the language name.
  3. creation of help desk to solve problem quickly if any problem occurred during hackathon.
  4. Sometimes the pootle translation page does not responds- it needs to be fixed.
  5. porting all translations of mozilla projects to locamotion for easy translation.

And lastly , the event was successful to some extent as we have expected. I would like to thanks all people like: Sankarshan Mukhopadhyay and Rajesh Ranjan who have directly or indirectly supported us in successful completion of the hackathon. A special thanks to Mozilla Locamotion and Transifex Developers.

Some important links:

Localization Hackathon: Get started

Steps to get started:
  • Check your mail box, you will receive a confirmation mail.
  • Click on confirmation link to activate your account.
  • Next task is to choose a project and start translating.
 For people who want to translate VLC Media Player
  • Click on your Language name like: Hindi or Bengali.
  • Click on Join Team.
  • Wait for getting approved as a translator.
  • Check notification for seeing you have been approved as a translator.
  • After Approval select any file from Language Resource click on that.
  • Like :vlc daily updating pot (to git2.0 state).
  • Now click on “Translate now” option.
  • And start translating.
  • Please follow the instructions taught during hackathon.
For people who want to translate Fedora
  • Click on your Language name like: Hindi.
  • Click on Join Team.
  • Wait for getting approved as a translator.
  • Check notification for seeing you have been approved as a translator.
  • After Approval select any file from Language Resource click on that.
  • Like: any untranslated file.
  • Now click on “Translate now” option. 
  • And start translating.
  • Please follow the instructions taught during hackathon.
For people who want to translate Mozilla
  • And register yourself.
  • Check your inbox for confirmation mail and click on confirmation link to activate your account.
  • Log in.
  • Go to accounts.
  • Click on settings.
  • From language select Hindi or Bengali.
  • Select all projects.
  • Now click on save.
  • Return back to dashboard.
  • All your selected project(s) will appear there.
  • Click on any project like: Webparts
  • Click on untranslated and start translating.
  • Enjoy it.
Suppose your language does not exist on Transifex.
  • Click on request language.
  • Select your language list from the drop down.
  • Click on Request Team.
  • Wait for the approval from project maintainer in order to get your language added.
  • After that, all the steps for translation are similar.
Suppose your language does not exist on Mozilla
 Configure your system for adding a new language for typing:
  • go to region and language settings
  • Click on input sources
  • Click on +
  • choose an input source
  • click on Add

Enjoy typing.

Mozmentoring: let’s train them!

The progress, growth and fame of a community comes from the training and a huge hard work that we do in order to train our volunteers. After the success of Durgapur-mozconnect, i Biraj, and Umesh decided to draft a plan through which we can train mozilla newbies as well as track to their whole process and process of contribution through monthly meeting. For doing the same, our first community monthly meetup named “mozmentoring” was organized on 17th April, 2013 at CSE/IT seminar hall at Dr.B.C.Roy Engineering College, Durgapur from 01:00 p:m to 04:00 p:m.

Before coming to the actual meeting, last night we all old and existing mozilla contributors meet on irc at about 01:00 a;m on #india channel of irc.mozilla.org server done a meeting. The final conclusion came out as a plan and that we have executed them,are as follows. Firstly, we told the newbies, what are the areas of contribution that mozilla provides by explaining software development life cycle, later on we move to FOSS. After that we enquired about their interest and the whole crowd into three groups. First group is mozilla design team who task to form two strong team for firefoxos video contest 2013 that is laid by umesh agarwal followed by santanu and avinash.

The second group is Mozilla codebase who task is to teach the half of them web maker and rest of them how to get their first solved by telling them how old volunteer get their first bug and is get solved by mozilla mentors. We told that they can contribute to different parts of mozilla codebase depending on their programming language interest. This was laid by Souradeep de, Aproorv Ashutosh, Zubin and Subho. The next and last group is sumo and localization laid by Amit Kumar Thakur and Biraj Karmakar. They taught through translation and sumo hindi/bengali localization. At the end of the whole thing, i have taught them how to use IRC and show them practically how to communicate on irc. Thanks to Gaurav and sayan for teaching them about JavaScript during meeting.

This slideshow requires JavaScript.

In night we have called newbies on irc. There i, umesh, biraj and amit taught live how to do translation by sorting and solving their problem. Today, 0n 18th April, 2013 i am going to give a practical training on how to do localization through effective use of style guide and fuel terminologies through online and offline editors.

Umesh agarwal created a video on FirefoxFlicks to teach and give a preview on how to make videos for firefoxos video contest 2013.

Lastly each group have given tasks to each newbies, they have fixed a deadline of 10 days to submit the task to the community. The closure report of the task is on the etherpad. The best contributor will get some special prizes from mozilla. Finally, we have ended the whole session by announcing about the mozilla student ambassador program and distributing mozilla swag among all. The next meetup will be held on in between 15th august to 30th august, 2013 for durgapur community.

Thanks to everybody for making the whole event successful by executing each and eevrything in a proper way.

Event page:- https://reps.mozilla.org/e/mozmentoring-bcrec/

Closure report:-https://etherpad.mozilla.org/remo-mozmentoring-bcrec

Durgapur-Mozconnect:- A review path for Mozilla Durgapur

Every plan after execution needs review at its end point. The awareness towards Mozilla and Open web was started in Durgapur from Mozcafe@ bcrec from 13th February, 2013. That event was successful. But to measure the success and growth in contribution towards Mozilla and its products from  mozcafe@bcrec, we have hosted a small meet-up named “Durgapur_mozconnect” near Bidhannagar, Durgapur (West Bengal) on 13th April, 2013 from 01:00 p:m to 04:00 p:m.

15 participants including previous contributors (Chandan kumar, Biraj karmakar, Gaurav Kumar, Umesh Agarwal), new contributors (Amit Kumar Thakur, Neeraj Goswami, Mrityunjay Kumar Singh, Souradeep De, Apoorv ashutosh, Shubendu Ghosh) and upcoming Contributors (Avinash Kumar, Shantanu Ghosh, Zubin Tiwari, Abhishek Kumar, Sourav Kumar) from Dr.B.C. Roy Engineering College, Durgapur attended under supervision of Mozilla Reps Shahid Farooqi and One guy from Asansol.

The meet-up started with the introduction of all volunteers specifying their interest and contribution. I basically found many of them are interested or contributing in Mozilla localization, Sumo and Web development. But all of them are interested in FirefoxOS and apps development. We are hoping from the community to get a FirefoxOS Apps day soon in Durgapur. After that i have presented a paper on “How to imply Screen-shot Comparison technique in Mozilla Firefox Localization Quality Analysis.” with the help of the source taken from Fuel Project. The material will be available soon in all mailing list. After listening and sorting out the problems in contribution to localization and sumo, we have formed a team for FirefoxOS video Contest.

This is not the last but with ending we have fixed a Durgapur community Monthly meetup every month (if possible) in our college on 18th April, 2013 from 01:00 p:m to 02:00 p:m to track the progress of contribution in the community.

This slideshow requires JavaScript.

Thanks to Shahid, Biraj, Umesh, Shubhendu, Apoorv and Souradeep for making the same successful.

Event Page:- https://reps.mozilla.org/e/mozconnect-durgapur/

Etherpad:- https://etherpad.mozilla.org/remo-mozconnect-durgapur