From: Ben Walton <bdwalton@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: [simh] Announcing the Open SIMH project
Date: Fri, 3 Jun 2022 22:35:45 +0100 [thread overview]
Message-ID: <CAP30j16dmpc4ogd9JfmzbvHFWSCy-7304ig-QCRgR4sNv3v27w@mail.gmail.com> (raw)
In-Reply-To: <20220603202330.f4spdxyn34uiyy5v@illithid>
[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]
On Fri 3 Jun 2022, 21:23 G. Branden Robinson, <g.branden.robinson@gmail.com>
wrote:
> At 2022-06-03T16:00:15-0400, Clem Cole wrote:
> > Recently a situation has arisen that compromises some of these principles
> > and thus the entire status of the project, creating consternation among
> > many users and contributors.
>
> I wonder if that issue would be the one referred to here.
>
> https://twitter.com/the_aiju/status/1526921795139514368
>
> (I understand if Clem doesn't want to directly answer that.)
>
> It's probably impolitic to reference that matter, and if I'm right
> that's no doubt why reference to same was omitted from the announcement
> email. It is traditional for such statements to be high-minded even if
> they wouldn't be necessary but for the rather low conduct that compels
> their issue in response.
>
> The above situation seems similar to others we've seen before. It's
> probably even more impolitic to note that in the Debian Project, this
> sort of licensing shenangians would be referred to as "pulling a Jörg
> Schilling"[1].
>
This stuck a chord for me this evening. I completely understand why such a
saying would come into being, having watched things like cdrecord as a
young person - I totally get the view on licenses here. But I had a chance
to work with Jörg, if only tangentially, on a project and found him to be
warm, engaging, brilliant and overall quite pleasant. I was in a unique
position to connect Jörg and Henry (yes, that Henry) to talk about some old
Unix arcana and it was magic to witness. I hope that in addition to Jörg's
eccentricities people also remember how neat he was as a person. He was a
brilliant mind.
Thanks
-Ben
> I expect that time will soon tell whether an even better term would be
> "committing an XFree86".
>
> On a positive note, I'd like to express my thanks to the SIMH
> contributors past and present for making it straightforward to verify
> the behavior Unix V7 troff in my development work on groff.
>
> If Open SIMH remains dedicated to software freedom in the GNU and DFSG
> senses I expect it will enjoy overwhelming support.
>
> Cheers,
> Branden
>
> [1] https://lwn.net/Articles/195167/
>
[-- Attachment #2: Type: text/html, Size: 3166 bytes --]
next prev parent reply other threads:[~2022-06-03 21:36 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BCDAF4C4-12EC-49D6-84A6-4592E245922F@comcast.net>
[not found] ` <CAC20D2NGMK1NG3J+iR8t2rAzOc2uWCe9ZGRJzkZn6ECgMETJEQ@mail.gmail.com>
[not found] ` <CAC20D2OK9muQm=gCSeRzarV_HQF6vZ9VNuYRas4uCbMyxYKjJA@mail.gmail.com>
2022-06-03 20:00 ` [TUHS] " Clem Cole
2022-06-03 20:12 ` [TUHS] " Blake McBride
2022-06-03 20:23 ` G. Branden Robinson
2022-06-03 21:06 ` Clem Cole
2022-06-03 21:20 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:32 ` Larry McVoy
2022-06-03 21:34 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:37 ` Larry McVoy
2022-06-03 21:36 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 21:40 ` Larry McVoy
2022-06-03 22:16 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:30 ` Larry McVoy
2022-06-03 22:52 ` Warner Losh
2022-06-03 23:48 ` Larry McVoy
2022-06-04 0:10 ` Warner Losh
2022-06-04 1:05 ` Larry McVoy
2022-06-04 1:46 ` David Arnold
2022-06-06 0:32 ` Theodore Ts'o
2022-06-06 0:47 ` George Michaelson
2022-06-06 1:17 ` Larry McVoy
2022-06-06 1:02 ` Warner Losh
2022-06-06 1:09 ` Dan Cross
2022-06-06 1:15 ` Larry McVoy
2022-06-06 1:40 ` Dan Cross
2022-06-06 2:36 ` Larry McVoy
2022-06-06 12:43 ` Dan Cross
2022-06-06 13:41 ` Larry McVoy
2022-06-06 14:27 ` Blake McBride
2022-06-06 14:33 ` Steve Nickolas
2022-06-06 14:53 ` Henry Bent
2022-06-06 23:28 ` David Arnold
2022-06-07 14:30 ` Theodore Ts'o
2022-06-07 15:08 ` Dan Cross
2022-06-07 15:25 ` Larry McVoy
2022-06-07 16:03 ` Will Senn
2022-06-07 16:38 ` Warner Losh
2022-06-07 16:45 ` Larry McVoy
2022-06-07 16:57 ` Warner Losh
2022-06-07 17:05 ` Larry McVoy
2022-06-07 16:46 ` Blake McBride
2022-06-07 17:26 ` Paul Winalski
2022-06-07 20:09 ` Blake McBride
2022-06-07 17:00 ` Paul Winalski
2022-06-07 23:41 ` [TUHS] " Chris Hanson
2022-06-07 15:55 ` [TUHS] Re: Fwd: " Richard Salz
2022-06-03 23:56 ` David Arnold
2022-06-04 0:30 ` Yeechang Lee
2022-06-04 1:03 ` Adam Thornton
2022-06-03 22:33 ` Warner Losh
2022-06-03 22:40 ` Tom Ivar Helbekkmo via TUHS
2022-06-03 22:56 ` Warner Losh
2022-06-03 22:26 ` Warner Losh
2022-06-03 22:19 ` Warner Losh
2022-06-03 21:35 ` Ben Walton [this message]
2022-06-03 20:52 ` Will Senn
2022-06-03 21:06 ` [TUHS] " Adam Thornton
2022-06-04 9:09 ` Ralph Corderoy
2022-06-04 2:59 [TUHS] Re: Fwd: " Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP30j16dmpc4ogd9JfmzbvHFWSCy-7304ig-QCRgR4sNv3v27w@mail.gmail.com \
--to=bdwalton@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).