Jonas, Whenever you feel somewhat secure about something, feel free to commit. As long as it doesn't break anything you should be ok (which is usually the case with new commiters, as we tend to double check stuff). If someone sees something wrong about it, you should get a reply in the commits list. Several people read the commit contents so if there's something to be pointed, it will be. This way you can tune yourself to the project while producing at the same time. If in the other hand, you don't feel secure about a change, because for instance it affects several subsystems, or changes an application's behavior, post the patch here and wait for comments. Smaller issues (which obviously are also important to get right, so we have an overall clean feel) are better discussed with code, so we can keep a good production/discussion ratio. These kind of lengthy discussions are required when large changes are due, which may have a wide impact. However, personally, i would rather see the 18pt font issue being fixed rather than changing about windows. It is a good metric to think about how many users are affected with a change. The bigger the number, the better. But you are free to spend your development time as you wish. :-) Have fun, Hugo On 6/9/07, Jonas Sundström <jonas@xxxxxxxxxxx> wrote:
"Hugo Santos" <hugosantos@xxxxxxxxx> wrote: > Guys, is it me or for the last couple weeks have issues of > minor importance been span over long discussion threads? > What if rather than discuss process, people discussed the result? Yes, fixing virtual memory bugs, etc, is infinitely more important to Haiku's progress than these GUI details, and naturally I would rather have the top talent of this project focus on the hard parts. I'm not sure it would be okay for me commit a lot of changes all over the tree without asking first, especially since I just got commit access, but if you guys prefer it I can work more silently. There are just all these issues all over the place, and I'm dying to fix them. /Jonas.