FreeBSD maintains a GitHub presence, with the FreeBSD GitHub Organisation, its repositories, svn2git integration and mirroring managed by Git Admin (team)
For general questions please email Git Admin <git-admin AT FreeBSD DOT org>
For change requests (new repositories, permissions, etc), please create an issue in Bugzilla -- Services:Git Integration
FreeBSD provides GitHub mirrors all project SVN repositories:
While Pull Requests are not officially accepted, but some project members do sometimes process/close them manually. The recommended method for submitting changes is via Bugzilla.
There are also working repositories for some Ports-specific projects and teams:
A number of well-known FreeBSD software projects maintain their primary repositories there as well:
Issues and Pull Requests are enabled and welcome.
Requests to be added to the FreeBSD GitHub Organisation can be made via Bugzilla (Product: Services, Component: Git Integration). Please include details of any teams you are a member of or hats you wear so that this can be reflected in GitHub.
Currently, only those with @FreeBSD.org accounts are approved in almost all cases. External users may apply to be a part of the organisation if a compelling case can be made. Examples may be external contributors that require write (commit) access to a non-FreeBSD (src, ports, doc) repository that is hosted within the organisation account.
Pull requests submitted to GitHub are an experimental feature of the project. While efforts are made to resolve them, the project's normal work flow documented in the FreeBSD Handbook is more reliable. Pull requests that include source code ready to go into the tree, or only need light editing to resolve conflicts or other trivial issues will be merged. Pull requests that require consensus building, discussion and or rework will be closed and redirected into the project's normal work flow. Pull requests may require maintainer approval before being merged, which we'll try to facilitate. Since this is an experimental service of the project, if you don't receive timely resolution via this means, please consider using the project's mailing lists, contacting maintainers directly, Bugzilla, Phabricator, etc to speed resolution.