From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_FONT_LOW_CONTRAST, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19865 invoked from network); 3 Jun 2022 20:12:36 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 3 Jun 2022 20:12:36 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 0FF9E40C23; Sat, 4 Jun 2022 06:12:32 +1000 (AEST) Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) by minnie.tuhs.org (Postfix) with ESMTPS id D8DCF40977 for ; Sat, 4 Jun 2022 06:12:25 +1000 (AEST) Received: by mail-oi1-x235.google.com with SMTP id p129so7113002oig.3 for ; Fri, 03 Jun 2022 13:12:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=2g7cqeOxXXQOvfWuOB+ezPxYw07fvIwXhK3XavKZUaM=; b=S4RbnZ1E9kGh8qvrn2KNDzo1t/xjql9cavcEX0E33vCZLla5hJCj0B0vQ8chR+DZ/a T6/cLwDpH4mzWESmyeVAFItjZVGQkSfS8QB2lFrrGwXEmrxDt7BNbuYVqmhTeByTUreA 8X5JtYROhoFA/L1r4TAZ/7E+REz//KaWmYJQyPati9JJBP8PuYFeMct62Jib7IOS2rqP TKbSEDe+QzOM04gXgFBT7M85N3S2oIfHZTyBxibY0ZskF2Lfpj0tL89SUf7trnJo+tk7 59HUUR5/bXwFDMhNIvh5Sj1ZZ46XXqmkfcwSUYYUcA8kWQNuwOisrJZTlfoSand8elFi kwpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=2g7cqeOxXXQOvfWuOB+ezPxYw07fvIwXhK3XavKZUaM=; b=yEPxRtQs5pQLnV4BzC/yycIC1J5mf6AFPNh5e6fMB/Cvpr30ahNBomLVKHwYpCLWUP KxbyJaur7SJNfR28nkIbp70fVNgl1D3aSC+X/gzwyOwzeVA446Mv6+UsJU4lKcnls99L dth19cwD7ANlztIYInk5kKgnk3/Nl4Im+dW64hZFQvxQ9/0r26HLBTf6mwgh8F/6sqZr dJAGjAo2LoRVxrbBEMgp/0vAgWCe3zFLV5EdoqJinWMMPLjzFIFOTB8rp4Ax6kKWkc4E +L+Age9IBbhuuIQV6dtzbPD5n8PEkjykILLZFdE5hedBE0KzxPDv19zZuewWbCItXSwr wR1w== X-Gm-Message-State: AOAM530/ULUsOnmSOmL5TIvvtyLERu4HmquOlIhVucsXUa0js3IRNgxF b8030EPrHhOKwDQ4btu0QksMyaESQndcJgNXiAdirq95Ctg= X-Google-Smtp-Source: ABdhPJwUgsFEG3B4kZM53nqXIrtY9XjLE5Y/5lDS7neasAD+Ht5MmjHGBk3VTGb6G3yk827jIkv2woAJu7RMe6leo6s= X-Received: by 2002:a05:6808:10c2:b0:32b:77fd:6160 with SMTP id s2-20020a05680810c200b0032b77fd6160mr22066208ois.122.1654287144853; Fri, 03 Jun 2022 13:12:24 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Blake McBride Date: Fri, 3 Jun 2022 15:12:14 -0500 Message-ID: To: The Eunuchs Hysterical Society Content-Type: multipart/alternative; boundary="000000000000a0247305e090bd54" Message-ID-Hash: QI6RC5ZBPADTXOLAYUQHEJIFNWQPRBC7 X-Message-ID-Hash: QI6RC5ZBPADTXOLAYUQHEJIFNWQPRBC7 X-MailFrom: blake1024@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Fwd: [simh] Announcing the Open SIMH project List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000a0247305e090bd54 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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 other= s, > with the primary goal of enabling the preservation of knowledge contained > in, and providing the ability to execute/experience, old/historic softwar= e > 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 th= e > 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 th= e > keeper and provide formal governance for the SIMH ecosystem going forward= . > While details of the structure and how it operates are likely to be refin= ed > 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 show= n > 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 improvement= s. > 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 appl= y > 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 fo= r > anyone to use as we continue to evolve the technology provided by the SIM= H > system. > > The SIMH Steering Group > Clem Cole > Richard Cornwell > Paul Koning > Timothe Litt > Seth Morabito > Bob Supnik > > > =E1=90=A7 > =E1=90=A7 > =E1=90=A7 > --000000000000a0247305e090bd54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This is all very interesting.=C2=A0 However, there is one = important point that I am unclear about.=C2=A0 Is this a fork in SIMH devel= opment or a restructuring of the original SIMH?=C2=A0 In other words, is th= is a continuation of the existing SIMH effort or a fork?

Thank you.

Blake McBride<= /div>

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 Sup= nik and continued with contributions (large and small) from many others, wi= th 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 successfull= y 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. T= his means functionally accurate, sometimes bug-compatible, but not cycle-ac= curate, simulation.

Second, make it reasonably easy to add new simulators for other hardware wh= ile leveraging common functions between the simulators.

Third, exploit the software nature of simulation and make SIMH convenient f= or debugging a simulated system, by adding non-historical features to the e= nvironment.

Fourth, make it convenient for users to explore old system environments, wi= th 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, bu= t it should be fun.

Previously, we unfortunately never spent the time to codify how we would de= liver on these concepts. Rather, we have relied on an informal use of tradi= tional free and open-source principles.

Recently a situation has arisen that compromises some of these principles a= nd 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 organizatio= nal structure, which we call "The Open SIMH Project", to be the k= eeper and provide formal governance for the SIMH ecosystem going forward.= =C2=A0 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 SI= MH as a free and open-source project, licensed under an MIT-style license a= s shown on the "simh" repository page.

It is our desire that all of the past users and contributors will come to r= ecognize 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 ipro= ject as defined, is where we intend to contribute our expertise and time go= ing forward.=C2=A0 At this point, we have in place the following, although = we foresee other resources being added in the future as we identify the nee= d 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 t= op level of the "simh" repository.=C2=A0

The "SIMH related tools" in h= ttps://github.com/open-simh/simtools. This is also licensed under MIT s= tyle or BSD style open source licenses (which are comparable apart from som= e 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 approva= l authority; this list is likely to change and grow over time.

By formalizing the underlying structure, our operational principles and gui= dance can best benefit the community. These are being developed and formali= zed, 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. M= any of us have been part of different projects and understand that past mis= takes 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 re= fine the organization and be able to provide this wonderful resource for an= yone to use as we continue to evolve the technology provided by the SIMH sy= stem.

=C2=A0 =C2=A0 =C2=A0The SIMH Steering Group
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Clem Cole
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Richard Cornwell
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul Koning
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Timothe Litt
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Seth Morabito
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Bob Supnik


=E1=90=A7
=E1=90=A7
=E1=90=A7
--000000000000a0247305e090bd54--