Sugar Labs

Summer of Code/2012/autorpmgen

< Summer of Code‎ | 2012
Revision as of 23:15, 9 February 2012 by Callkalpa (talk | contribs) (→‎About your project)


About You

  1. What is your name? Kalpa Pathum Welivitigoda
  2. What is your email address? callkalpa@gmail.com
  3. What is your Sugar Labs wiki username?
  4. What is your IRC nickname? callkalpa
  5. What is your primary language? English
  6. Where are you located, and what hours do you tend to work? I am located in Sri Lanka (GMT + 0530h), work hours can be varied as required and willing to work at night as well.
  7. Have you participated in an open-source project before?

About your project

  1. What is the name of your project? autorpmgen
  2. Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
    • I am going to make a tool which will automatically build the rpm packages for the existing sugar activities. It builds new rpms as new activities are submitted or new updates are issued for existing activities. And there will be a separate repo established for those rpms.
    • At the time of writing there are almost 400 sugar activities. Projects like sugar on a stick have widen the community for these activities (like they can be used by Fedora users as well). Still that is possible only for the packages that are packaged for Fedora (making the rpm, going through the review process and all that). What I am trying to do is spread it even more. People who want to use activities on their Fedora box will just add the repo and install them. There's no need for them to be approved for Fedora repo. This is true for any other rpm based distro. Further there is no need of maintainers who need to follow the development and build new rpms. (Currently there are packaged activities for Fedora where there are no further rpm issues due to lack of maintainers). It is even better to extend this to other package managing systems as well like deb. But I have no experience with that at the time of writing so I will for now just stick to rpm.
    • The idea is to maintain a ini file like file for each activity and generate the spec file out from that and finally generate the rpm. There is Spectacle, a tool to generate spec out of a ini file and Tito which can be used to build rpm from the spec file.
  3. What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week.
    • 1st and 2nd week : Generate ini file (details extracted from the activity.info file in each activity and from other sources related)
    • 3rd week : generate spec file from the ini file
    • 4th and 5th week : generate rpm from the spec
    • 6th week : establish a repo for the rpms
    • 7th week : implement the new activity submission and update submission feature
    • Here I have outlined my schedule only for coding. Evaluations will be there and the schedule is subjected to undergo changes as necessary. For generating the ini file and rpm, I have allocated two weeks each and this is with a safety time margin. I don't think they will take that long to implement.
  4. Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
    • I've been packaging some of the sugar activities for Fedora which is directly related to the core of this proposal. I started with Ruler about 6 months ago with the guidance of Peter Robinson. Since then I have been maintaining and co-maintaining around 10 packages associated with sugar activities. I am familiar with python and bash scripting as well.

You and the community

  1. If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
  2. What will you do if you get stuck on your project and your mentor isn't around?
  3. How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous

  1. We want to make sure that you can set up a development environment before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.
  2. What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
  3. Describe a great learning experience you had as a child.
  4. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2012/autorpmgen&oldid=75407"