From Newsgroup: muc.lists.freebsd.ports
From: Hannes Hauswedell <
h2+lists2026@fsfe.org>
To: "freebsd-ports"<
freebsd-ports@freebsd.org>
Date: Fri, 18 Sep 2026 10:00:23 +0200
Subject: [new port] www/jotty-page
Hello folks,
what's the process nowadays for getting a new port committed?
* I opened a PR in May: https://github.com/freebsd/freebsd-ports/pull/525/
* I have since updated it several times to keep track of new versions.
* I opened a bugzilla issue in July: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297122
* No response anywhere so far.
Thank you for your help with this!
Hello Hannes,
sorry, that it went this way! We obviously have some issues with contributions that are not triaged to a single person but remain on the pile and then become part of the backlog due to new stuff coming in. I have seen quite a few cases of that over the last months.
In general we are a lot better at triaging stuff which is already part of the portstree because there is at least a maintainer for it and more committers are looking for exactly that kind of work in bugzilla.
Well nothing of that should be your problem. I just write it because other committers might read it and I think we need to fix our workflows to bring more attention to this kind of PRs.
So going forward I have taken your bugzilla PR and closed the github PR because it's easier to work with (at least for us (me)). I also had a quick look at the patch and it doesn't look too scary even though it's nodejs. It might take a bit
for me to review it in more detail and push it through my pipeline but I'll keep
you informed in the PR.
So thanks for your contribution and sorry that it has gone this wrong!
--
Bernhard Froehlich
https://www.bluelife.at/
--
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