site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Am 27.06.2005 um 18:46 schrieb Michael L Torrie: Have fun, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I would have been perfectly willing to dive into the code and try to identify the problems I had and help Apple fix them, but I was unable to do this. IMHO, the really disencouraging thing is, you can fix bugs to some extents, just to find them with the next OS X release fixed independently by an Apple engineer as well. I was initially encouraged by Apple's embracing of open source, but I have come to realize that Apple is just as much a cathedral as Microsoft is, only they happen to use (fork) open source code in a legal and license-abiding way. The funny thing these days is, Apple prefers to work lots more with other open source teams, like e.g. FSF gcc, than with it's own community. If you want to know about and participate in the future of the Apple version of gcc, looking an Apple Darwin or OpenDarwin is moot, you have to discuss on gcc's mailing lists instead. An open, read-only bug tracking system would be a great start. When the interested public was locked out of Apple's cvs and out of Radar and OpenDarwin was founded instead, I told my fears about the effective end of community work with Darwin, but was flamed. Hmmm. Having clear patches to core code such as samba and openldap (opendirectory) would also go a long ways. Finally, shipping a self-hosting development environment (out of the box) would be a requirement to truly bring darwin back to where you feel it once was. There's nothing stopping the Darwin community to develop such things. But how would you build a strong community around a closed, deaf and mute cathedral? For me, Darwin is read-only source and OpenDarwin is fine for building add-ons at the CLI level: XPostFacto, Darwine, ... you name it ... This email sent to site_archiver@lists.apple.com