If we were to go by time invested and seniority, then here is the list that I would initially recommend. However, I agree with Chad that we should give everyone on the mailing list a vote. I do think that we should set a time period for such a thing, and a way of formally accepting your vote (so we dont go chasing votes from stale email addresses). We'll get a list together and publish it in our webspace. Once we close the registration, I like the idea of adding new members by proposal to the group. But the list still has a point:
- Mircea Cristian Racasan (for writing the AOT) - Bruce Markham (for interrupt work, kernel work, and even the infamous function pointer stuff) - Johann Macdonagh, as one of the original visionaries and community leaders, for his work on the initial AOT, his work on testcases and setting up the build system, and generally helping to steer this beast of a project. - Sander van Rossen, for his excellent work on the kernel, particularly his keyboard and console code - Me, but I won't talk it up, I really just do the odd jobs.... just a lot of them That leaves what I call "intellectual" contributors to the project. Those that are helping in discussions, writing documentation, working on specifications etc. That group in my mind consists of anyone who's posted a message here, but particularly Scott Ballmos has been doing a lot with ongoing JIT/VM design crunching and his continued availability for discussion on IRC. Another one that sticks out is Michael Schurter, who provided our initial webspace and got the ball rolling. There's many others who contribute with discussion at the IRC channel. Chad, you are doing a great deal organizing changes in the way we're running the project and that is admirable. Aside from that though, you've invested very little time here and done very little other than talk. I'm not sure how you would get a seat at a "time-invested" based provisional board. Nevertheless, I would still recommend that you get a vote on the provisional board (if we weren't doing it by the mailing list registration) because I do have a lot of respect for the work you've done in the past and that makes me think you're going to help us along in many ways. . On 8/30/07, Darx Kies <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > As this project was not started by any one person, I personally like the > > FreeBSD Core Board model. At first, until we have a working kernel and > > bootable OS, we would consist of a provisional board consisting of the > > active core people as generally determined by this mailing list and IRC > > (so far, looks to be me, William, Chriss, Bruce, and Chad. Please add / > > delete if otherwise). > I kept thinking and thinking.... > > ...and I somehow disagree with the provisional board. William, Bruce and > Johann started the project. > Correct me if I am wrong. AFAIK Johann doesn't have time anymore. > Provided they he is still interested > and has time the provisional board should start with these 3. They > should decide who should join the > provisional board. (In the first list of names, the name of Logical > Error is missing.) > > Provided again that Chad will be part of the board and the board decides > to choose GPL/LGPL , > the il2cpu (which actually hasn't been announced officially on the > SharpOS ML), if it wants to be > part of SharpOS would have to obey to that license as well. And it > should be in the SharpOS > repository too even if only in the sandbox for the beginning as William > said. Even if il2cpu, > as Chad mentioned, is not targeting SharpOS only, it should still be > very obvious that the kernel and > all the code would rely on il2run, and there for it should be part of > the SharpOS project. Another issue > was that il2cpu is using LINQ that is not yet supported by mono (or at > least not entirely). SharpOS > *is* an open source project that shouldn't leave anyone out. And that > should be respected. Solutions > like using the linux TFC (is that the right name?) client (which is not > free?) to only be able to contribute > to il2run and then installing the ORcas Beta2, that no one knows for > sure, when will come out, > won't help developers getting involved with the project. And solutions > like using only the binaries > of il2cpu to develop the SharpOS if one developer doesn't want to > install Orcas Beta2 or can't do that, > won't improve the situation either. That is why the project should > target .NET 2.0 IMHO. > > I, for one, am getting sick and tired of all the discussions that seem > to lead nowhere. > > We should really go on with building the provisional board so that there > will be some decisions made, > before the whole talking tears the small SharpOS team/community apart. > So that we can stop all the bashing > and flaming and so on and start addressing the pitfalls like the > documentation and start coding again > so that we can make the first release. > > > Chriss. > > PS: It is 6 a.m. here and I am sorry if some of my email is not clear or > I misspelled any names. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
