Assuming you are the maintainer, you submit a bug on Bugzilla as per:
https://docs.freebsd.org/en/books/porters-handbook/upgrading/
Dear FreeBSD users,
I have created a FreeBSD port of my text editor SciTECO and would like
to get it upstreamed:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276492
Who is responsible for taking this kind of decision?
Hello Bob,
nice to see you are on Usenet as well.
On Thu, 17 Oct 2024, Bob Eager wrote:
Assuming you are the maintainer, you submit a bug on Bugzilla as per:Isn't that what I've done? I did read the handbook. Is there anything I missed, perhaps?
https://docs.freebsd.org/en/books/porters-handbook/upgrading/
Have you tried asking for a review on the freebsd-ports@freebsd.org
mailing list? You might also get more attention using reviews.freebsd.org
for new Ports, it is extra work, tho, the added exposure across platforms
may be of some benefit?
On Thu, 17 Oct 2024, Alastair Hogge wrote:
Have you tried asking for a review on the freebsd-ports@freebsd.orgThere seems to be some movement in the ticket now, so let's see whether
mailing list? You might also get more attention using
reviews.freebsd.org for new Ports, it is extra work, tho, the added
exposure across platforms may be of some benefit?
this helped.
Apparently, the right people are hanging out on
comp.unix.bsd.freebsd.misc. ;-)
You should have been here when loads of the official mailing lists where synchronised here on Usenet, good times...sadly gone now, and now, even mailing lists are being replaced by shit like Github, and even Matrix has entered the picture.
On Sat, 19 Oct 2024, Alastair Hogge wrote:
You should have been here when loads of the official mailing lists
where synchronised here on Usenet, good times...sadly gone now, and
now, even mailing lists are being replaced by shit like Github, and
even Matrix has entered the picture.
Github doesn't really get accepted in the FreeBSD communit it seems.
By the way, I am about to patch the kernel to get a job interview with
some company. While the docs say, you can try submitting a PR on
freebsd-src via Github, I was recommened to use reviews.freebsd.org.
That's the way to go?
On Thu, 17 Oct 2024 14:27:51 +0300, Robin Haberkorn wrote:
On Thu, 17 Oct 2024, Alastair Hogge wrote:
Have you tried asking for a review on the freebsd-ports@freebsd.orgThere seems to be some movement in the ticket now, so let's see whether
mailing list? You might also get more attention using
reviews.freebsd.org for new Ports, it is extra work, tho, the added
exposure across platforms may be of some benefit?
this helped.
Apparently, the right people are hanging out on
comp.unix.bsd.freebsd.misc. ;-)
You should have been here when loads of the official mailing lists where synchronised here on Usenet, good times...
sadly gone now, and now, even mailing lists are being replaced by shit
like Github, and even Matrix has entered the picture.
Yes. And put a pointer to your review in bugs.freebsd.org if you're
fixing a bug. Discussing changes on mailing lists is also encouraged. hackers@ and current@ are often good places to start. arch@ may be appropriate for broader architectural changes, but probably best to
start with hackers@.
On Mon, 28 Oct 2024, Philip Paeps wrote:
Yes. And put a pointer to your review in bugs.freebsd.org if you're
fixing a bug. Discussing changes on mailing lists is also encouraged.
hackers@ and current@ are often good places to start. arch@ may be
appropriate for broader architectural changes, but probably best to
start with hackers@.
You would prefer hackers@ over drivers@?
Unless you're fixing a driver. :)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 43:30:43 |
Calls: | 8,141 |
Calls today: | 4 |
Files: | 13,085 |
Messages: | 5,857,951 |