Question about submitting a NEW FreeBSD port (process & review)

P

Pavlos87

Hi everyone,
We are preparing a new FreeBSD port for an open-source email service called FEATHER and would like to make sure we follow the correct and current process.

After reading the Porter's Handbook, I would like to clarify a few practical points with the community:
  1. For a new port, is the recommended approach still:
    • Bugzilla PR + git format-patch, or
    • a GitHub pull request to the ports repository?
  2. Who normally reviews and merges a new port?
    • a category maintainer,
    • any ports committer, or
    • only specific maintainers?
  3. Is a MAINTAINER required upfront when submitting a new port?
  4. If a new port PR sits unreviewed, what is the recommended way to get feedback (mailing list, specific list, or contact)?

Any guidance or pointers would be greatly appreciated.
Thank you!
 
1) Github pull requests are possible now, but might fall through the cracks, I suggest sticking to a Bugzilla PR.
2) a port committer
3) no, but it's certainly better to have someone responsible for the port, we have enough unmaintained ports as it is.
4) Send a ping to the freebsd-ports mailing list asking for a committer to have a look at it.
 
You must log in or register to reply here.
Back
Top