From: Blake McBride <blake1024@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Fwd: [simh] Announcing the Open SIMH project
Date: Fri, 3 Jun 2022 15:12:14 -0500 [thread overview]
Message-ID: <CABwHSOvy+MzCmn9fGs5qTc9kx6_tj3DZu9QDAv0_MnUayQmuJQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MC1q2XEJPwpX9BKRxta63CeYsn9VpV8NrcD1vj=pLDUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5032 bytes --]
This is all very interesting. However, there is one important point that I
am unclear about. Is this a fork in SIMH development or a restructuring of
the original SIMH? In other words, is this a continuation of the existing
SIMH effort or a fork?
Thank you.
Blake McBride
On Fri, Jun 3, 2022 at 3:00 PM Clem Cole <clemc@ccc.com> wrote:
> Announcing the Open SIMH project
>
> SIMH is a framework and family of computer simulators, initiated by Bob
> Supnik and continued with contributions (large and small) from many others,
> with the primary goal of enabling the preservation of knowledge contained
> in, and providing the ability to execute/experience, old/historic software
> via simulation of the hardware on which it ran. This goal has been
> successfully achieved and has for these years created a diverse community
> of users and developers.
>
> This has mapped to some core operational principles:
>
> First, preserve the ability to run old/historically significant software.
> This means functionally accurate, sometimes bug-compatible, but not
> cycle-accurate, simulation.
>
> Second, make it reasonably easy to add new simulators for other hardware
> while leveraging common functions between the simulators.
>
> Third, exploit the software nature of simulation and make SIMH convenient
> for debugging a simulated system, by adding non-historical features to the
> environment.
>
> Fourth, make it convenient for users to explore old system environments,
> with as close to historical interfaces, by mapping them to new features
> that modern host operating systems provide.
>
> Fifth, be inclusive of people and new technology. It's serious work, but
> it should be fun.
>
> Previously, we unfortunately never spent the time to codify how we would
> deliver on these concepts. Rather, we have relied on an informal use of
> traditional free and open-source principles.
>
> 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.
>
> For this reason, a number of us have stepped up to create a new
> organizational structure, which we call "The Open SIMH Project", to be the
> keeper and provide formal governance for the SIMH ecosystem going forward.
> While details of the structure and how it operates are likely to be refined
> over time, what will not change is our commitment to maintaining SIMH as a
> free and open-source project, licensed under an MIT-style license as shown
> on the "simh" repository page.
>
> It is our desire that all of the past users and contributors will come to
> recognize that the new organizational structure is in the best interests of
> the community at large and that they will join us in it. However, this
> iproject as defined, is where we intend to contribute our expertise and
> time going forward. At this point, we have in place the following,
> although we foresee other resources being added in the future as we
> identify the need and execute against them:
>
> A Github "organization" for the project at https://github.com/open-simh
>
> A Git repository for the simulators themselves at
> https://github.com/open-simh/simh
>
> The license for the SIMH simulator code base, found in LICENSE.txt in the
> top level of the "simh" repository.
>
> The "SIMH related tools" in https://github.com/open-simh/simtools. This
> is also licensed under MIT style or BSD style open source licenses (which
> are comparable apart from some minor wording differences).
>
> A "SIMH Steering Group" -- project maintainers and guides.
>
> The conventional git style process is used for code contributions, via
> pull request to the project repository. The Steering Group members have
> approval authority; this list is likely to change and grow over time.
>
> By formalizing the underlying structure, our operational principles and
> guidance can best benefit the community. These are being developed and
> formalized, with a plan to publish them soon.
>
> We have used our best judgment in setting up this structure but are open
> to discussion and consideration of other ideas, and to making improvements.
> Many of us have been part of different projects and understand that past
> mistakes are real. We have tried to learn from these experiences and apply
> the collected wisdom appropriately. We desire to hear from the community as
> we update and refine the operating structure for the Open SIMH project.
>
> We hope for your patience and look forward to your support as we work to
> refine the organization and be able to provide this wonderful resource for
> anyone to use as we continue to evolve the technology provided by the SIMH
> system.
>
> The SIMH Steering Group
> Clem Cole
> Richard Cornwell
> Paul Koning
> Timothe Litt
> Seth Morabito
> Bob Supnik
>
>
> ᐧ
> ᐧ
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 6958 bytes --]
next prev parent reply other threads:[~2022-06-03 20:12 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 ` Blake McBride [this message]
2022-06-03 20:23 ` [TUHS] " 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
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=CABwHSOvy+MzCmn9fGs5qTc9kx6_tj3DZu9QDAv0_MnUayQmuJQ@mail.gmail.com \
--to=blake1024@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).