[haiku-development] Re: Haiku development: getting involved
- From: Sean Collins <smc.collins@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 09 May 2013 20:02:40 -0400
Stephan Aßmus wrote:
IMHO the best motivation is to work on something that annoys you, that
you need, or that you find interesting.
The bug tracker is full of tickets with interesing/annoying bugs or
feature requests. It probably helps to look at the tickets by
component. You can pick an area that you think might contain
interesting stuff and then just look at the tickets for that component.
Or you simply try to use Haiku and look at it from the perspective of
it being your main operating system... what sucks and what would you
like to change? If it's something fundamental about the user
experience, it's probably best to discuss it here on this list. Or you
risk your work not being included if it isn't considered "within the
Haiku vision" by many. (The Haiku vision isn't often very clear or
defined, mostly it can only be derived by discussion here.)
I have been reading on this list for a long time now, even replied more
then a few times, the haiku vision is pretty clear cut imho. Mimic BeOS
as much as possible. Provide a mostly binary compatible OS to BeOS r5,
and make the system sane, orthogonal and practical to develop for. Also,
put the users first.
Sean
Other related posts:
