> The problem I see is that most open source projects are not managed, >they simply evolve. This typically means that the projects are never >x.0 releases, they are eternally stuck in the 95% complete stages and >lack the polish of commercial software. This is despite the more >complete testing and review process that an open source project sees. > Agreed -- this MUST BE tended to > Solving this problem is the task I would like to see this project take >on as well. OBOS, as I'll refer to it, needs a RedHat, an entity to >control the project, to set release goals, and to ultimately work with >the GOBE's and Apacabar's of the world to establish a commercial >distribution presence. In order for this project to succeed, we need >more than to keep the community together, we need to continue to expand >the community, without the religious zealotry of the OSS, FSF or Linux >is better set. This means the need for commercial partners. > mmm... maybe > There are a slew of little issues facing this project, not the least >of which is naming. BeOS is a registered trademark, therefore is a >liability to an unfunded project. First thing to done, change the >name. OBOS, might work in the short term, but not in the long term. right on (I've already warned about this) >Legitimizing the project means that the code and the project needs to be >documented from day 1, not years later ala the LDP (Linux documentation >project). It also means that we need to approach some of the most vocal >and strong supporters in the community to throw some weight and >credibility to the project, Scot Hacker, Chris Herberoth, Daniel Berlin, >Dane Scott, etc... Each of these gentleman bring significant >credibility with them in the community. > that would be nice! >These are my thoughts, > as always take them with a grain of salt > >Andy good thoughts!