Skip to main content


Recent posts

Getting Started with release notes

Release notes are a short descriptions describing what was fixed when we submit a patch that fixes a user facing bug.
At the end of a release, the release notes get rendered into a document that users and deployers can see what changed in the release.
In OpenStack we have a release notes manager called Reno.
Following are the steps that we follow:

        $ git review -d <change number>

To create a tox environment that will install our release note tool:

       $ tox -e releasenotes --notest

      $ source .tox/releasenotes/bin/activate
      $ reno new bug-bugID

The reno tool will create a new file in releasenotes directory that we can open and edit accordingly as the file contains a bunch of different sections.
Detailed information can be viewed here.

Dealing with multiple branches

On my interaction with my mentor one day I had a question about dealing with new commits that we make. Is that we need to create a new branch everytime? or wait for our review to get merged and then work again? wait what if we had hundreds of changes to be commited?
Is it still that we have to create a new branch everytime and remember those creepy names >_<.

So the answer was git-ready!
Two people fluent withh git-ready and git-review can easily work on a patch without being stopped by each other's change.
git-ready can be cloned or downloaded here.

From the Python Package Index (PyPi):

        $ pip install git-ready

Once git-ready is installed in a summary we can do:

        $ git ready

Then if we need to make any changes we just do:

       $ make my changes
       $ git commit -a
       $ git review

If we need to make our changes, we just do:

      $ git review -d <change_number>
      $ make my changes
      $ git commit -a --amend
      $ git review

Beginning as an OpenStack contributor

New year new beginnings..Happy new year everyone!. I am really happy to be a part of OpenStack community btw to make the article quick for you all, following are the things I learned as a beginner OpenStack contributor:

IRC: The most important to keep the conversation with team members going, I used to hang out a lot here. I personally used but there are a lot of other options available too! Hang out to the channels you are interested in here and you know what their irc recordings can also be found out here so you have recordings of the days and channels you are interested in :D.  The community is very warm everyone there is very helpful so not shy and start the ping.
DevStack: Depending upon your contribution type, but its always good to get acquainted with the know-how of a project. Extremely suggested getting this set up for code contributors. Can find out more about it here.
Gerrit: Is the code review and repository management system for git VCS and is primarily used by…

Outreachy internship begins

I am really excited as my internship with outreachy has begun on 05 dec 2017 and will last till 05 march 2018.

The best thing about this is "Remote work".  I am passionate about remote work and the opportunites it opens up are quite amazing and outreachy has provided me grounds for it.

For the rest few weeks I will be working on the project Keystone at OpenStack with my mentor Lance Bragstad and will try my best to get the things completed before Queens.
I will be working as per the session at PTG and will be applying the consistent writing guidelines as per this.

Outreachy: What? Why? How?

What? Outreachy:  For all those who have never heard about it, outreachy is managed by Software Freedom Conservancy that provides three-month internship to women (cis and trans), trans men, and gender queer people. For simplicity it can be thought of as a Google Summer of Code for specific genders and also with wide variety of projects ranging from coding. documentation, UI, advocacy etc. Its no doubt that outreachy has served people to start a confident-bright career in tech. I suggest all the eligible people to once apply for this amazing program once on their lifetime. Why? Many of you might have that question, Why? The answer lies in rest of the few lines from my personal experience: Breaking the conventional barriers of the college degree or onsite industrial experiences outreachy teaches a person to be a self-learner, communicative, confident and what not. I got to know about FOSS and the amazing opportunities it holds after knowing about this program :).
I got selected to this…

GitHub Hacktober Fest 2016

Hey folks altough its too late for the post but I feel its no bad sharing some swags earned :) ;).

Github Hacktoberfest in association with their friends organised this event worldwide  in which the github users had to create 4 or more than 4 pull requests in the month of february ,and all those who did it were to be given a github t-shirt cool isn't that <3.