On 2019/05/11 16:22, Ingo Schwarze wrote: > Hi Matthew, > > cho...@jtan.com wrote on Sat, May 11, 2019 at 04:18:07PM +0300: > > > The question remains but now with a wider audience - > > I've posted a port to the mailing list, what next? > > Wait for feedback. > > > I'm happy to leave it in the porters' collective lap or begin > > to take on some responsibility myself; I'm just not sure what > > to do with it. > > Any of the following may happen next: > > a) A ports developer decides the port is useful and mature > and commits it, with or without minor changes. > > b) Somebody thinks it is potentially useful but requires > more work. That person will ask you to do specific work > on it and resubmit once you have done that. > > c) You get no feedback whatsoever. > > d) A ports developer decides the software is inappropriate > for the ports tree for some reason and explicitely says so. > > The outcome d) is relatively rare. For you, c) is the least > desirable outcome, and it is *not* rare. It is undesirable > because you won't know the reason: > > ca) Maybe nobody really noticed the submission, it simply fell > through the cracks. It might still be a very good port. > > cb) Maybe some noticed, but weren't interested personally > and had other things to do. It might still become a port > if somebody becomes interested. > > cc) Maybe most who noticed considered it a dubious idea, > but didn't care enough to explicitly oppose it. > In case somebody finally picks it up, explicit opposition > might start being discussed, but that's rare (just like d). > > Remeber that testing and committing a port requires time and > effort, and more ports are being submitted than porters have > time to deal with. Even short feedback requires spending some > time. > > Personally, i'm in the cb) camp in this case, but that really > doesn't tell you anything useful.
For me it's mostly cb) mixed with a little concern that it might bring extra work to do in the future when handling an update to perl (which usually already involve a fair bit of work across the ports tree). or due to changes in the base OS. Especially so if other ports start depending on this. For a port which is somewhat closely tied to OpenBSD base, I'm really a lot happier if it has a maintainer who is reasonably likely to stick around and help with updates in future..
