joseeantonior

Just another WordPress.com site

Month: May, 2012

Accomplishments – Should I write one?

As many of you know, Jono Bacon, along with other people, has been developing a system called Ubuntu Accomplishments, which is very cool, indeed. You earn trophies for doing different things in the community, or locally. The system even has its own daemon!

But, the problem is: We need accomplishments writers! Although writing one seems very complicated, it’s much easier than it seems. For me, it took less than 45 minutes, including a step-by-step class on how to use bzr to upload and propose for merging by Rafal Cieślak. Then, if you’re just writing it, it would be around 15-20 minutes. I started working on a “Gain an Ubuntu Member Cloak” accomplishment. Here’s what I did:

  1. Write the script. When writing the script, if the accomplishment needs to be verified by checking if you’re a LP team member, you can just grab one of the scripts and modify it writing the correct team name (these are on the scripts folder, in the trunk branch). In my case, I used the motu.py script, and replaced motu bu ubuntu-irc-cloaks. Save your script with a name (name.py).
  2. Write the accomplishment file. You should use one of the accomplishments that is already created, modifying it with the correct information again (these are in the accomplishments folder, in the trunk branch again). Just fill in the correct information, and you’ve done it. Remember that, as it’ll be our official accomplishments program, it should be a squeakly clean and great documentation. Save this file with the name name.accomplishment.
  3. Write the test file. One more time, you can just grab this from the test files. In this you should specify two emails. The success email, is to give the tester a positive result, it means that it should be the email of an user that has already accomplished what needed, and so on with the fail email. You should save it with the name <name> (with no <>).
  4. Once you’ve done that, you should upload it to a personal branch, and ask for review.

After all this process, my accomplishment got into the collection, check it out!

Remember that all your files should be named under the same name. As you can see, this is not so difficult. I hope many of you get into this fun and helpful process. You can check http://wiki.ubuntu.com/Accomplishments/Creating/Guidelines for the guidelines. If you need any further help, just go to #ubuntu-accomplishments in freenode. Thanks to all of you who have already contributed, and to all of those who will contribute to us!

Just a few words about UDS.

The Ubuntu Developer Summit. One week, full of experiences, sessions, plenaries, social events, etc. One week where you find out what is the essence of this community. Last week I’ve had my first UDS. Believe me, this is something that entirely changes your perspective of the community. You get to know how things work, how the process of this cycle will be, and what are the projects. Most important, you get to know the people you will work this during all this entire 6-month cycle. With this post, all I want to say is thanks. Thanks to all the people who were there, making this event as great as they could. Thanks to Marianna, Claire, Claire and Michelle for organizing it, to the track leads for their work managing their tracks, to Chris Johnston and the crew for the great work we did, and to all the people that I don’t mention, but know they were very important for me in this first experience (I do not write the whole list because I would fill up the whole planet homepage). Last but not least, thanks to Mark Shuttleworth for making this awesome summits, that, apart from being a place to get work done, is a week full of emotions, that you will surely never forget.

 

EDIT on 15/May/2012: For the next UDS I go to, I promise I will sing in the karaoke!