Index: head/en_US.ISO8859-1/htdocs/news/status/report-sample.md =================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-sample.md (nonexistent) +++ head/en_US.ISO8859-1/htdocs/news/status/report-sample.md (revision 52319) @@ -0,0 +1,30 @@ +## Status Report Sample - This Will Become The Title ## + +Contact: John Smith, + +Link: [Link description here](http://www.example.com/project/url) + +Paragraphs are separated with an empty line. Use Markdown +syntax, the same as you use on GitHub. If you don't know +Markdown, just write it as if it was plain text. + +Introduce your work. Do not assume that the person reading +the report knows about your project. + +Show the importance of your work. Status reports are not +just about telling everyone that things were done, they also +need to explain why they were done. + +What has happened since the last report? Let us know what +is new in this area. + +Optionally include the information about the sponsor. + +If help is needed, make this explicit. List tasks, with enough +detail that people know if they are likely to be able to do them, +and invite people to get in contact: + + * First task + * Second task + * Third, if any + Property changes on: head/en_US.ISO8859-1/htdocs/news/status/report-sample.md ___________________________________________________________________ Added: fbsd:nokeywords ## -0,0 +1 ## +yes \ No newline at end of property Index: head/en_US.ISO8859-1/htdocs/news/status/status.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/status.xml (revision 52318) +++ head/en_US.ISO8859-1/htdocs/news/status/status.xml (revision 52319) @@ -1,278 +1,279 @@ ]> &title; $FreeBSD$

Next Quarterly Status Report submissions (October, 2017 – September, 2018) due: October 31th, 2018

Submit your entries as Pull Requests from your fork of FreeBSD Quarterly Status Reports GitHub repo or submit them via e-mail to - quarterly@FreeBSD.org.

+ quarterly@FreeBSD.org, + using the Markdown template.

One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.

The &os; Development Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.

For more exact guidelines on how to write good status reports, please consult our recommendations.

Periodically, special status reports are prepared and published. One of those are the developer summit reports. Developer summits are places where developers meet in person to discuss issues related to the project. They are definitely worth attending if one is interested in making significant contributions to the Project and they are open to anybody!

These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given.

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001