On Sat, Aug 29, 2020, at 8:50 PM, Adam Weinberger wrote: > Just a disclaimer: I’m speaking for myself here, not on behalf of portmgr@. > Also please keep in mind that I am perpetually, pathologically optimistic. > >> On Aug 29, 2020, at 18:01, Warner Losh <i...@bsdimp.com> wrote: >> >> >> Basically, it draws the community back in, even if it's just small ways, >> rather than having them be a pure consumer giving nothing back. Make it easy >> to adopt a port, and we'll grow our base of labor. Make it easy to remove >> ports that no one can be bothered to adopt and we shrink our workload. And >> we'll spend our time on the things that we know net us at least one user who >> will pledge to keep it going. > > This is a serious issue that we’ve been dealing with for a long time. I’ve > advocated very strongly for a script that automatically notifies the > maintainer (+/- ports@?) when a port is marked BROKEN and/or DEPRECATED. > Community notification is always a good thing, and it opens the door for > objections and discussion. Nobody has written such a script, but I would be > thrilled to help deploy such a script if someone writes it.
In the meantime, FreshPorts has a 'Watch ports I maintain' report under 'Watch ports I maintain' re https://github.com/FreshPorts/freshports/issues/138 -- Dan Langille d...@langille.org _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
