[haiku] Re: Google Summer of Code (candidate)
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Wed, 08 Mar 2017 08:50:21 +0000
8 mars 2017 09:23 "Ania Bui" <lichi.bui@xxxxxxxxx> a écrit:
Hi!
Thank you for your reply and addressing my concerns. I really appreciate your
explanation as it
gives a clearer idea of your expectations! Working with many clients
(especially difficult ones :))
is a big part of being a designer. So, I hope my experience will be helpful
in communicating with
the community and coming to a solution that satisfies the majority. I am
planning to start working
on GSoC proposal and I was wondering if you had time to glance through it
quickly and give me some
feedback?
Yes, of course. The best proposals come from early review and discussion. If
you share your work early, we can comment on it and you can integrate the
feedback, whereas if you wait until the last moment to submit a proposal you
built on your own, you miss that opportunity.
Also, are there any specific skills that might be helpful for this project so
I can begin
getting familiar or more proficient with them?
I guess you have already read
https://www.haiku-os.org/community/gsoc/2017/students
In particular, we request at least one patch submitted to Haiku. This means you
need to:
- Set up the development environment
- Compile and run Haiku
- Make some changes to the code
- Submit a patch to the bugtracker and get it through the review process
Tools and technologies needed:
- Some UNIX system (Linux, BSD, Mac OS X, or Haiku itself) to compile our
sources
- git, to checkout the sources and make patches
- C++, to actually make changes to the code
You will see if there is anything else needed, as you work on writing your
proposal.
Also, don't hesitate to use the mailing lists (this and haiku-dvelopment) as
well as the IRC channel for more direct discussion.
Other related posts:
