> As Chad said, driver cross polination is very good example, and since > drivers in SharpOS will be separated by a well-defined ABI, they can > be classified as a separate work from our kernel, and thus be licensed > in a different way. If we wanted to, we could collaborate on driver > APIs, something which has never been covered by either the ECMA
As per my previous mail, I doubt either will want to be restricted by the others design. Aside from license issues, my ideas revolved around knowledge sharing of hardware etc... as that is the hardest part of implementing drivers, and possibly some sort of port agreements. > The biggest problem so far in allowing such collaboration. The > communication barriers have not yet changed. The Cosmos project is > very opaque to me, with so little available to work with The Cosmos-Dev list is pretty open, and we have a Cosmos-Dev chat on skype. The admin team is not officially formed yet, but is quasi formed. I'll be resolving that in coming weeks. At least initially it will start out Indy model, which is closed. The Indy model puts all focus and discussion on dev (open) and only very limited items on admin (closed). Indy admin was closed because it dealt with a lot of NDA stuff with Borland. So maybe Cosmos admin would be open, but we'll have to see and that itself will be an admin decision to open it or not. But even if its closed - its not really a big problem as Indy model puts a lot of stuff that other projects put in admin, in dev. The admin is basically for NDA stuff, and resolving things that for some reason leads to deadlock or problems on dev. But dev generally "runs" Indy and admin are for arbitration type things. > participation there is totally limited to observer only, not only to > avoid stirring up trouble but also because the mailing list is closed, Cosmos-Dev isn't closed, its just join approval to keep spammers out. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
