> On Jul 21, 2026, at 15:08, Stanciuc Paul Marius <[email protected]> > wrote: > > 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. > From the Porter's Handbook, we understand that Bugzilla is used for > submitting new ports. However, I would like to clarify a couple of points: > • 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? > • 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? > • 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 >
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
signature.asc
Description: Message signed with OpenPGP
