svn commit: r50198 - head/en_US.ISO8859-1/htdocs/news/status
Benjamin Kaduk <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.cvs.doc |
|---|---|
| Message-ID | <[email protected]> |
Author: bjk
Date: Sun Apr 23 04:32:20 2017
New Revision: 50198
URL: https://svnweb.freebsd.org/changeset/doc/50198
Log:
Add 2017Q1 core entry from matthew
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml Sun Apr 23 03:19:08 2017 (r50197)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml Sun Apr 23 04:32:20 2017 (r50198)
@@ -1184,4 +1184,99 @@
<tt>bhyve</tt> and attached to an RBD image.</task>
</help>
</project>
+
+ <project cat='team'>
+ <title>The &os; Core Team</title>
+
+ <contact>
+ <person>
+ <name>&os; Core Team</name>
+ <email>[email protected]</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>Core's primary function is to ensure the long-term viability of
+ the &os; project. A very large part of that is to ensure that the
+ interactions between developers remain cordial, and consequently
+ that the project appears welcoming to newcomers.</p>
+
+ <p>Normally, most of Core's activities around this are done in
+ private -- a quiet word in the right ear, some discrete
+ peacemaking, occasional reading of the riot act. Most of the time,
+ this is all that is necessary.</p>
+
+ <p>Unfortunately, this quarter we had an instance where such private
+ measures failed to achieve the desired result, and we ended up
+ ejecting a developer. John Marino is an extremely talented
+ programmer and has made significant contributions to the Ports
+ Collection. Despite this, portmgr found him to be
+ sufficiently disruptive and abrasive that in their judgement,
+ the project was better off overall to sever his connection to
+ itself, and core backed them up in that. We are sorry that
+ events came to this sad conclusion, but we remain convinced
+ that this was a necessary step to safeguard the character of
+ our community.</p>
+
+ <p>In a more positive light, Core has been working on a proposal
+ to recognise notable contributors to the &os; project who are not
+ (or perhaps <i>not yet</i>) suitable to be put forward as new
+ committers. In addition to the usual routes of recognising people
+ that write numbers of good bug reports or that supply patches or
+ that volunteer to maintain ports, this will also allow recognition
+ of people who contribute by such things as organising &os; events
+ or who promote &os; through social media. A formal announcement
+ of Core's proposal is imminent.</p>
+
+ <p>During January, the core secretary held an exercise to contact
+ all source committers who had been inactive for more than 18
+ months and persuade them to hand in their commit bits if they
+ weren't planning to resume working on &os; in the near future.
+ This is meant to be a routine function -- the "grim reaper" --
+ that aims to keep the list of people with the ability to commit
+ pretty much in synchrony with the list of people that are actively
+ committing. The regular process had fallen out of activity
+ several years ago, and we needed to clear the decks before
+ restarting. Ultimately, this resulted in some 20
+ developers-emeritus handing in their commit bits.</p>
+
+ <p>No new commit bits were awarded during this quarter.</p>
+
+ <p>Core is also taking soundings on producing a 10.4-RELEASE.
+ This is not in the current plan, but a number of developers and
+ important &os; users would be keen to see it happen, given some of
+ the work that has gone into the stable/10 branch since
+ 10.3-RELEASE. On the other hand, this would require an additional
+ support burden for SecTeam, including maintaining versions of
+ software that have been declared obsolete upstream, in particular
+ OpenSSL. As an even-numbered release, 10.4-RELEASE would have a
+ "normal" rather than an "extended" lifetime which means it should
+ not result in extending the support lifetime of the stable/10
+ branch.</p>
+
+ <p>In other news, Core arranged for the old and largely inactive
+ [email protected] mailing list to be wound up, and for any
+ remaining activities to be transferred to the &os; Foundation.</p>
+
+ <p>Core also asked clusteradm to turn off Internet-wide access to
+ the <tt>finger</tt> server on freefall.freebsd.org. Many
+ developers have included details such as phone numbers into
+ the GECOS field of their &os; password database entries, and
+ these would be revealed by the <tt>finger</tt> server --
+ details which are nowadays generally felt inadvisable to
+ expose publicly. <tt>finger</tt> is still available
+ internally within freefall.freebsd.org. Core recommends that
+ GECOS data is limited to just your full name, and we have
+ updated the standard "new committer" e-mail template
+ to reflect that.</p>
+
+ <p>Core is looking for new volunteers to help out with several of
+ the teams that manage various aspects of the project. In
+ particular, Postmaster and SecTeam are in need of new blood.
+ Recruiting a new member of SecTeam is well underway, but anyone
+ interested in joining any of the teams is encouraged to make
+ themselves known either to Core, or directly to the teams
+ concerned.</p>
+ </body>
+ </project>
</report>
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"