• Does the new policy allow an "overloaded" committer to add ports that will be maintained by others?

    From Yuri@yuri@FreeBSD.org to muc.lists.freebsd.ports on Wed Sep 23 14:00:55 2026
    From Newsgroup: muc.lists.freebsd.ports

    It says "While a maintainer is overloaded, taking on additional ports [skipped]".

    My reading is that yes, so-called "overloaded" maintainers are allowed
    to add ports as long as the MAINTAINER has someone else.

    Is my reading correct?



    Thanks,

    Yuri




    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Moin Rahman@bofh@freebsd.org to muc.lists.freebsd.ports on Thu Sep 24 00:10:16 2026
    From Newsgroup: muc.lists.freebsd.ports


    On Sep 23, 2026, at 23:00, Yuri <yuri@FreeBSD.org> wrote:

    It says "While a maintainer is overloaded, taking on additional ports [skipped]".

    My reading is that yes, so-called "overloaded" maintainers are allowed to add ports as long as the MAINTAINER has someone else.

    Is my reading correct?



    Thanks,

    Yuri



    Is the MAINTAINER a committer or an external contributor?
    Kind regards,
    Moin--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Robert Clausecker@fuz@freebsd.org to muc.lists.freebsd.ports on Wed Sep 23 23:29:01 2026
    From Newsgroup: muc.lists.freebsd.ports

    Hi Yuri,

    The intent of the policy is that this is allowed and even encouraged,
    if the maintainer then actually ends up maintaining the port. You are
    not allowed to use someone else as a strawman to fill in the committer
    field while you do all the work ("anti-gaming rule").

    It is up to portmgr (in your case represented by bapt) to make a
    decision for each individual case.

    Yours,
    Robert clausecker

    On Wed, Sep 23, 2026 at 02:00:55PM -0700, Yuri wrote:
    It says "While a maintainer is overloaded, taking on additional ports [skipped]".

    My reading is that yes, so-called "overloaded" maintainers are allowed to
    add ports as long as the MAINTAINER has someone else.

    Is my reading correct?



    Thanks,

    Yuri



    --
    () ascii ribbon campaign - for an encoding-agnostic world
    /\ - against html email - against proprietary attachments


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Yuri@yuri@FreeBSD.org to muc.lists.freebsd.ports on Wed Sep 23 22:20:53 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 9/23/26 15:10, Moin Rahman wrote:
    Is the MAINTAINER a committer or an external contributor?


    It's an external maintainer who currently maintains only 5 ports.


    Yuri




    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Yuri@yuri@FreeBSD.org to muc.lists.freebsd.ports on Wed Sep 23 22:24:01 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 9/23/26 16:29, Robert Clausecker wrote:
    The intent of the policy is that this is allowed and even encouraged,
    if the maintainer then actually ends up maintaining the port. You are
    not allowed to use someone else as a strawman to fill in the committer
    field while you do all the work ("anti-gaming rule").

    It is up to portmgr (in your case represented by bapt) to make a
    decision for each individual case.


    No, there are no strawmen. He submitted this port and it is needed. I've
    never heard of him or talked to him.



    Yuri




    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2