From Newsgroup: muc.lists.freebsd.ports
------=_Part_836094_93834601.1765820820976
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hello,
I am preparing a new FreeBSD port for an open-source email service (FEATHER) and would like to ensure we follow the correct process.
After reviewing the Porter's Handbook, I would appreciate clarification on the following:
-
For a new port, is the preferred submission method:
-
a Bugzilla PR with a git format-patch, or
-
a GitHub pull request to the ports repository?
-
Who typically reviews and merges new ports?
-
category maintainer,
-
any ports committer, or
-
specific maintainers?
-
Is a MAINTAINER required at submission time?
-
If a new port PR remains unreviewed, what is the recommended way to follow up?
Any guidance would be very helpful.
Thank you for your time.
Best regards,
Paul
------=_Part_836094_93834601.1765820820976
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html><head></head><body><div class="yahoo-style-wrap" style="font-family:verdana, helvetica, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div><p data-start="3075" data-end="3083">Hello,</p>
<p data-start="3090" data-end="3228">I am preparing a <strong data-start="3107" data-end="3127">new FreeBSD port</strong> for an open-source email service (FEATHER) and would like to ensure we follow the correct process.</p>
<p data-start="3235" data-end="3324">After reviewing the Porter's Handbook, I would appreciate clarification on the following:</p>
<ul data-start="3331" data-end="3786">
<li data-start="3331" data-end="3497">
<p data-start="3333" data-end="3388">For a <strong data-start="3339" data-end="3351">new port</strong>, is the preferred submission method:</p>
<ul data-start="3393" data-end="3497">
<li data-start="3393" data-end="3440">
<p data-start="3395" data-end="3440">a Bugzilla PR with a <code data-start="3416" data-end="3434">git format-patch</code>, or</p>
</li>
<li data-start="3445" data-end="3493">
<p data-start="3447" data-end="3493">a GitHub pull request to the ports repository?</p>
</li>
</ul>
</li>
<li data-start="3500" data-end="3642">
<p data-start="3502" data-end="3549">Who typically <strong data-start="3516" data-end="3538">reviews and merges</strong> new ports?</p>
<ul data-start="3554" data-end="3642">
<li data-start="3554" data-end="3578">
<p data-start="3556" data-end="3578">category maintainer,</p>
</li>
<li data-start="3583" data-end="3610">
<p data-start="3585" data-end="3610">any ports committer, or</p>
</li>
<li data-start="3615" data-end="3638">
<p data-start="3617" data-end="3638">specific maintainers?</p>
</li>
</ul>
</li>
<li data-start="3645" data-end="3695">
<p data-start="3647" data-end="3695">Is a <strong data-start="3652" data-end="3666">MAINTAINER</strong> required at submission time?</p>
</li>
<li data-start="3702" data-end="3782">
<p data-start="3704" data-end="3782">If a new port PR remains unreviewed, what is the recommended way to follow up?</p>
</li>
</ul>
<p data-start="3789" data-end="3853">Any guidance would be very helpful.<br data-start="3824" data-end="3827">
Thank you for your time.</p>
<p data-start="3860" data-end="3882">Best regards,<br data-start="3873" data-end="3876">
Paul</p></div><br></div></div></body></html> ------=_Part_836094_93834601.1765820820976--
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to
news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2