• There are 593 ports pending to be commited, disaster

    From Simeo Reig@reig.simeo@gmail.com to muc.lists.freebsd.ports on Mon Oct 19 18:58:12 2026
    From Newsgroup: muc.lists.freebsd.ports

    --000000000000eea249065e346c96
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    A month ago, I decided to upload a new port after years of not doing so. It=E2=80=99s been open for 30 days and absolutely nothing has happened. Tha= t=E2=80=99s not
    really the problem, though=E2=80=94the port isn=E2=80=99t anything special.=
    Just a small
    Perl wrapper for some mojo stuff. The problem is that when I look at
    Bugzilla, there are 590 ports waiting to be committed <https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=3DOpen&limit=3D0&= list_id=3D996712&order=3Dchangeddate%20DESC%2Cpriority%2Cbug_severity&produ= ct=3DPorts%20%26%20Packages&query_format=3Dadvanced>,
    some of which are 10 years old! It=E2=80=99s all very concerning=E2=80=94it=
    doesn=E2=80=99t bode
    well for FreeBSD.

    Best regards, the last one to turn off the lights

    Sime=C3=B3 Reig

    --000000000000eea249065e346c96
    Content-Type: text/html; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    <div dir=3D"ltr"><div></div><div>A month ago, I decided to upload a new por=
    t after years of not doing so. It=E2=80=99s been open for 30 days and absol= utely nothing has happened. That=E2=80=99s not really the problem, though= =E2=80=94the port isn=E2=80=99t anything special. Just a small Perl wrapper=
    for some mojo stuff. The problem is that when I look at Bugzilla, there ar=
    e <a href=3D"https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=3DOpe= n&amp;limit=3D0&amp;list_id=3D996712&amp;order=3Dchangeddate%20DESC%2Cprior= ity%2Cbug_severity&amp;product=3DPorts%20%26%20Packages&amp;query_format=3D= advanced">590 ports waiting to be committed</a>, some of which are 10 years=
    old! It=E2=80=99s all very concerning=E2=80=94it doesn=E2=80=99t bode well=
    for FreeBSD.<br><br>Best regards, the last one to turn off the lights<br><= br></div><div>Sime=C3=B3 Reig</div><div><br><br><br><br></div><div><br></di= v><div><br></div></div>

    --000000000000eea249065e346c96--


    --
    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
  • From Bernhard Froehlich@decke@FreeBSD.org to muc.lists.freebsd.ports on Mon Oct 19 21:56:16 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_1299818_449944494.1792439776358
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    ---- Am Mon, 19 Oct 2026 18:58:12 +0200 mailto:reig.simeo@gmail.com schri=
    eb ----


    A month ago, I decided to upload a new port after years of not doing so. It= =E2=80=99s been open for 30 days and absolutely nothing has happened. That= =E2=80=99s not really the problem, though=E2=80=94the port isn=E2=80=99t an= ything special. Just a small Perl wrapper for some mojo stuff. The problem =
    is that when I look at Bugzilla, there are https://bugs.freebsd.org/bugzill= a/buglist.cgi?bug_status=3DOpen&limit=3D0&list_id=3D996712&order=3Dchangedd= ate%20DESC%2Cpriority%2Cbug_severity&product=3DPorts%20%26%20Packages&query= _format=3Dadvanced , some of which are 10 years old! It=E2=80=99s all very = concerning=E2=80=94it doesn=E2=80=99t bode well for FreeBSD.

    Best regards, the last one to turn off the lights


    Sime=C3=B3 Reig


    Thanks a lot for your motivating words of wisdom!


    Anyway your statistics are wrong. That 590 tickets in bugzilla are not 590 = ports to be committed but 590 bugs which are assigned and Open. Completely = useless number. Overall we currently close around 350 Ports PRs per week bu=
    t we have a backlog of around 2950 PRs.


    https://bugs.freebsd.org/bugzilla/page.cgi?id=3Ddashboard.html


    Feel free to help or at least stop wasting time with useless stats. ------=_Part_1299818_449944494.1792439776358
    Content-Type: text/html; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>= <meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h= ead><body ><div dir=3D'auto' style=3D'font-size:10pt;font-family:Verdana,Ar= ial,Helvetica,sans-serif;'><div id=3D"message" dir=3D"auto"><div dir=3D"aut=
    o" style=3D"font-size: 10pt; font-family: Verdana, Arial, Helvetica, sans-s= erif"><div id=3D"x_387284671message" dir=3D"auto"><div><br></div></div><div=
    id=3D"x_387284671content" dir=3D"auto"> ---- Am Mon, 19 Oct 2026 18:58:12 = +0200 <b> <a href=3D"mailto:reig.simeo@gmail.com" target=3D"_blank">reig.si= meo@gmail.com</a> schrieb </b> ----<br><br><blockquote style=3D"border: 0px=
    ; padding: 0px; margin: 0px"><div dir=3D"ltr"><div></div><div>A month ago, =
    I decided to upload a new port after years of not doing so. It=E2=80=99s be=
    en open for 30 days and absolutely nothing has happened. That=E2=80=99s not=
    really the problem, though=E2=80=94the port isn=E2=80=99t anything special=
    . Just a small Perl wrapper for some mojo stuff. The problem is that when I=
    look at Bugzilla, there are <a href=3D"https://bugs.freebsd.org/bugzilla/b= uglist.cgi?bug_status=3DOpen&amp;limit=3D0&amp;list_id=3D996712&amp;order= =3Dchangeddate%20DESC%2Cpriority%2Cbug_severity&amp;product=3DPorts%20%26%2= 0Packages&amp;query_format=3Dadvanced" target=3D"_blank">590 ports waiting =
    to be committed</a>, some of which are 10 years old! It=E2=80=99s all very = concerning=E2=80=94it doesn=E2=80=99t bode well for FreeBSD.<br><br>Best re= gards, the last one to turn off the lights<br><br></div><div>Sime=C3=B3 Rei= g</div><div dir=3D"auto"><br><br>Thanks a lot for your motivating words of = wisdom!</div><div dir=3D"auto"><br></div><div dir=3D"auto">Anyway your stat= istics are wrong. That 590 tickets in bugzilla are not 590 ports to be comm= itted but 590 bugs which are assigned and Open. Completely useless number. = Overall we currently close around 350 Ports PRs per week but we have a back= log of around 2950 PRs.</div><div dir=3D"auto"><br></div><div dir=3D"auto">= https://bugs.freebsd.org/bugzilla/page.cgi?id=3Ddashboard.html</div><div di= r=3D"auto"><br></div><div dir=3D"auto">Feel free to help or at least stop w= asting time with useless stats.</div><div><br></div><div><br></div></div> </blockquote></div></div></div><div id=3D"signature" dir=3D"auto"></div><di=
    v id=3D"content" dir=3D"auto"></div></div><br></body></html> ------=_Part_1299818_449944494.1792439776358--



    --
    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
  • From Bernhard Froehlich@decke@FreeBSD.org to muc.lists.freebsd.ports on Fri Oct 30 15:28:12 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_795625_2022713194.1793370492573
    Content-Type: text/plain; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    Hi Roger,



    I consider your question as serious interest so let me answer it in

    a serious way. You already know that we are quite understaffed

    as in "we're dealing with a portstree that has 35k ports and are

    getting flooded with new ports, updates, security issues besides

    the never ending improvements in the open source world".



    So the reality is that you are free to choose to help wherever you

    feel comfortable. Just to give you an idea of what I mean:



    Check the list of ports that are unmaintained and vulnerable:

    https://portstatus.bsdproject.de/maintainer/ports%40FreeBSD.org?f=3Dupdates= &sort=3Dcvss&dir=3Ddesc=20



    Try to update the ones that are simple and leaf ports (not used

    by any others) submit patches for them and if you feel especially

    interested in them adopt them as a maintainer.



    Then continue with just unmaintained and outdated ones:

    https://portstatus.bsdproject.de/maintainer/ports%40FreeBSD.org?f=3Dupdates= =20



    Or let's have a look a licensing. That's manual work but not hard

    one and we will need it to make progress with SBOMs:

    https://portslicense.freebsd.org/maintainers/ports@FreeBSD.org.html=20



    And then I'm pretty sure we all want to have a better "pkg audit"

    so let's populate CPE data to the ports. It's about as hard as

    checking licenses but there are about 1-2k ports to check manually:

    https://github.com/decke/chkcpe=20



    You like to port new stuff that we don't have in the portstree yet?

    https://wiki.freebsd.org/WantedPorts=20



    If you are here somewhere I'm pretty sure you got your commit

    bit already and found more dirty spots in the portstree yourself

    that keep you busy for years.



    Feel free to also join us on ports related IRC channels to see how

    we fight the dragon or just to get your questions answered. https://wiki.freebsd.org/IRC/Channels=20



    --

    Bernhard Froehlich

    https://www.bluelife.at/=20









    From: Roger Olofsson <raggen44@gmail.com>
    To: <freebsd-ports@FreeBSD.org>
    Date: Tue, 20 Oct 2026 11:53:16 +0200
    Subject: Re: There are 593 ports pending to be commited, disaster



    I think the best reply to the original
    email (Sime=C3=B3) is:



    How can I help?



    I have always liked the 3 layers of
    FreBSD with kernel, userland and ports. Complicating this would
    not be good.



    (I am long time FreeBSD user that
    decided to learn the process of porting software this year.
    Submitted my first in March which is in the tree (thank you
    decke), my second in April still waiting for final review and my
    third in july which was removed by upstream before review. I saw
    the backlog and had similar thoughts as Sime=C3=B3.)



    Greetings

    /Roger



    Den 2026-10-19 kl. 22:34, skrev Marek
    Zarychta:






    On 19.10.2026=C2=A0at 22:07, Daniel
    Engberg wrote:

    On 2026-10-19 21:56, Bernhard
    Froehlich wrote:




    ---- Am Mon, 19
    Oct 2026 18:58:12 +0200 mailto:reig.simeo@gmail.com sch= rieb ----

    =20

    =20

    A month ago, I decided to upload a new port
    after years of not doing so. It=E2=80=99s been open=
    for
    30 days and absolutely nothing has happened.
    That=E2=80=99s not really the problem, though=E2=80= =94the port
    isn=E2=80=99t anything special. Just a small Perl
    wrapper for some mojo stuff. The problem is that
    when I look at Bugzilla, there are https://bugs.fre= ebsd.org/bugzilla/buglist.cgi?bug_status=3DOpen&limit=3D0&list_id=3D996712&= order=3Dchangeddate%20DESC%2Cpriority%2Cbug_severity&product=3DPorts%20%26%= 20Packages&query_format=3Dadvanced , some of
    which are 10 years old! It=E2=80=99s all very
    concerning=E2=80=94it doesn=E2=80=99t bode well for=
    FreeBSD.
    =20
    Best regards, the last one to turn off the
    lights
    =20

    Sime=C3=B3 Reig



    Thanks a lot for your motivating words of
    wisdom!


    Anyway your statistics are wrong.
    That 590 tickets in bugzilla are not 590 ports
    to be committed but 590 bugs which are assigned
    and Open. Completely useless number. Overall we
    currently close around 350 Ports PRs per week
    but we have a backlog of around 2950 PRs.



    https://bugs.freebsd.org/bugzilla/page.cgi?id=3Ddashboard.html=20



    Feel free to help or at least stop
    wasting time with useless stats.










    I understand the frustration, unfortunately there are
    administrative/management issues regarding the ports tree
    affecting multiple areas including productivity and engagement
    which in turn also affects our ability to process PRs. On top of
    that most of us are volunteers with limited time, hardware etc.

    =20

    Best regards,

    Daniel=20


    With LLVM and the
    abundance of freely available software, the Ports Tree can
    grow rapidly. However, this raises questions about how we
    balance software availability with long-term maintainability.

    One issue worth reconsidering
    is the two-week maintainer timeout.=C2=A0For simple updates and
    minor fixes, the two-week timeout could be shortened, while
    more substantial changes would still receive adequate review.

    We should also consider
    whether every piece of software needs to be included in the
    official tree. Some ports serve only a narrow audience or
    duplicate existing functionality, yet still require resources
    to build and maintain. Evaluating the broader usefulness of
    new ports could help keep the collection manageable and
    sustainable.=C2=A0I maintain a few ports locally, but I
    doubt they would be useful to a sufficiently broad audience to
    justify their inclusion in the official tree, especially given
    the resources required to build and maintain them.

    The goal should not be to discourage
    contributions, but to ensure that the growth of the Ports Tree
    brings lasting value to the FreeBSD community.=C2=A0

    Cheers

    --=20
    Marek Zarychta
    ------=_Part_795625_2022713194.1793370492573
    Content-Type: text/html; charset="UTF-8"
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>= <meta content=3D"text/html;charset=3DUTF-8" http-equiv=3D"Content-Type"></h= ead><body ><div style=3D"font-family: Verdana, Arial, Helvetica, sans-serif=
    ; font-size: 10pt;"><div>Hi Roger,<br></div><div><br></div><div>I consider = your question as serious interest so let me answer it in<br></div><div>a se= rious way. You already know that we are quite understaffed<br></div><div>as=
    in "we're dealing with a portstree that has 35k ports and are<br></div><di= v>getting flooded with new ports, updates, security issues besides<br></div= ><div>the never ending improvements in the open source world".<br></div><di= v><br></div><div>So the reality is that you are free to choose to help wher= ever you<br></div><div>feel comfortable. Just to give you an idea of what I=
    mean:<br></div><div><br></div><div>Check the list of ports that are unmain= tained and vulnerable:<br></div><div><a target=3D"_blank" href=3D"https://p= ortstatus.bsdproject.de/maintainer/ports%40FreeBSD.org?f=3Dupdates&amp;sort= =3Dcvss&amp;dir=3Ddesc">https://portstatus.bsdproject.de/maintainer/ports%4= 0FreeBSD.org?f=3Dupdates&amp;sort=3Dcvss&amp;dir=3Ddesc</a><br></div><div><= br></div><div>Try to update the ones that are simple and leaf ports (not us= ed<br></div><div>by any others) submit patches for them and if you feel esp= ecially<br></div><div>interested in them adopt them as a maintainer.<br></d= iv><div><br></div><div>Then continue with just unmaintained and outdated on= es:<br></div><div><a target=3D"_blank" href=3D"https://portstatus.bsdprojec= t.de/maintainer/ports%40FreeBSD.org?f=3Dupdates">https://portstatus.bsdproj= ect.de/maintainer/ports%40FreeBSD.org?f=3Dupdates</a><br></div><div><br></d= iv><div>Or let's have a look a licensing. That's manual work but not hard<b= r></div><div>one and we will need it to make progress with SBOMs:<br></div>= <div><a target=3D"_blank" href=3D"https://portslicense.freebsd.org/maintain= ers/ports@FreeBSD.org.html">https://portslicense.freebsd.org/maintainers/po= rts@FreeBSD.org.html</a><br></div><div><br></div><div>And then I'm pretty s= ure we all want to have a better "pkg audit"<br></div><div>so let's populat=
    e CPE data to the ports. It's about as hard as<br></div><div>checking licen= ses but there are about 1-2k ports to check manually:<br></div><div><a targ= et=3D"_blank" href=3D"https://github.com/decke/chkcpe">https://github.com/d= ecke/chkcpe</a><br></div><div><br></div><div>You like to port new stuff tha=
    t we don't have in the portstree yet?<br></div><div><a target=3D"_blank" hr= ef=3D"https://wiki.freebsd.org/WantedPorts">https://wiki.freebsd.org/Wanted= Ports</a><br></div><div><br></div><div>If you are here somewhere I'm pretty=
    sure you got your commit<br></div><div>bit already and found more dirty sp= ots in the portstree yourself<br></div><div>that keep you busy for years.<b= r></div><div><br></div><div>Feel free to also join us on ports related IRC = channels to see how<br></div><div>we fight the dragon or just to get your q= uestions answered.</div><div><a target=3D"_blank" href=3D"https://wiki.free= bsd.org/IRC/Channels">https://wiki.freebsd.org/IRC/Channels</a><br></div><d= iv><br></div><div class=3D"zmail_signature_below"><div id=3D"Zm-_Id_-Sgn" d= ata-zbluepencil-ignore=3D"true" data-sigid=3D"2481435000000201011"><div>--<= br></div><div>Bernhard Froehlich<br></div><div><a target=3D"_blank" href=3D= "https://www.bluelife.at/">https://www.bluelife.at/</a><br></div></div></di= v><div><br></div><div class=3D"zmail_extra_hr" style=3D"border-top: 1px sol=
    id rgb(204, 204, 204); height: 0px; margin-top: 10px; margin-bottom: 10px; = line-height: 0px;"><br></div><div class=3D"zmail_extra" data-zbluepencil-ig= nore=3D"true"><div><br></div><div id=3D"Zm-_Id_-Sgn1">From: Roger Olofsson = &lt;raggen44@gmail.com&gt;<br>To: &lt;freebsd-ports@FreeBSD.org&gt;<br>Date=
    : Tue, 20 Oct 2026 11:53:16 +0200<br>Subject: Re: There are 593 ports pendi=
    ng to be commited, disaster<br></div><div><br></div><blockquote style=3D"ma= rgin: 0px;" id=3D"blockquote_zmail"><div><div class=3D"x_761045520moz-cite-= prefix">I think the best reply to the original
    email (Sime=C3=B3) is:<br></div><div class=3D"x_761045520moz-cite-pre= fix"><br></div><div class=3D"x_761045520moz-cite-prefix">How can I help?<br= ></div><div class=3D"x_761045520moz-cite-prefix"><br></div><div class=3D"x_= 761045520moz-cite-prefix">I have always liked the 3 layers of
    FreBSD with kernel, userland and ports. Complicating this would
    not be good.<br></div><div class=3D"x_761045520moz-cite-prefix"><br><= /div><div class=3D"x_761045520moz-cite-prefix">(I am long time FreeBSD user=
    that
    decided to learn the process of porting software this year.
    Submitted my first in March which is in the tree (thank you
    decke), my second in April still waiting for final review and my
    third in july which was removed by upstream before review. I saw
    the backlog and had similar thoughts as Sime=C3=B3.)<br></div><div><b= r></div><div class=3D"x_761045520moz-cite-prefix">Greetings<br></div><div c= lass=3D"x_761045520moz-cite-prefix">/Roger<br></div><div class=3D"x_7610455= 20moz-cite-prefix"><br></div><div class=3D"x_761045520moz-cite-prefix">Den = 2026-10-19 kl. 22:34, skrev Marek
    Zarychta:<br></div><div id=3D"zmail_block"><br></div><p><br></p></div= ><blockquote><div class=3D"x_761045520moz-cite-prefix">On 19.10.2026&nbsp;a=
    t 22:07, Daniel
    Engberg wrote:<br></div><blockquote><div class=3D"x_761045520moz-ci= te-prefix">On 2026-10-19 21:56, Bernhard
    Froehlich wrote:<br></div><blockquote><div dir=3D"auto"><div id= =3D"x_761045520message" dir=3D"auto"><div dir=3D"auto"><div id=3D"x_3872846= 71message" dir=3D"auto"><div><br></div></div><div id=3D"x_387284671content"=
    dir=3D"auto"><div>---- Am Mon, 19
    Oct 2026 18:58:12 +0200 <b> <a href=3D"mailto:reig.simeo@= gmail.com" target=3D"_blank" class=3D"x_761045520moz-txt-link-freetext">rei= g.simeo@gmail.com</a> schrieb </b> ----<br></div><div> <br></div><div> <br>= </div><blockquote><div dir=3D"ltr"><div>A month ago, I decided to upload a = new port
    after years of not doing so. It=E2=80=99s been open=
    for
    30 days and absolutely nothing has happened.
    That=E2=80=99s not really the problem, though=E2=80= =94the port
    isn=E2=80=99t anything special. Just a small Perl
    wrapper for some mojo stuff. The problem is that
    when I look at Bugzilla, there are <a href=3D"https= ://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=3DOpen&amp;limit=3D0&am= p;list_id=3D996712&amp;order=3Dchangeddate%20DESC%2Cpriority%2Cbug_severity= &amp;product=3DPorts%20%26%20Packages&amp;query_format=3Dadvanced" target= =3D"_blank">590
    ports waiting to be committed</a>, some of
    which are 10 years old! It=E2=80=99s all very
    concerning=E2=80=94it doesn=E2=80=99t bode well for=
    FreeBSD.<br> <br> Best regards, the last one to turn off the
    lights<br> <br></div><div>Sime=C3=B3 Reig<br></div>= <div dir=3D"auto"><br><br>Thanks a lot for your motivating words of
    wisdom!</div><div dir=3D"auto"><br></div><div dir= =3D"auto">Anyway your statistics are wrong.
    That 590 tickets in bugzilla are not 590 ports
    to be committed but 590 bugs which are assigned
    and Open. Completely useless number. Overall we
    currently close around 350 Ports PRs per week
    but we have a backlog of around 2950 PRs.<br></div>= <div dir=3D"auto"><br></div><div dir=3D"auto"><a class=3D"x_761045520moz-tx= t-link-freetext" href=3D"https://bugs.freebsd.org/bugzilla/page.cgi?id=3Dda= shboard.html" target=3D"_blank">https://bugs.freebsd.org/bugzilla/page.cgi?= id=3Ddashboard.html</a><br></div><div dir=3D"auto"><br></div><div dir=3D"au= to">Feel free to help or at least stop
    wasting time with useless stats.<br></div><div><br>= </div></div></blockquote></div></div></div></div></blockquote><div>I unders= tand the frustration, unfortunately there are
    administrative/management issues regarding the ports tree
    affecting multiple areas including productivity and engagement
    which in turn also affects our ability to process PRs. On top of
    that most of us are volunteers with limited time, hardware etc.<br>= </div><div> <br></div><div> Best regards,<br></div><div> Daniel <br></div><= /blockquote><p dir=3D"auto" class=3D"x_761045520isSelectedEnd"><span>With L= LVM and the
    abundance of freely available software, the Ports Tree can
    grow rapidly. However, this raises questions about how we
    balance software availability with long-term maintainability.</sp= an><br></p><p dir=3D"auto" class=3D"x_761045520isSelectedEnd">One issue wor=
    th reconsidering
    is the two-week maintainer timeout.&nbsp;<span>For simple updates a=
    nd
    minor fixes, the two-week timeout could be shortened, while
    more substantial changes would still receive adequate review.</sp= an><br></p><p dir=3D"auto" class=3D"x_761045520isSelectedEnd"><span>We shou=
    ld also consider
    whether every piece of software needs to be included in the
    official tree. Some ports serve only a narrow audience or
    duplicate existing functionality, yet still require resources
    to build and maintain. Evaluating the broader usefulness of
    new ports could help keep the collection manageable and
    sustainable.&nbsp;</span>I maintain a few ports locally, but I
    doubt they would be useful to a sufficiently broad audience to
    justify their inclusion in the official tree, especially given
    the resources required to build and maintain them.<br></p><p dir=3D= "auto"><span>The goal should not be to discourage
    contributions, but to ensure that the growth of the Ports Tree
    brings lasting value to the FreeBSD community.&nbsp;</span><br></= p><p>Cheers<br></p><pre class=3D"x_761045520moz-signature">--=20
    Marek Zarychta<br></pre></blockquote></blockquote></div><div><br></div></di= v><br></body></html>
    ------=_Part_795625_2022713194.1793370492573--



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