faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: So what is happening with Safari Patches?
by Mike Hearn on Friday 08/Oct/2004, @08:12
|
I think it is a very fair evaluation, to be honest. It's well known how to have corporate hackers work well with volunteer hackers, it's done in open source projects like the kernel, Wine, and yes KDE/GNOME all the time. You send back patches in series, with a detailed changelog. You should develop those patches in the open, with discussion on the mailing lists.
In other words, you do not do what Apple has done - effectively fork the codebase in secret and then give the original developers a huge unworkable patch dump. I've had to deal with such things from TransGaming in Wine and they're basically useless, especially as often they duplicate code already written by volunteers and usually nobody understands the changes except developers who aren't in the community. The way CodeWeavers does it is *much* preferable (disclaimer: I am biased, I work for CodeWeavers. But I wouldn't work for them if they didn't interact with the community well).
To be frank it doesn't surprise me that KHTML has forked, Apple clearly have no interest in working with the community on it and demonstrated this from the start. They fulfill their legal obligations and do no more. |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
