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?

Best regards,
Robin

On Thu, 17 Oct 2024 03:45:33 +0300, Robin Haberkorn wrote:

> 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?

Assuming you are the maintainer, you submit a bug on Bugzilla as per:

https://docs.freebsd.org/en/books/porters-handbook/upgrading/

--
Using UNIX since v6 (1975)...

Use the BIG mirror service in the UK:
http://www.mirrorservice.org

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:
>
> https://docs.freebsd.org/en/books/porters-handbook/upgrading/
>
Isn't that what I've done? I did read the handbook. Is there anything I
missed, perhaps?

- Robin

On Thu, 17 Oct 2024 13:13:41 +0300, Robin Haberkorn wrote:

Hi Robin,

> 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:
>>
>> https://docs.freebsd.org/en/books/porters-handbook/upgrading/
>>
> Isn't that what I've done? I did read the handbook. Is there anything I
> missed, perhaps?

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?

--
To health and anarchy

On Thu, 17 Oct 2024, Alastair Hogge wrote:

> 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?
>
There seems to be some movement in the ticket now, so let's see whether
this helped.
Apparently, the right people are hanging out on
comp.unix.bsd.freebsd.misc. ;-)

If nothing helps, I will try reviews.freebsd.org.

Best regards,
Robin

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.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?
>>
> There seems to be some movement in the ticket now, so let's see whether
> 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.

--
To health and anarchy

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?

Best regards,
Robin

Robin Haberkorn <robin.haberkorn@googlemail.com> wrote:
> 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.

The FreeBSD Project hosts its own Git repositories.

>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?

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@.

Philip

Alastair Hogge <agh@riseup.net> wrote:
> 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.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?
>>>
>> There seems to be some movement in the ticket now, so let's see whether
>> 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...

For what it's worth: I still run a hack to forward posts to announce@ to
comp.unix.bsd.freebsd.announce.

Gmane also still exists. A bit.

>sadly gone now, and now, even mailing lists are being replaced by shit
>like Github, and even Matrix has entered the picture.

The optimist's view is that a lot of the noise that made Usenet and
mailing lists less productive since September 1993 has now moved
elsewhere. You don't have to follow GitHub. And I'm not even going to
look up what Matrix is. :-)

Philip

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@?

Robin Haberkorn <robin.haberkorn@googlemail.com> wrote:
> 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. :)

Philip

On Tue, 29 Oct 2024, Philip Paeps wrote:
>
> Unless you're fixing a driver. :)
>
I am trying to add TTY devices to linsysfs. So, yes, it's a driver.