Re: Question about submitting a new FreeBSD port for review

Den 2026-07-21 kl. 15:19, skrev Moin Rahman:
>
>> 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
>
>
Hi and thank you,

I did not know about phabricator until I read your email so I have added 
my attempts to port software to FreeBSD in Bugzilla (following the 
handbook).

Are the two paths mutually exclusive?

I am asking since I have noticed that it's kind of difficult to get 
feedback for attempts to create ports. I guess no one has the time to 
look at my feeble and probably horrid attempts to port.

Could I/Should I ask that the PRs in Bugzilla should be closed and 
revert to phabricator?

These are my feeble and horrid attempts:

March 17 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293877

April 14 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294521

July 8 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296618

Best regards

Roger