Re: Question about submitting a new FreeBSD port for review

--Apple-Mail=_979F6F89-A3A0-4C9F-BAD1-2D606F8C2905
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jul 21, 2026, at 15:08, Stanciuc Paul Marius =
<[email protected]> wrote:
>=20
> Hello FreeBSD Ports team,
> We are working on preparing a new port for the FEATHER project and =
would like to confirm the recommended submission workflow before =
proceeding.
> =46rom the Porter's Handbook, we understand that Bugzilla is used for =
submitting new ports. However, I would like to clarify a couple of =
points:
>     =E2=80=A2 Is opening a Bugzilla issue with a link to the port =
repository sufficient for review, or is it expected that the submission =
also includes a patch/diff against the current Ports tree?
>     =E2=80=A2 If a Bugzilla submission is the correct approach, is =
there anything else you would recommend including to help a ports =
committer review and integrate the new port?
>     =E2=80=A2 Is there any preferred way to request a review from a =
ports committer once the Bugzilla submission is ready?
> We would like to follow the preferred FreeBSD contribution workflow =
and make the review process as straightforward as possible.
> Thank you for your time and guidance.
> Best regards,
> Paul Stanciuc
>=20

Hi,

There are two paths available here:

1. Phabricator(https://reviews.freebsd.org =
<https://reviews.freebsd.org/>)

If you are unsure what you are doing and want someone to review your =
codes line
by line this is the better approach. I would at least recommend this if =
this is
the first time you are submitting a patch. This will help you understand =
how
the porting works. Create a account and send a mail to
[email protected] <mailto:[email protected]> notifying =
your intent to use it. Once approved submit
the patch.

2. Bugzilla(https://bugs.freebsd.org <https://bugs.freebsd.org/>)
If you are confident on what you are doing and have tested this on =
multiple
different versions and absolutely confident that the patch is what it is =
follow
this:
a. Create a bug report
b. Do not attach any patches
c. Mark the bug report number
d. Create the port in your local working branch do poudriere test and =
portlint
e. Create a commit. In the commit message add necessary git markers =
specially
   the markers like `PR: <BUG NUMBER>` and `Approved by: maintainer is =
submitter`
f. Create a git formatted patch out of the commmit
g. Attach the patch to the bug report
h. And wait for someone to commit

I hope this clears the confusion.

Kind regards,
Moin



--Apple-Mail=_979F6F89-A3A0-4C9F-BAD1-2D606F8C2905
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmpfcfBfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE
Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA
vJH1Nw//Wh7+umF5uS4hBZsG0/4PNNjt644Rpb8v304LA5SZLm6vpgQKpgch9RJp
T76qB5hlM4f/0C1+XYOYzEgroqH9vbaXq/CYrLMvLt2PoYolY7afw8p+VwDWa451
8Pjg8nkedE/wbjax81kHDPl8CTH6+t3V0bV3AnjtddFSN/g8uhbBhlliCBPGFAWj
vwH6dwyC/B7eTNSh8tE2l8xsVc98TJfdvqzNNWG0Zph2ZklyD92Rwol2sGwNxwy7
7i3APh81CO+/MtlKuj1G4gGeT+ZLFDDxwB7d1a8vK8gA0z7FM4WYr7KymL3X0fuq
Z9ChHSoqE6GQZJ52cWC9qb3NsE2WGJAOSk/CIkZluTAU5CQbRbHsAJb0UIC70vh7
eEpfu8BahDHqf3CNf/GNvg4EGIL8sLiah+1GYTMzRjQmbaw7LojSVHlT1+/dbGzR
zj4FL080S+U6uCLbt+0IWPB7vKVRIeyTnG4pvLiCTWfqCbcle0B3LQ6s5XVneDlL
2rAHkBD/L9X2XJSNsALDyDiUIfMedROhl5CSvx31GtP3j7gE/AOdVyCxLHBV2ksU
IZyLLMPPWcJICieWVR1mIvOpTsFB9Wk0o70J8NSe1TmBGjrTvS1GaNdtH34kvkEg
szAqcid3nkYWb6EsljXo+UZNQErLN2scyypCnXeptuj5MWzI6G0=
=LIyd
-----END PGP SIGNATURE-----

--Apple-Mail=_979F6F89-A3A0-4C9F-BAD1-2D606F8C2905--