FreeBSD maintains a GitHub presence, with the FreeBSD GitHub Organisation, its repositories, svn2git integration and mirroring managed by GitAdmin.

For repositories where pull requests (PRs) are not officially accepted:

• some Project members may process requests
• the recommended method for submitting changes is via Bugzilla.

Secondary mirrors of doc, ports, and src trees:

• freebsd-doc — FreeBSD Documentation Project (FDP)
  • pull requests are accepted
  • no guidelines/policy for PRs
• freebsd-ports — the ports collection
  • pull requests are subject to the whims of developers
  • better follow the guidelines for contributing to ports
• freebsd-src — FreeBSD base
  • pull requests are preferred for relatively straightforward changes, where the contributor already has a GitHub account
  • guidelines for contributors were introduced in February 2023 (history).

Ports-specific projects and teams:

• freebsd-ports-gnome — GNOME
• freebsd-ports-kde — QT & KDE.

Primary repositories — issues and pull requests welcome — for other well-known projects include:

• drm-kmod — the DRM drivers ported from Linux to FreeBSD using LinuxKPI
• pkg — a binary package manager for FreeBSD
• portmaster — port management script without external databases or languages
• poudriere — port/package build and test system.

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, in almost all cases, only those with @FreeBSD.org accounts are approved. 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 FreeBSD repository other than src, ports, and doc that is hosted within the organisation account.

<<anchor(pr)» <<anchor(prs)»

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.

There are webhooks configured on some FreeBSD Organisation repositories. This section details who configured them and what they're in use for. All external configurations or integrations should be listed here.

• IRC Messages for commit events:
  • Endpoint: n.tkte.ch Purpose: IRC (freenode) commit events
  • Repositories: freebsd-src, freebsd-ports, freebsd-doc
  • Contact: KubilayKocak

• Discord Messages for commit events:
  • Endpoint: dev.wired.sh Purpose: Discord commit events
  • Repositories: freebsd-src, freebsd-ports, freebsd-doc
  • Contact: KubilayKocak LewisCook

• For general questions, email Git Admin
• For change requests (new repositories, permissions, etc), please create an issue in Bugzilla -- Services:Git Integration