new ports and maintainer

[Eric Gallager]

A compromise here could be, instead of getting rid of openmaintainer
entirely, or keeping it opt-in like it currently is, we could make it
opt-out instead. There are two ways we could do this:

1. When committing new ports submitted by users without commit access, make
it a policy to automatically add "openmaintainer" for them unless they
specifically request otherwise,
or:
2. Get rid of the openmaintainer pseudo-maintainername entirely, and
replace it with a new pseudo-maintainername that would be equivalent to
what is currently signified by leaving out the "openmaintainer"
pseudo-maintainername. I am not sure what we would call this replacement
though...


On Thu, Jul 24, 2014 at 3:13 PM, Daniel J. Luke <dluke at geeklair.net> wrote:

> On Jul 24, 2014, at 2:37 PM, Sean Farley <sean at macports.org> wrote:
> >
> > Why not drop 'openmaintainer' and amend the community policy to have
> > every port be what we now call 'openmaintainer'? Furthermore, we could
> > set up a way for the listed port authors to be emailed when a port with
> > their name on it has changed.
>
> I, for one, appreciate the ability to specify which ports I don't care if
> people apply patches to vs. ports where I'm very careful about
> updating/keeping things from breaking.
>
> Ultimately, I'm not willing to provide active support for something that
> lots of other people are going to (potentially) be updating (and, in
> general, I prefer to get prior notice of a possible change before it hits
> the repo).
>
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
>
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140724/dfc9b0ce/attachment.html>