Since 1998... Here until the last user leaves...

Haiku Google Summer of Code Interview with Smita Vijayakumar

by @ 11:21 am on 5/4/2009. Filed under Haiku

Various BeOS/Haiku related news sites are going to be hosting interviews with some of the Google Summer of Code students who applied to work on Haiku. Here’s the interview we did with Smita Vijayakumar, who applied to work on adding IPv6 support to Haiku. Smita’s entry didn’t make the final six, but she’s hopeful that there might be another Haiku Code Drive this year.

How did you hear of GSoC?
Through a friend who worked for GSoC in 2008.

What convinced you that Haiku is a project worth working on?

I liked the idea list, and the development work. I have had past experience working on similar features.

How’d you first hear about Haiku?
Through the Google Summer of Code list of organizations.

Do you have any experience with BeOS or Zeta?

What did you apply to work on, why did that specifically interest you?

I applied to work on implementing IPv6 support for Haiku.
It specifically interested me since I have 4 years’ development experience on network stacks.

If you do not get the chance to work on the project you applied for is
there another area that interests you?

I am open to good development opportunities that will involve learning for me.

Is there anything Haiku (as an organization, website, community,
individuals, any facet of Haiku) could’ve done differently to help you
as an applying student?

For supplying patches, there should be a set of bugs assigned to applicants, and mentors should evaluate quality of patches for the same bug fixed.

Was anything overly complicated or discouraging?
🙂 No. I personally did not fix a bug, since all bugs reported were application level bugs, and there was none which was a system-level bug.

Do you have any suggestions or constructive criticism for the people
involved with Haiku’s participation in GSoC?

Better feedback on proposals will really help. I understand there are many applicants, but if there is something specific missing in a proposal, and is highlighted, that helps to improve future applications.

Besides Haiku, did you apply to any of the other orgs involved with
GSoC? If so which ones?

I applied to Google Chromium and Asterisk.

Would you be interested in a possible Haiku Code Drive?

What influenced your decision to become a programmer?
I have always been passionate about programming, especially low-level programming, since it involves a lot of intricate logic and design.

What is/are your language(s) of choice?
C/C++ programming.

Did you work on any open Haiku tickets, and if so which ones and what
was your overall impression on the code you worked on? Any plans to
try working on other open items?

Though I did not work on any ticket, I did write up a few lines of code to test my idea in the proposal. This code never did find its way onto the code branch.
I personally feel the system-level code (especially handling of ICMP and the division between network layers) can be more modularized. I found some functionalities to be spread out.; This increases the chances of bugs.

3 Responses to “Haiku Google Summer of Code Interview with Smita Vijayakumar”

  1. Your GSoC application was particularily good, there wasn’t really much that you could have improved on as far as we mentors were concerned. But the patch requirement was really important to us and we favored students who submitted patches. Our bug tracker contains a lot of system level bugs, you can find those in a number of ways, for example by searching by component. You could have even asked to be assigned a bug in a certain direction, but the ability of students to find something to work on that interested them was one criteria for our evaluation and ranking process. In any case, it would be easier for students if we had better a preparation of tickets to work on. For example, some tickets were marked as “easy” and turned out not to be so easy after all.

    As far as the Haiku Code Drive goes, there is not yet an initiative to make it happen. I hope there will be one, but as always it depends on somebody to take the initiative and right now it seems like people are pretty much covered in work.

  2. Humdinger says:

    Thanks for that interview!
    Hmmm… I’m pretty sure that there are system-level bugs listed in Trac. Though probably none of them are marked “easy”. Which they almost never are, I guess. 🙂

  3. Smita says:

    Thanks for your feedback. I will keep in my mind your inputs, and get a fix on your bug tracking system.


Leave a Reply

You must be logged in to post a comment.

[BeGroovy is proudly powered by WordPress.]