From owner-freebsd-hackers Tue Sep 28 5:46:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 34E0A14F73; Tue, 28 Sep 1999 05:46:07 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.30]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA21D; Tue, 28 Sep 1999 14:46:06 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id OAA35308; Tue, 28 Sep 1999 14:46:51 +0200 (CEST) (envelope-from asmodai) Date: Tue, 28 Sep 1999 14:46:51 +0200 From: Jeroen Ruigrok/Asmodai To: hackers@freebsd.org, current@freebsd.org Subject: Call for projects Message-ID: <19990928144651.B35262@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since no-one except Poul-Henning gave a start with this I thought I might try my hand at this. Given FreeBSD's rapid development over the last year a lot of things around the releases have changed. Nik Clayton and his team are doing a terrific job to keep up with the documentation. However, what has been lacking, at least in my opinion, is the lack of alerting less advanced, more time-restrained, however you wish to call it, hackers of tasks which need to be fixed in FreeBSD. The PR system is nice and works pretty well [thanks to a lot of people] but it is not what I meant with my above words. What I did mean though, is that when someone messes with source code at large in FreeBSD to let the hacker/developer-community know of these changes plus point out some areas which need to be fixed/looked-out with these patches in place. Small-term projects. Also, put out more patches on either -hackers or -current [depending on what platform the patches aim at] and call for more test reviews to eliminate more and more initial bugs upon introducing. Plus, let the doc guys know what changes have been made and in which places the docs should be altered. Doesn't take much, but remember that not every docperson is a kernel hacker and vice versa, so UTSL, how well intended doesn't always help in these cases. All of this is merely a call for clearer communication between the diverse efforts within the project as a whole and external hackers with no access to the repository but who wish to send-pr diffs/patches to fix up forgotten/neglected/overseen areas in the code. Thanking you all in advance for helping on this. It's together we make this project work... -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Any fool can make a rule And every fool will mind it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message