Saturday Feb 23, 2008

Code For Freedom contest closed

Well, the Code For Freedom (CFF) contest is finally over. The results are posted on the CFF site. The grand prize winners will be awarded at Sun Tech Days in Hyderabad on 29th Feb 08 by Ian Murdock. Congratulations to all the winners. Thanx to everyone who contributed. Without all these contributions, this contest would not have been successful.

I was tracking the contributions to the OpenSolaris technology. The load in the initial stages of the contest was negligible. But during the end it reached a peak. I used to stay awake till 3am chatting with students answering their queries. Here is a screenshot of one of my gmail chat session. In the last two weeks of the contest, more than 50 contributions were submitted. The last contribution to OpenSolaris was submitted on 23:57 on 14th Feb 2008 IST! Just minutes before the contest ended.

Many students have committed to continue the contributions to OpenSolaris even after CFF. This contest has definitely raised the interest level of the students across India to contribute to open source projects. I believe, its just the beginning ...

Its not just the students, even we have learnt a lot while conducting this contest. We have received a number of feedback on what went well and what could be improved. Many people are asking if we'll have CFF next year. Well, I don't know. AFAIK, no decision has been taken in this regard. I hope it is...


Tuesday Jan 08, 2008

More tips for OpenSolaris CFF participants

Always...

  • send mails from email ids registered in SCA.
  • use SCA number in every mail you send to request-sponsor.

Before picking up a bug...

  • confirm if a bug is already being sponsored on
    http://opensolaris.org/os/bug_reports/request_sponsor
  • ensure that 'Responsible Engineer' field of the bug is empty
  • avoid selecting RFEs if you don't want to work on ARC cases. ARC cases are a good learning experience, but it takes time. And we have little time for CFF to end.

As soon as you pick up a bug send a mail to request-sponsor alias. The mail should contain:

  • Name and email id of the contributor. If two of you are working, give both names and email ids.
  • The bug number and synopsis
  • Category and subcategory of the bug (this is FYI to sponsors)
  • A two or three line description of the bug
  • A tentative date (in dd-mmm-yyyy country neutral format) when you'll submit the fix.
  • Your SCA number(s). If you don't have a SCA, then mention that you have started a process to get a SCA number.
  • Do NOT request for a sponsor. This mail is only an intent-to-work mail. A sponsor should be requested when a fix is ready. If a sponsor has special interest in the bug, then even such requests could be picked up by the sponsor.
  • Check http://opensolaris.org/os/bug_reports/request_sponsor.  This page should be updated with your request in a couple of days.

After selecting a bug...

  • do not expect that a sponsor will pick up your request or help you with fixing a bug just because you sent a intent-to-work mail
  • develop a fix for the bug, on your own.
  • compile the source with your fix and generate a binary
  • test your binary (this is very important)

When a fix is ready send a mail to request-sponsor alias. The mail should contain:

  • Name and email id of the contributor. If two of you are working, give both names and email ids.
  • The bug number and synopsis
  • Category and subcategory of the bug (this is FYI to sponsors)
  • The fix. The fix should be sent in one of the following formats:

An attachment of 'diff -u <oldfile> <newfile>'
A link to webrev or diff (-u) output uploaded to http://cr.opensolaris.org
'diff -u' output inline with the mail if the fix is just a few lines of change.

  • Mention any testing that you have done. This can include sample output of command or the steps you followed to test your fix and its results.
  • Your SCA number(s). If you don't have a SCA, then mention that you have started a process to get a SCA number.
  • Now you can request for a sponsor. Please be patient while your request is picked up.

Note:

  • All mails sent to request-sponsor alias are NOT eligible for CFF contest
  • All fixes integrated before 14th Feb are eligible for CFF.
  • Fixes submitted before 14th Feb but which are not yet integrated will be reviewed. Only those fixes which gets approved for quality will be eligible for CFF (even if they don't make it to OpenSolaris for some reason). So, make sure you have tested your fix properly and mentioned the test results in your mail to request-sponsor while submitting the fix.
  • If you have submitted a fix for any bug, then make a submission on CFF site NOW!
    Do now wait for your fix to be integrated or someone to tell you that you are qualified.  Make a submission now and we'll determine the quality.  Remember, make the submission ONLY if you have submitted a fix.
  • Do not request for a sponsor when you have picked up a bug.

Common mistakes:

  • Using unregistered email ids.
  • Not mentioning SCA numbers in the mail
  • Not giving the details (full name, email id, SCA #) of partners
  • Not mentioning existence of a partner while sending a mail to request-sponsor
  • Selecting wrong bugs (already sponsored, already fixed, too complex etc)
  • Copy pasting from others mails without editing the details properly
  • Requesting a sponsor without a fix

Please refer to my earlier blogs as well:

http://blogs.sun.com/jkini/entry/tips_for_opensolaris_cff_participants

http://blogs.sun.com/jkini/entry/contributing_to_opensolaris

BTW, did you know that Campus Ambassadors have have access to more details about the bugs than what is presented on opensolaris.org?  So, if you need more info about a bug, contact your CA!

There is little time now.  The contest is closing on Feb 14th.  Rush your entries and your submissions.  And just because there is little time don't compromise on quality either!

All the best!

About

jkini

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today