Differences between revisions 29 and 30
Revision 29 as of 2010-08-15 22:55:27
Size: 20522
Editor: ari-tczew
Revision 30 as of 2010-08-17 07:34:39
Size: 20879
Editor: 59
Deletions are marked like this. Additions are marked like this.
Line 172: Line 172:
   * (ppl merge fixes FTBFS)
Line 185: Line 187:
Line 222: Line 226:





I, Bhavani Shankar, apply for MOTU.


Bhavani Shankar

Launchpad Page

Wiki Page

Who I am

I am a 23 year old cerebral palsy physically challenged guy and an Electrical engineer from Bangalore India

My Ubuntu story

My involvement in the community started back in 2007 where i worked on the forums (answered to around 4000 questions) which I really like doing Gradually I did a bit of translation in my mother tongue kannada and now active in bug triaging and packaging over past year and a half.I am an ubuntu member from November 2007

My involvement

My involvement In the commmunity ranges from the answer tracker to translations to malone and soyuz of late (from the intrepid cycle) .. My list of packages can be found here

Examples of my work / Things I'm proud of

Mostly I work on merges and syncs and new upstream versions and bugfixes. Some bugs I have worked and fixed:

In Jaunty release cycle with the collaboration of dholbach and hamish in debian I updated the whole geda stack in ubuntu (some of them which had missing build dep on intltool which I forwarded to debian and got it synced here) Some of the bug reports:

I am active in updating gnome-lirc-properties from Jaunty cycle

Some of the other bugs I have worked on:

Updates of ugene package:

Other bugs I worked on:


Some FTBFS bugs I have worked on recently:

(Some of the packages failed to build with new ffmpeg and I fixed few packages by defining STDC_CONSTANT_MACROS which is a workaround to allow C++ programs to use macros specified in the C99 standard that aren't in the C++ standard AFAIK.)

Few SRU requests that I filed recently:

Long list of packages uploaded can be found here

Areas of work

I mainly work on merges and syncs and updating packages and fixing FTBFS. Especially I m interested in Science packages (Electronics to be precise) and as a part of the MOTU science team as a long standing contributor ( and I maintain few packages in debian Major notable things are:

reviving xoscope in debian

maintaining mobile-broadband-provider-info in debian from close to a year where I forward bugs upstream according to their relevance and do a git pull twice a month and update the package in debian and due to its integration with NM now the popcon of the package has risen almost exponentially


Copied emu8051 from ubuntu and almost repackaged it completely with packaging improvements to comply with modern standards

Serving on board of pkg-electronics as a senior packager/developer

My Debian QA Page

Things I could do better

Perhaps maintain more packages in debian and in ubuntu and work on SRU's more

Plans for the future

Just to keep contributing in a single hand as long as possible Smile :)


* Continue to keep contributing in whichever small way I can.

What I like least in Ubuntu

ubuntu-revu seems somewhat less transparent to especially new guys who want to get their package into ubuntu as compared to debian-mentors where packagers put the links to their packages from on debian mentors mailing list and DD's give a quick response thereby packagers feel impressed and pushed even more to get their package into debian


If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.

Bhavani is tireless in merging, syncing and fixing FTBFS. IMHO there is no need for a debate on whether he should become a MOTU or not! -- Bilal Akhtar

I would question this application. Bhavani is a keen self promoter and has made contributions with questionable background workings. While undoubted a contributor the way he goes about it and the work passed off as his own content is questionable. This is not me saying "no" to membership, this is me raising a concern and question. -- ikonia

Hello matt, I could not understand what were you referring to.. I ve also made mistakes in the past but I have taken care to correct those mistakes and have come a long way learning something related to ubuntu, If you have any doubts about my contribution I ll step down from my ubuntu membership gladly though and can you please provide a justification of the same --Bhavani Shankar

Bhavani is very huge contributor for Ubuntu development. His issue is not including people work in debian/changelog. I think that every person who has added a change in revision should be mentioned in changelog file. In my opinion it's important when sponsor is working on someone else's patch - sponsor should not ignore contributors work. Next case is why Bhavani links bzr branch to every bug if patch is available through debdiff? For high position in top contributors? I don't care... I would encourage him to more visiting #ubuntu-motu. We are there not only when we are in trouble. As a team we can help other people and discuss about who will take a merge. However, I think that Bhavani is enough expierence with packaging and if sponsors/DMB team don't have objections, I'm +1 for this application. I would like to see the same quantity of work by Bhavani done by himself as a sponsor with upload access! ari-tczew


As a sponsor, just copy the template below, fill it out and add it to this section.

Benjamin Drung

General feedback

I sponsored around 100 sync requests from Bhavani. He described detailed enough, why the Ubuntu changes could be dropped. I can't remember any serious problems with his requests. Looking at his other work, he is definitively experienced enough to become MOTU. He will be an asset for the team.

Specific Experiences of working together

Here is a list of latest sponsored syncs:

Charlie Smotherman

General feedback

Bhavani is a work horse when it comes to doing sync's, merges and fixing FTBFS. I have sponsored 10 packages for him and his work is of good quality and rarely did I have to ask him to change anything and when I did he was quick to respond. He works well with other community members and I think he would make a good addition to the team.

Specific Experiences of working together

Here is a list of sync/merges I have sponsored for Bhavani:

Areas of Improvement

The only suggestion I have for Bhavani is to do a couple of SRU's and backports to make himself more familiar with the process.

Stefano Rivera (tumbleweed)

General feedback

Bhavani's work is technically excellent (and theres a fair amount of it). The only comments I've made in review are merges that could be syncs. I strongly endorse this application.

Specific Experiences of working together

600129, 596190, 598947, 599245, 599256, 599774, 610149, 600917, 609019

Areas of Improvement

None I can name.

Daniel Holbach (dholbach)

General feedback

I think I sponsored around a hundred of Bhavani's changes. The reason I didn't suggest to him earlier to apply for upload rights already was that there were mistakes and oversights in his sponsoring requests every now and then. The quality of his contributions improved over time though.

Bhavani is all over the place. There's hundreds of contributions of his. While we all benefit from synced and merged goodness from Debian and Upstreams, I sometimes think it'd be better to do a bit less with more focus.

Specific Experiences of working together

There's 200+ bugs Bhavani and I interacted with and while there's lots of material for simple, good, easy and well-done work, here's a few examples that weren't done so well:

Areas of Improvement

I very much appreciate Bhavani's work and as I said: the quality of his contributions improved a lot, but still more attention to detail and more focus stay the primary areas of improvement.

Fabrice Coutadeur (fabrice_sp)

General feedback

I sponsored around 120 uploads of Bhavani, most of them, merge or syncs. The quality of what Bhavani submitted increased a lot over the last 6 months, there is still some cases in which he should have been more careful.

Specific Experiences of working together

Obviously, with 120 uploads, there is a lot of good examples of work.

Some that weren't so well are: obsolete package, so removal instead of fixing FTBFS


Areas of Improvement

Bhavani should challenge a lot more the previous changes in a merge, and not make a mechanical merge. Also, submitting the changes to Debian or checking the Debian package should be the first step. This would save him a lot of time.


=== General feedback ===
## Please fill us in on your shared experience. (How many packages did you sponsor? How would you judge the quality? How would you describe the improvements? Do you trust the applicant?)

=== Specific Experiences of working together ===
''Please add good examples of your work together, but also cases that could have handled better.''
=== Areas of Improvement ===

Bhavani_Shankar/MOTUApplication (last edited 2010-08-18 14:02:13 by 59)