Milan Jurik writes: > You have good opportunity to discuss the most of features in psarc > process before integration. And in many cases even in stages like "one > page". But it is project team decision if they want to work on their > project in private group or not. Like in the rest of world. And I don't > agree that this level of freedom is bad thing.
There are certainly cases where working exclusively in the open may be too much -- integrating a small bug fix, for example -- or where it's just impossible -- such as in modifying usr/closed. The process should "shrink to fit" the application, rather than being a noose. However, I do think the expected default (particularly for Sun employees) should be to do things in the open. This means that if there's an I-team mailing list, it's on some open site (such as opensolaris.org). If there's a project source repository or documentation, then that's kept in the open. Schedules and lists of people involved should be open. If there's an organized code review effort, then that's in the open. And so on. Particularly given Sun's at times haphazard relationship with the concept of open source, it seems quite likely that there are more than a few who doubt our intentions, and I think it's very important that we aim for best practices in the work we do. Even more so, when there are alternative open projects (such as BSD and GNU/Linux) where contributors could go instead, we need to be even better. And I feel that we should begin to view projects that are less open with some skepticism. Certainly, there's a transition that's still in process, with some groups and projects being less "open" than others, and this should improve with time, but we do need to start setting high standards, and asking questions. Opensolaris.org isn't just a marketing gimmick. It's not just a "user group" or way for Sun engineers to contact customers directly. Instead, it's a software development community, and the elements of development (direct access to project gates, open discussion of requirements and design, and so on) need to be present. -- 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 opensolaris-discuss@opensolaris.org
