Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!agate!soda.berkeley.edu!wjolitz From: wjolitz@soda.berkeley.edu (William F. Jolitz) Newsgroups: comp.unix.bsd Subject: Policy on Software Development for 0.2... Date: 30 Nov 1992 20:58:28 GMT Organization: U.C. Berkeley, CS Undergraduate Association Lines: 66 Message-ID: <1fdv9kINN597@agate.berkeley.edu> References: <ali.723149640@fred> NNTP-Posting-Host: soda.berkeley.edu Keywords: 386bsd, policy A note from the Developers Workshop: A few items related to 0.2 sofware development policy and acceptance of code. 1. Anyone may "hack" 386bsd to their heart's content, and may distribute their code as they see fit. We do not regulate anyone in this regard. 386bsd is a research and development system, and is expected to be changed, altered, or otherwise modified for educational and research purposes (or even personal entertainment). 2. Frequently, we incorporate code (especially related to ports of PD software, fixes, and enhancements) directly into future releases. However, for larger subsystems, new approaches and new work which may affect the future directions and choices of releases, we suggest that people work within the email Special Interest Groups to ensure that their work will be part of future releases. This includes shared libraries and the console work ongoing. Everyone's work will be reviewed, as long as it does not contain proprietary or trade secret code. 3. Everyone who is sincerely interested in 386bsd releases (and I mean sincere as in willing to work hard, willing to work with others, and willing to help others) is welcome to participate in all work on 386bsd development. 4. Conflicts of direction with respect to 386bsd development can be brought directly to our attention at wjolitz@soda.berkeley.edu. We can also be contacted by phone (contact me for number) from 7-9am PST. (Please do not place standard support calls - please use the netnews facility). For key develpment concerns, conference discussions can be arranged. A brief outline of email SIG policy and procedures: 1. SIG group charters will be out shortly. These groups are mailing lists which allow usenet as well as internet sites to participate (and even groups on compuserve and so forth). 2. To get on the SIG mailing list, please send in your registration form indicating what SIGs you would be most interested in participating in. Please only check one or two -- we want to keep each group focussed on the development issues assigned to each group. The current groups formed are as follows: databases, drivers, filesystems, international language support, kernel internals, multithreaded symmetric multiprocessing, networking and telecommunications, performance issues, security, shared libraries (already in progress), windowing systems. If you are interested in a specific area not on this list, send me email. 3. Some people who registered for 0.0 could not choose a preference for SIGs. Please send me email as soon as possible. 4. We are looking for SIG coordinators to work directly with us in guiding groups productively. Please send me email if you are interested. Please, coordinating a group is demanding and you must have a good technical grounding in 386bsd and in the subject matter. 5. SIG group reports/inquiries and new information will be coordinated from comp.os.386bsd.devel (or development). Other items: Bill and I will be at the SUN User Group Conference in San Jose, CA. Bill will be speaking on "Multithreaded Kernels: What Do We Need" on 8 December 1992 after lunch. We are also available afterwards for 386bsd questions. Lynne.