• Q to nominees: Rough plan on Debian/Ubuntu collaboration?

    From M. Zhou@21:1/5 to All on Sun Mar 16 20:40:01 2025
    Hi all,

    Thank you for stepping up for this important and challenging role!

    I noticed that a half of the nominees mentioned strengthening the
    collaboration between Debian/Ubuntu. Would you mind expand a little
    bit on this, like the rough idea? In particular:

    * What problem needs to be addressed regarding Debian/Ubuntu collabration?

    * Rough idea on how the identified issue can be addressed?

    Generally I find the DDPO page's Ubuntu column quite helpful.
    Sometimes I can see Ubuntu has some patches, but not forwarded
    to Debian. Some of these changes can indeed be merged into Debian,
    and I did this multiple times.

    * What is the goal of the proposed collaboration improvement?
    For example, what will be introduced on top of my current experience
    in this regard.

    Long answers are not necessary. I just want to understand the brief
    motivation and goals.

    Thank you!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julian Andres Klode@21:1/5 to M. Zhou on Sun Mar 16 23:00:01 2025
    On Sun, Mar 16, 2025 at 03:31:26PM -0400, M. Zhou wrote:
    Hi all,

    Thank you for stepping up for this important and challenging role!

    I noticed that a half of the nominees mentioned strengthening the collaboration between Debian/Ubuntu. Would you mind expand a little
    bit on this, like the rough idea? In particular:

    * What problem needs to be addressed regarding Debian/Ubuntu collabration?

    * Rough idea on how the identified issue can be addressed?

    Generally I find the DDPO page's Ubuntu column quite helpful.
    Sometimes I can see Ubuntu has some patches, but not forwarded
    to Debian. Some of these changes can indeed be merged into Debian,
    and I did this multiple times.

    * What is the goal of the proposed collaboration improvement?
    For example, what will be introduced on top of my current experience
    in this regard.

    Long answers are not necessary. I just want to understand the brief motivation and goals.

    I'm afraid that this is both a longer email than you anticipated,
    and also somewhat perhaps different answers than what you were
    interested perhaps, because I think for me it's less a concrete issue
    in the collaboration space.

    But I don't want to leave you without an answer to your concrete
    question, so having thought about this some way, I have some notes
    and ideas on how we collaborate and how we can collaborate better.

    We sure have a lot of spaces where collaboration works great, like the Canonical desktop team is very engaged in Debian GNOME maintenance too,
    Paride has become very actively involved in upstream autopkgtest
    maintenance, and of course most of the APT work happens upstream
    first; and sure the patch board is useful.

    But we also have situations like the time_t transition that in the
    end caused some grieve with no clear way to communicate those
    grievances; or people are unhappy with changes performed to their
    package downstream but don't find anyone to contact.

    We can sort of improve both by improving communication. Say you want
    to try something new and would like Ubuntu to try it first, who do
    you reach out too? Say you notice that your packages get mangled in
    wrong ways downstream by various people, who do you talk to?

    In Ubuntu, rbasak started an initiative called SRU Reps that has
    teams designate representatives to the Ubuntu Stable Release Updates
    team to provide a channel for feedback on patterns of behavior.

    In a sort of sense, it may be worthwhile for Ubuntu to provide
    representatives in Debian for Debian developers to reach out to,
    and vice versa, it could make sense for Debian to have designated representatives in the Ubuntu community.

    # concerns re increasing community divergence

    But what I mentioned in my platform as a problem is less of a collaborative
    one but rather that in some ways, Ubuntu community sometimes feels like
    it grows healthier, and I wonder how we can convert Ubuntu members into
    Debian members too.

    I think there's challenges for Ubuntu people to contribute to Debian,
    and it will increasingly become so because we're diverging further and
    further, and there will be more people who (can) contribute to Ubuntu
    but can't/won't contribute to Debian.

    Ubuntu has almost-universal git access to all source packages now, a contributor can for most part just `git ubuntu clone` a repository,
    make some changes and then submit a merge request. Done. People are
    sort of expected to make do with a merge request like that even if
    they prefer a different workflow; like a debdiff in the BTS is in
    Debian.

    Ubuntu has a web-based way to report bugs, a discourse forum for
    discussions and recently moved from IRC to Matrix, all of which
    create a significantly lower burden of entry.

    I don't have good answers here, I'm not sure I have any answers
    really, and a lot of this is highly complex both on the technical
    as well as social level, as the whole discussion on mail line
    length limits shows.

    While we talk about line length limits, I literally had people give
    up trying to interact because they never used a mailing list before
    and are too scared of doing something wrong.

    --
    debian developer - deb.li/jak | jak-linux.org - free software dev
    ubuntu core developer i speak de, en

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Tue Mar 18 17:00:02 2025
    Hi,

    Am Sun, Mar 16, 2025 at 03:31:26PM -0400 schrieb M. Zhou:
    I noticed that a half of the nominees mentioned strengthening the collaboration between Debian/Ubuntu.

    Although I belong to "the other half," I'd still like to share my
    perspective.

    I personally have never had a reason to work on anything other than
    Debian. This is not because I do not appreciate the work of other distributions-whether Ubuntu, another Debian derivative, or something
    entirely different. Rather, it is simply a matter of efficiency for me
    to stick to what I know best.

    I have never subscribed to a "Debian is better than XY" mindset. For me,
    it has always been: "Debian is better **for me** than XY because it
    solves **my** problems, and I am extremely efficient with it since I
    know it in a depth I could never achieve with XY."

    This has, in some ways, led to a certain "ignorance" in my relationship
    with other Linux distributions in the past. However, as I wrote in my
    platform last year[1] under the title 'Reaching Out to Learn', I have
    since attempted to foster more outreach. I answered the call for papers
    at both FOSDEM and FOSSASIA with the following proposal:


    Cross distribution experience exchange

    As Debian Project Leader, I have often reflected on how other Free
    Software distributions address challenges we all face. I am interested
    in discussing how we can learn from each other to improve our work and
    better serve our users. Recognizing my limited understanding of other
    distributions, I aim to bridge this gap through open knowledge exchange.
    My hope is to foster a constructive dialogue that benefits the broader
    Free Software ecosystem. Representatives of other distributions are
    encouraged to participate in this BoF-whether as contributors or
    official co-speakers. My intention is not to drive the discussion from a
    Debian-centric perspective but to ensure that all distributions have an
    equal voice in the conversation.


    This was my way of "sticking to a promise" I made in my platform. Guess
    what? The proposal was rejected by both conferences. Perhaps I
    approached it the wrong way-maybe I should have reached out to other distributions first and submitted a joint proposal. Or perhaps there
    simply isn't much interest in such an exchange. (That said, I have
    participated in similar discussions at DebConf, where we engaged with derivatives, and I found those conversations valuable.)

    As for our derivatives, I am deeply convinced that all our direct and
    indirect users-whether they use Debian itself or one of its
    derivatives-benefit the most when downstream changes flow back upstream
    into Debian. I strongly support making this process as easy as possible.


    Would you mind expand a little
    bit on this, like the rough idea? In particular:

    * What problem needs to be addressed regarding Debian/Ubuntu collabration?

    While I absolutely believe we should enhance collaboration with
    Ubuntu-arguably our most successful derivative-I would not limit the
    effort to just Ubuntu. As I tried to express above, I think the first
    step is simply to start talking to each other, which often seems to be a challenge in the IT world.

    * Rough idea on how the identified issue can be addressed?

    Unfortunately, not at the moment, as I've already admitted that I lack knowledge in this area. However, I am open to any sensible advice on how
    to support good cooperation.


    Generally I find the DDPO page's Ubuntu column quite helpful.
    Sometimes I can see Ubuntu has some patches, but not forwarded
    to Debian. Some of these changes can indeed be merged into Debian,
    and I did this multiple times.

    I can confirm that I have a personal policy of applying patches from any derivative within a 24-hour timeframe and uploading them as soon as
    possible. If these patches come through the BTS or as merge requests, I
    am more than happy to assist.

    This is my perspective as a developer. However, if there are ways I can contribute to this process in my role as DPL, I would be glad to help.

    Long answers are not necessary. I just want to understand the brief motivation and goals.

    Apologies for the lengthy responses. I believe my answers provide
    insight into my approach to collaboration with other distributions,
    which may still be of interest.

    Kind regards
    Andreas.

    [1] https://www.debian.org/vote/2024/platforms/tille

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Matthias Urlichs@21:1/5 to All on Wed Mar 19 08:40:01 2025
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------8E0JT2eI40T41wfp06BJ790x
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    T24gMTYuMDMuMjUgMjI6NTEsIEp1bGlhbiBBbmRyZXMgS2xvZGUgd3JvdGU6DQo+IFVidW50 dSBoYXMgYWxtb3N0LXVuaXZlcnNhbCBnaXQgYWNjZXNzIHRvIGFsbCBzb3VyY2UgcGFja2Fn ZXMgbm93LCBhDQo+IGNvbnRyaWJ1dG9yIGNhbiBmb3IgbW9zdCBwYXJ0IGp1c3QgYGdpdCB1 YnVudHUgY2xvbmVgIGEgcmVwb3NpdG9yeSwNCj4gbWFrZSBzb21lIGNoYW5nZXMgYW5kIHRo ZW4gc3VibWl0IGEgbWVyZ2UgcmVxdWVzdC4gRG9uZS4NCg0KRG9lcyB0aGlzIG1lYW4gdGhh dCBVYnVudHUncyB0eXBpY2FsIHBhY2thZ2VzJ3MgZ2l0IHJlcG9zaXRvcnkgaXMgYW4gDQpV cHN0cmVhbSBjaGVjay1vdXQgd2l0aCBkZWJpYW4vIHN1YmRpcmVjdG9yeSBvbiB0b3AsIGFu ZCBkZWJpYW4vcGF0Y2hlcyANCmFwcGxpZWQ/DQoNCkhvdyBkaWQgeW91IGdldCB0aGVyZSBm cm9tIGhlcmU/IHdvdWxkIERlYmlhbiBiZSBhYmxlIHRvIGNvcHkgdGhhdCANCmFwcHJvYWNo PyByZWxldmFudCB0byBkLXZvdGUsIHdvdWxkIGEgRFBMIHdobyBwcm9tb3RlZCB0aGlzIGlk ZWEgcnVuIA0KaW50byBhbnkgdGVjaG5pY2FsIHByb2JsZW1zLCBiZXNpZGVzIHRoZSBvYnZp b3VzIHNvY2lhbCBvbmVzPyA6LS8NCg0KLS0gDQotLSByZWdhcmRzDQotLSANCi0tIE1hdHRo aWFzIFVybGljaHMNCg0K

    --------------8E0JT2eI40T41wfp06BJ790x--

    -----BEGIN PGP SIGNATURE-----

    wsF5BAABCAAjFiEEr9eXgvO67AILKKGfcs+OXiW0wpMFAmfaZZcFAwAAAAAACgkQcs+OXiW0wpMB bw//eUX/mkIGBI4oghzX2ikD0ZUr7XD/gm0+W6UFjs2yBB0zx2smAvDJzDHKl0i7ap43wA33zEK0 983cpCLqE8VBpj6Beq7U1xHu23oUp+65yl0u3hgzSbC+PNOT7G1qzv13bGvnS4FuCvdk3cdGyn0n uT90fWw5dKLiivIh87ZyWJm45YCLPPoN1WhYP46qtBE5Un/oCk38YKaOBH9KalbBI5A/8cdnE46i sy/e9ty1K3mFMeaZgnE9T4GmTR/eYh3aEKtqkfO6OQ0Qd1hv5PtgcZeT6ZGkuo/2VI2+YyWPhhc6 lJy6WlKvpPAEayFaJ+RZkcLNmEg0+JSjkLetsWOA4ooxmoBre2vmxTVOD643FnBOF/j+pbYIk6xa gdh8/5jWc3iUtAFttbXC5KJEBzOFa1nNhKfm+oQSKfXbmP3XTehTJT3Tf1DtLA5hgM4OTVaLRgyF n3XhFpo9VJszNqQpBNh3ZWAKoO/+RmvLDW3dFq9FEnYGGpeJXeKa8yRFo6Cql6fnCmftWqB7QyaP ELlcZZCGBpbeFoYv4/JG/WnvoUcNnmV+GBYT9gPhTgsUutDkgTM9peESxNpQdAYy/RYNHtybj7I/ 7bJik9UsVzmHUVwA/rLhWE4OefBQNzvH+XBEp8r9JYiMQAosFy3APDG3HnFwDIJYovsx/H/f4XTY +LQ=
    =rEj0
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julian Andres Klode@21:1/5 to Matthias Urlichs on Wed Mar 19 17:20:01 2025
    On Wed, Mar 19, 2025 at 07:35:03AM +0100, Matthias Urlichs wrote:
    On 16.03.25 22:51, Julian Andres Klode wrote:
    Ubuntu has almost-universal git access to all source packages now, a contributor can for most part just `git ubuntu clone` a repository,
    make some changes and then submit a merge request. Done.

    Does this mean that Ubuntu's typical packages's git repository is an
    Upstream check-out with debian/ subdirectory on top, and debian/patches applied?


    No, git-ubuntu imports the unapplied tree, roughly similar to what
    gbp import-dsc would do.


    How did you get there from here? would Debian be able to copy that approach? relevant to d-vote, would a DPL who promoted this idea run into any
    technical problems, besides the obvious social ones? :-/

    The main technical issues is running an importer service and hosting
    the imported repositories, space requirements, reliability, etc; but
    also you don't get those technical issues by proposing it, but the
    person running it :D
    --
    debian developer - deb.li/jak | jak-linux.org - free software dev
    ubuntu core developer i speak de, en

    -----BEGIN PGP SIGNATURE-----

    wsG7BAABCgBvBYJn2uxUCRBvpFjdHbA/cUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcmcO2+8Cj0A/oXoECUETQFDYhRHM6xtxt7mj3OsGPKGS VBYhBE+1iKhMLd55p0x3h2+kWN0dsD9xAAAxHRAAkiIiz03HB+2NmL4WkWFJvRvB obhIB4ztRMRHZM8DzC5hS954wujKapfJ/yljjsgy+b7yQaMj167W9Wa7NUFtY+pj /R1fSd9nsUXCFqM0Y47xx3XmErwr3wV3aqClMsdg6JFrPtH/S3r5gbhftweunLhM Ah5Q1t1e0NHj0kAbhdQt7WgKVceLZ9T9cEUI3tK6aLw3WP3RTQkxsqIlqaTpvt+b de7OmWt0r2HoosMHLQTY8jKUcG35G0aLUyRIe6Cb6jph6y14c90GVNazn1CVEuxi LmGoHLL6Dhdlb33PFVhaXSHeVYt0zaomLVH/cpYSh15BckBTw7h70undnSKWol43 ztXVSwKRK0uKkTZ3TfPEvqhVd/NQsLHfuWxKNCuAKbIx6HkFSmVjRB5+IDmtexvY onQLnfoP2/pZlkP+06kwzEoaLE1xHU4zjgHvwNPbho7lsHKiZ3KmR7YqHjPWi7/9 BxxGlBf1Mj5+J3q/jro8n6JiGksduEsHcomiAPrzQlJwY1NDxiLFjzlkjUkLLqLf u7FDdh/2Guo3elgWUWcRFHTUiW+c9VVxkCcK5RFLfyWXXOBFN6lrF8tWCZBDX75a IRMrM2lWiS2YYVpsadfmS0MO3BLGDSs7GWpaqdtwls/sxZ4xK8nBqmqAtj
  • From Andreas Tille@21:1/5 to All on Wed Mar 19 17:20:01 2025
    Hi Julian,

    Am Wed, Mar 19, 2025 at 05:10:01PM +0100 schrieb Julian Andres Klode:

    No, git-ubuntu imports the unapplied tree, roughly similar to what
    gbp import-dsc would do.

    What will happen if a package has Vcs fields set to Salsa when using git-ubuntu? Is it just cloning the Salsa repository?

    If yes, would it be beneficial for Ubuntu (and other derivatives) if all
    Debian packages were hosted on Salsa, or would such an effort have no
    impact on your workflow?

    Kind regards
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ian Jackson@21:1/5 to Matthias Urlichs on Wed Mar 19 17:40:01 2025
    Matthias Urlichs writes ("Re: Q to nominees: Rough plan on Debian/Ubuntu collaboration?"):
    On 16.03.25 22:51, Julian Andres Klode wrote:
    Ubuntu has almost-universal git access to all source packages now, a contributor can for most part just `git ubuntu clone` a repository,
    make some changes and then submit a merge request. Done.

    I think in the future it will be possible for elements of the
    tag2upload and dgit ecosystem to provide a similar experience.

    We already have "dgit clone" for every package. It gives you
    directly and immediately useable source code, buildable and editable
    withouot knowing the maintainer workflow. [1] [2]

    Reservation [1]: You don't get proper git history this way unless
    the maintainer uploaded with dgit or t2u. t2u adoption will
    hopefully fix that.

    Reservation [2]: dgit clone pisses about with tarballs. The user
    doesn't really need to know about all that stuff, but it makes it
    slow and it causes it to leave droppings lying about. In the
    future, when most packages are uploaded via dgit or t2u, we hope to
    start importing all non-git-based uploads to dgit-repos. Then
    you'll just be able to `git clone`.

    The information exists in principle, to convert a user's MR based on patches-applied back to the maintainer's git format, for all supported
    dgit quilt modes at least. With dgit/tag2upload adoption, we will
    have machine-readable data which should be sufficient to automate
    that.

    The remaining missing part is a forge-like service to which the user/contributor can "git push", which gateways the results to
    whatever the maintainer is doing. In principle we could do this with
    extra stuff on salsa and a bunch of robots, maybe.

    I think this would make a good handwaving workshop, in Brest maybe.

    Does this mean that Ubuntu's typical packages's git repository is an
    Upstream check-out with debian/ subdirectory on top, and debian/patches applied?

    I doubt this is true. But maybe Ubuntu have some magic git-fu I don't
    know about. I'd be interested to hear.

    How did you get there from here? would Debian be able to copy that
    approach? relevant to d-vote, would a DPL who promoted this idea run
    into any technical problems, besides the obvious social ones? :-/

    I think there might be only few *technical* difficulties to your
    suggested proposal - but I don't think we want to try to persuade
    everyone to adopt git-debrebase. (I think git-debrebase is the least
    bad available tooling for maintaining a Debian package with a patch
    stack in a patches-applied view, giving a git-rebase-like dev
    experience.)

    When I and Joey Hess and others invented dgit in Vaumarcus in 2013 we
    assumed it would be impossible to persuade everyone to adopt a uniform
    git tree/branch format, and we thought that central services would be
    very difficult, especially if they needed to interact with ftp.d.o.

    Ian.

    --
    Ian Jackson <[email protected]> These opinions are my own.

    Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
    that is a private address which bypasses my fierce spamfilter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Julian Andres Klode@21:1/5 to Andreas Tille on Wed Mar 19 20:20:01 2025
    On March 19, 2025 5:16:30 PM GMT+01:00, Andreas Tille <[email protected]> wrote: >Hi Julian,

    Am Wed, Mar 19, 2025 at 05:10:01PM +0100 schrieb Julian Andres Klode:

    No, git-ubuntu imports the unapplied tree, roughly similar to what
    gbp import-dsc would do.

    What will happen if a package has Vcs fields set to Salsa when using >git-ubuntu? Is it just cloning the Salsa repository?

    No it's always an imported upload, possibly augmented with a local history.

    Such that if you make a change, you can include your repo and commit in the changes file.
    It then fast forwards to that instead of importing the tarball.
    I think it imports the tarball on top of that if the too disagree, but haven't had the case.

    The Debian repositories at that point don't really matter or even local Ubuntu ones,
    a whole bunch of packages has separate classic packaging repos still.

    --
    sent from my phone, excuse the brevity, if any

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to Andres Klode on Wed Mar 19 17:39:36 2025
    On Sunday, March 16, 2025 2:51:24 PM Mountain Standard Time Julian
    Andres Klode wrote:
    While we talk about line length limits, I literally had people give
    up trying to interact because they never used a mailing list before
    and are too scared of doing something wrong.

    That is a sad commentary.

    --
    Soren Stoutner
    [email protected]
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmfbY8kACgkQwufLJ66w tgOqEBAAg/UTe5fUfkwQer68lMYrvUd/8W1t4nxF0CLXDTIwCo5Idkd9fdSfZY13 bt8pwDN6p2aKSYs9olA30vBpDm2e179u6lg9hcKrqU7EFzLC2X0hepoKclpty5x+ HL/vumdH8iLvrGDnftSr2hsB7SKK/H7c/DXj4BvqnvEyz/7ZN3QPjOO97QmBbxYC UGp/wgpDLGnRajcHWE0N3qZHsHkbJGEFY8v/w7+YpQeclVJnBIyWVs0lDL8TyS7j rAI+Jheyrufr02lPhEvMEtYu6d5U2QzSszM1R8QBqHAVphnVXrFU/HquC+dXhwtF eJ4uouYSPGAoHQnrNppc7wgP9FTiXy1nk5mRwp//Qq9MujvQiqiq2sxiC2BrDJbz 9QRDRXq1ieYtS+P59s0/ywYIbFt++XECPZH54qPlxGSPv+vY5VJqWt6vxP8+6d8a h7fquSgkDIXfltVorhOpW1P8h84UKMlPXqy2lbtBXkwnBwLSNVLIojlIo7KGSoLT DSJqNgtktRFQTUIpMmihXp2UcIXyUsM18leDJHp/IXcdXPQT6MwNjiTIxLsdKzzk Y/ZAQegPvBNxLy8ml98XPPjGSAW7IxG+yMODakIterTUsxw+m3FoLRkUG+48CN/P mAItrdyYhDhkiE0mDREzJst1mwZTvcwyAsq4LgyxqxHPWdDmwqE=
    =bSVF
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Gianfranco Costamagna@21:1/5 to All on Fri Mar 21 09:40:01 2025
    Hello,

    I noticed that a half of the nominees mentioned strengthening the >collaboration between Debian/Ubuntu. Would you mind expand a little
    bit on this, like the rough idea? In particular:

    * What problem needs to be addressed regarding Debian/Ubuntu collabration?

    * Rough idea on how the identified issue can be addressed?

    Generally I find the DDPO page's Ubuntu column quite helpful.
    Sometimes I can see Ubuntu has some patches, but not forwarded
    to Debian. Some of these changes can indeed be merged into Debian,
    and I did this multiple times.

    For example some automatic mail sent when an Ubuntu upload is done, some automatic bug opening
    when an Ubuntu upload is done, e.g. the submittodebian tool might be done inside Ubuntu internal
    repo, with some question if the patch has to be upstreamed or not.

    As example Ubuntu usually does gcc/python/boost/ruby/php transitions ahead of Debian, and all the bugfixes
    build-fixes patches are easily upstreamable.

    * What is the goal of the proposed collaboration improvement?
      For example, what will be introduced on top of my current experience
      in this regard.

    I'm open to smart ideas, I don't have a solution right now, but this doesn't mean we can't find something.

    E.g. something I would appreciate is some sort of whatsapp/telegram bot to notify me when a package I have under DDPO
    is uploaded in Ubuntu, or a new bug is opened, or a new version is released upstream.

    This would make me aware of an issue without having to search for all the emails/spam I receive everyday.

    Emails were good like 30 years ago, I think now we can add some additional tooling for new people joining Debian
    (and also for old people like me who stopped reading emails some time ago)

    G.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)