>Good evening, troops! Hey, Michael and everybody else! >There are now more than 60 people on this list. WOW! I am consistantly impressed more and more with the BeOS community. Yes, this is very cool. I'm so excited I can hardly contain myself! =P >Those of you who have already mailed me, I will sign you up for items. Those who have not, let me know. Where/when will you post these assignments? >Another is personal - I am moving at the end of this week, so we are packing, etc. Good luck! >For what my approval is worth, the charter that was posted here a few days ago (cut and paste coming) >is very good. Thanks to Daniel Reinhold. Count my vote for Dan's charter. While I agree that publishing a lot at this point might be unwise, this should probably go up on sourceforge. >Other issues: >License - on source-forge, I chose MIT License. Works for me. >Leadership - I think (and others can certainly talk me out of this), what I would like to do is >break into groups. Small groups centered around kits would help in this regard. A good idea. I think the main list should continue as an open forum for the various kit teams to discuss what they've done with everyone and get input. And as a place for people coming into the project later to start. >I am looking for motivated, mature people to lead groups. I personally will lead the kernel group >for now, as well as the project as a whole (unless the majority disagrees). That just gives a >single point of contact for people to get to us, as well as dealing with administrative things. >I am not a dictator. Promise. :-) Michael's got my vote as over-all project lead. His efforts have been instrumental in getting this ball rolling, and IMO show a capacity to take on the resposibility of keeping us all headed in roughly the same direction. ;) If nobody else is dying to do it, I'd be happy to lead a team as well; my primary focus lies with app_server/app kit/interface kit -- libbe.so, I suppose. >Final note: > >Please forgive the length here. There are a lot of people interested in the kernel. Suggestions have >ranged from using Linux to using the Be kernel. I want to draw a line in the sand. Short term, we >have to use Be's. I see only two possibilities for a kernel on a long term basis. Either we modify >NewOS or we make one from scratch. I have emailed Travis as a representitive of the group asking >him what he would like to do about this. I would love to get him on board. If not, we will write >our own with NewOS supplying code and ideas. Several of us had a fairly long discussion on this very topic this afternoon (preventing me from getting *anything* useful done ;) and the concensus as I read it was quite solidly on the side of using NewOS as our starting point, with general agreement that having Travis on board would be cool, but not strictly necessary. >We have to make some decisions some time or we will never get anywhere. This is one >that I want to make sooner and more concisely than others. :-) A conclusion that this afternoon's discussion also arrived at. Man, I'm excited about this! =D e Data is not information, and information is not knowledge: knowledge is not understanding, and understanding is not wisdom. - Philip Adams