Linus still releases his kernel, but there are so many other trees
out there worth looking at. I'd argue that a community project could
do just fine as long as it's properly managed, and coexist with
Mick's project, share, all that.
I wouldn't want to manage the community project, (I'm new at that - learning but new) but if someone's willing I'd love to see what it could grow into. Maybe I'd even make the leap into coco programing. (I'm a database/php developer lately.) I'd probably have a hard time accepting patches myself, I'm too much of a control freak, I want to make sure the code I write can work with the stuff I've only got a faint idea of. It makes for slow programing but I find it very fulfilling (most of the time), I'm just not used to working with a team yet.
On Jan 27, 2006, at 8:16 AM, Geoffrey Kruse wrote:
On Jan 27, 2006, at 8:19 AM, themacuser wrote:
I'd rather have one project. But I'd rather have two projects, one forking off the other, if the original goes stagnant.
And then we end up with two stagnant projects instead of one.
Francis Gulotta reconbot@xxxxxxx