I've been thinking the same. I've submitted a couple of bugfixes over time
to Apple but only one has been accepted (that I know about), haven't heard
anything back on the others. There are several other bugs that I know about
and would like to solve.
I would like an active development community around DSS and I think that
would be benefisial for all parties, also for Apple who would get new
features into their QTSS faster than they otherwise would. Although not
being a lawer, I think it would be possible to do a "guerilla" fork as long
as all changes are submitted back to Apple but that wouldn't be desirable.
The best is to have Apple's blessing, to create something like the symbios
between Fedora and RedHat EL. Preferably Apple should also be actively
involved, so that whatever new features they develop also shows up in the
open version.
A start could be to set up a wiki which collects patches and information
already availible and starts building a knowledge base. I can have one set
up by next week. Are there anybody else out there that wants to participate
in collecting the information, find links to already availible pages and
patches etc?
/Sverker
----- Original Message -----
From: "Cian Cullinan" <email@hidden>
To: <email@hidden>
Sent: Tuesday, December 13, 2005 8:31 PM
Subject: Re: DSS fork?
On 12/12/05, Dave Schroeder <email@hidden> wrote:
I think the problem is that Apple uses DSS as the base for QTSS, and
as such, can't necessarily quickly include changes that are submitted
by the community, because there's a lot more testing, QA, and
qualification from technical and marketing angles that needs to
happen.
While I understand this may be the case (is it, does anyone know?),
look at something like Redhat/Fedora, where Redhat using Fedora Core
as a testing ground for new ideas that they role into their enterprise
products when they think they are ready. I'm not saying we should
expect anything like this from Apple, RH invest a lot of time and
money in this relationship and they come from opensource roots, but
this shows at least that it's possible to have an "enterprise class
product" - whatever that means - and an active developer community.
Anyway, not trying to be belligerent, just trying to start some debate
around this idea.
