William James writes: > > Those all sound like points for the kde project to discuss once > > it's established. There's no reason to constrain the project > > up front with them. > > It's better to discuss and define the scope of the project *NOW* > instead of getting the response 'we don't take that' from Sun *AFTER* > we did all the work.
What "take" problem are you talking about? I wouldn't expect a KDE project to deliver through any of the existing consolidations. It doesn't seem to make sense for any of them. So, it wouldn't have to conform to the rules of any existing consolidation -- it could, just like JDS, write its own. However, if you're expecting the community to mandate that some particular distributor (such as Sun) "must" include the work of a given project or consolidation, then I think you might be mistaken. Sun's own Solaris distribution is its own, just as the others are independent and can choose KDE if they prefer. If there's some specific problem with the development process related to this "we don't take that" issue, you'd like to see it fixed, please do share. I don't know what you're referring to. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
