Source string Read only

(itstool) path: section/title
22/220
Context English State
The Standards hat is responsible for ensuring that FreeBSD complies with the standards it is committed to , keeping up to date on the development of these standards and notifying FreeBSD developers of important changes that allows them to take a proactive role and decrease the time between a standards update and FreeBSD's compliancy.
Hat currently held by: Garrett Wollman <email>wollman@FreeBSD.org</email>.
Core Secretary
The Core Secretary's main responsibility is to write drafts to and publish the final Core Reports. The secretary also keeps the core agenda, thus ensuring that no balls are dropped unresolved.
Hat currently held by: Muhammad Moinur Rahman <email>bofh@FreeBSD.org</email>.
Bugmeister
The Bugmeister is responsible for ensuring that the maintenance database is in working order, that the entries are correctly categorised and that there are no invalid entries. They supervise bugbusters.
Hat currently held by: the Bugmeister Team <email>bugmeister@FreeBSD.org</email>.
Donations Liaison Officer
The task of the donations liaison officer is to match the developers with needs with people or organisations willing to make a donation.
Hat held by: the Donations Liaison Office <email>donations@FreeBSD.org</email>. The <link xlink:href="https://www.freebsd.org/donations/"> Donations Liaison Charter</link>.
Admin
(Also called <quote>FreeBSD Cluster Admin</quote>)
The admin team consists of the people responsible for administrating the computers that the project relies on for its distributed work and communication to be synchronised. It consists mainly of those people who have physical access to the servers.
Hat held by: the Admin team <email>admin@FreeBSD.org</email>.
Process dependent hats
Report originator
The person originally responsible for filing a Problem Report.
Bugbuster
A person who will either find the right person to solve the problem, or close the PR if it is a duplicate or otherwise not an interesting one.
Mentor
A mentor is a committer who takes it upon them to introduce a new committer to the project, both in terms of ensuring the new committer's setup is valid, that the new committer knows the available tools required in their work, and that the new committer knows what is expected of them in terms of behavior.
Vendor
The person(s) or organisation whom external code comes from and whom patches are sent to.
Reviewers
People on the mailing list where the request for review is posted.
Processes
The following section will describe the defined project processes. Issues that are not handled by these processes happen on an ad-hoc basis based on what has been customary to do in similar cases.
Adding new and removing old committers
The Core team has the responsibility of giving and removing commit privileges to contributors. This can only be done through a vote on the core mailing list. The ports and documentation sub-projects can give commit privileges to people working on these projects, but have to date not removed such privileges.
Normally a contributor is recommended to core by a committer. For contributors or outsiders to contact core asking to be a committer is not well thought of and is usually rejected.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: section/title
Flags
read-only
Source string location
book.translate.xml:1365
String age
a year ago
Source string age
a year ago
Translation file
books/dev-model.pot, string 216