On Sat, 11 May 2019 at 05:36, <cho...@jtan.com> wrote: > [including ports@] > > Theo de Raadt writes: > > cho...@jtan.com wrote: > > > > > I recently posted a new CPAN module to ports@ which wraps pledge and > > > unveil. There was a bit of a balls up because as a sysadmin I'm not > > > really used to group development and what I've done has usually been in > > > a corporate environment but in the end a complete tarball was posted. > > > > Well -- I do not make decisions in the ports environment. > > > > Other people lead that effort, and make decisions after weighing the > > benefits and potential costs. > > The question ultimately is how to I know if I'm completely finished with > providing this port? > > If I need to do something more or promise on-going maintenance to get > this minor port included in the big picture, that is to say: in > OpenBSD's public CVS repository, then I'm happy to get it done. If it's > enough to send in a tarball (as I've done already) and let the current > ports maintainers take over then I'm (more than) happy to do that. > > Is "send a tarball to ports@ and forget about it" enough?
You should consider becoming part of the process, one of the most valuable currencies you can give to the project is a degree of continuity. To phrase it differently, “fire and forget” is rarely a sustainable approach. Kind regards, Job
