Just a final reminder that status reports are due tomorrow afternoon,
please submit your reports ASAP so as to make sure they get included.
Just as a reminder, this is a request for status for on-going and
completed projects since the last status report, and can include both raw
software development and other things that might be going on. Things
don't have to be merged into -STABLE for it to count, it can be "shoot
yourself in the foot"-style status from -CURRENT.
Things I haven't received status reports on:
- KSE
- SMPng
- OpenSSL
- OpenSSH
- KerberosV work
- KAME
- The kernel summit at USENIX
These are all important things that are going on in the project, and we'd
like to let the world that we're doing this cool stuff.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
---------- Forwarded message ----------
Date: Sat, 28 Jul 2001 18:26:31 -0400 (EDT)
From: Robert Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: FreeBSD Monthly Development Status Report -- Request For Submissions
It's that time again! The last FreeBSD Development Status report was over
a month ago, and given its success, we'll try it again this month. As
with the previous edition, I'm interested in seeing about one paragraph
per on-going project (or for major projects, a paragraph for each major
component of the project) describing work that has happened since the last
report. If no prior report has been given for the project, a general
overview paragraph as well as status is acceptable. If more than one
person is working on a project, only a single report should be submitted
(although if there are reports for components, they might be seperately
submitted by the relevant developers). Take a look at the previous
month's report for a sense of how this works (in particular, see how
TrustedBSD and SMPng reports were broken out). Developers should feel
free to submit more than one report, if they are working on more than one
project.
Reports should relate to the FreeBSD Project, but are not limited to
software development: they could include documentation work, web work,
FreeBSD.org cluster management, cooperation with application developers,
public relations activities, partnering with companies, funding
announcements for new projects, etc. In the past report the primary focus
was development, and that will remain important to the status report, of
course, but other parts of the FreeBSD Project are welcome to submit
status!
Please submit reports in the following format:
Project: (name here -- required)
URL: (URL, if any, here -- omit line if none)
Contact: (name and e-mail address of a contact point -- required)
One paragraph on the topic of the project status since the last report,
indented two spaces, and wrapped before column 78. Plain text only,
please.
Please send submissions to:
[EMAIL PROTECTED]
The deadline for submissions is Friday August 3, 2001, at 3:00pm EST. The
report will be released soon thereafter.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
