|
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-simhA Git repository for the simulators themselves at https://github.com/open-simh/simhThe 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
|
|
|
Awesome! Thanks for your effort!
Jordi Guillaumes Pons
toggle quoted message
Show quoted text
El 3 juny 2022, a les 21:53, Paul Koning <paulkoning@...> va escriure:
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
|
|
|
On Fri, 3 Jun 2022 15:52:08 -0400 "Paul Koning" <paulkoning@...> wrote: Announcing the Open SIMH project Followed.
|
|
|
On Jun 3, 2022, at 12:52 PM, Paul Koning <paulkoning@...> 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
This is great news!
|
|
|
Please consider using gnu license going forward.
On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes < jg@...> wrote: Awesome! Thanks for your effort!
Jordi Guillaumes Pons
> El 3 juny 2022, a les 21:53, Paul Koning <paulkoning@...> va escriure:
>
> 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
>
>
>
>
>
|
|
|
Can you give a good argument for that?
Johnny
toggle quoted message
Show quoted text
On 2022-06-03 22:56, e jaquay wrote: Please consider using gnu license going forward.
On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes <jg@... <mailto:jg@...>> wrote:
Awesome! Thanks for your effort!
Jordi Guillaumes Pons
> El 3 juny 2022, a les 21:53, Paul Koning <paulkoning@...
<mailto:paulkoning@...>> va escriure:
>
> 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 <https://github.com/open-simh>
>
> A Git repository for the simulators themselves at
https://github.com/open-simh/simh <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
<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
>
>
>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
If I had a vote on that I would vote no
From: simh@groups.io <simh@groups.io> on behalf of e jaquay <edj.jaquay@...>
Sent: Friday, June 3, 2022 1:56:18 PM
To: simh@groups.io <simh@groups.io>
Subject: Re: [simh] Announcing the Open SIMH project
Please consider using gnu license going forward.
On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes < jg@...> wrote:
Awesome! Thanks for your effort!
Jordi Guillaumes Pons
> El 3 juny 2022, a les 21:53, Paul Koning <paulkoning@...> va escriure:
>
> 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
>
>
>
>
>
|
|
|
Changing from the MIT license to something very different, which is what GPL is, would be problematic. It might not even be possible given the history of SIMH and the agreement with Digital that made it open source. But in any case, such a change would require the approval of all the copyright holders, which is difficult at best and unlikely to be feasible.
paul
toggle quoted message
Show quoted text
On Jun 3, 2022, at 4:56 PM, e jaquay <edj.jaquay@...> wrote:
Please consider using gnu license going forward.
|
|
|
Just a gut feeling that derivative works clauses in the gnu license might prevent a repeat of the issues causing this fork. As a previous user of simh pdp and vax simulations for industry and one of the maintainers of a totally unrelated simulator project on github I both understood how the issue arose and was also quite dismayed that it did. In industry I would not have been able to use simh if there was any question about the licensing.
On Fri, Jun 3, 2022, 17:08 Johnny Billquist < bqt@...> wrote: Can you give a good argument for that?
Johnny
On 2022-06-03 22:56, e jaquay wrote:
> Please consider using gnu license going forward.
>
> On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes <jg@...
> <mailto:jg@...>> wrote:
>
> Awesome! Thanks for your effort!
>
> Jordi Guillaumes Pons
>
>
> > El 3 juny 2022, a les 21:53, Paul Koning <paulkoning@...
> <mailto:paulkoning@...>> va escriure:
> >
> > 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 <https://github.com/open-simh>
> >
> > A Git repository for the simulators themselves at
> https://github.com/open-simh/simh <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
> <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
> >
> >
> >
> >
> >
>
>
>
>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
GNU licenses are one of the major reasons in industry to not use some software.
Johnny
toggle quoted message
Show quoted text
On 2022-06-03 23:45, e jaquay wrote: Just a gut feeling that derivative works clauses in the gnu license might prevent a repeat of the issues causing this fork. As a previous user of simh pdp and vax simulations for industry and one of the maintainers of a totally unrelated simulator project on github I both understood how the issue arose and was also quite dismayed that it did. In industry I would not have been able to use simh if there was any question about the licensing.
On Fri, Jun 3, 2022, 17:08 Johnny Billquist <bqt@... <mailto:bqt@...>> wrote:
Can you give a good argument for that?
Johnny
On 2022-06-03 22:56, e jaquay wrote:
> Please consider using gnu license going forward.
>
> On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes
<jg@... <mailto:jg@...>
> <mailto:jg@...
<mailto:jg@...>>> wrote:
>
> Awesome! Thanks for your effort!
>
> Jordi Guillaumes Pons
>
>
> > El 3 juny 2022, a les 21:53, Paul Koning
<paulkoning@... <mailto:paulkoning@...>
> <mailto:paulkoning@...
<mailto:paulkoning@...>>> va escriure:
> >
> > 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 <https://github.com/open-simh>
<https://github.com/open-simh <https://github.com/open-simh>>
> >
> > A Git repository for the simulators themselves at
> https://github.com/open-simh/simh
<https://github.com/open-simh/simh>
<https://github.com/open-simh/simh <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
<https://github.com/open-simh/simtools>
> <https://github.com/open-simh/simtools
<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
> >
> >
> >
> >
> >
>
>
>
>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... <mailto:bqt@...> || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
Almost everyone legally uses Linux (big data, super computers, databases, web servers, phones, tvs, cars, etc.) which is GPL. People who use it in products are forced to comply with GPL terms and I agree some would rather not have to. i apreciate that you even consider my suggestion. The important thing for simh is that it is free to use and it remains so.
On Fri, Jun 3, 2022, 17:47 Johnny Billquist < bqt@...> wrote: GNU licenses are one of the major reasons in industry to not use some
software.
Johnny
On 2022-06-03 23:45, e jaquay wrote:
> Just a gut feeling that derivative works clauses in the gnu license
> might prevent a repeat of the issues causing this fork. As a previous
> user of simh pdp and vax simulations for industry and one of the
> maintainers of a totally unrelated simulator project on github I both
> understood how the issue arose and was also quite dismayed that it did.
> In industry I would not have been able to use simh if there was any
> question about the licensing.
>
> On Fri, Jun 3, 2022, 17:08 Johnny Billquist <bqt@...
> <mailto:bqt@...>> wrote:
>
> Can you give a good argument for that?
>
> Johnny
>
> On 2022-06-03 22:56, e jaquay wrote:
> > Please consider using gnu license going forward.
> >
> > On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes
> <jg@... <mailto:jg@...>
> > <mailto:jg@...
> <mailto:jg@...>>> wrote:
> >
> > Awesome! Thanks for your effort!
> >
> > Jordi Guillaumes Pons
> >
> >
> > > El 3 juny 2022, a les 21:53, Paul Koning
> <paulkoning@... <mailto:paulkoning@...>
> > <mailto:paulkoning@...
> <mailto:paulkoning@...>>> va escriure:
> > >
> > > 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 <https://github.com/open-simh>
> <https://github.com/open-simh <https://github.com/open-simh>>
> > >
> > > A Git repository for the simulators themselves at
> > https://github.com/open-simh/simh
> <https://github.com/open-simh/simh>
> <https://github.com/open-simh/simh <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
> <https://github.com/open-simh/simtools>
> > <https://github.com/open-simh/simtools
> <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
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt@... <mailto:bqt@...> ||
> Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol
>
>
>
>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
Various BSD variants plan/have switched to clang from gcc because of the license issues. Apparently they have had complex issues because of the linense. I'd prefer to avoid duplicating their problems.
|
|
|
Well, I can tell there are plenty who don't. Just because a few very big, and noticeable companies are don't mean all the smaller ones do.
But I appreciate the topic being brought up, so it can be clarified if we really want to be open source, or if we want to put in various restrictions. I feel many times people who advocate gpl don't really understand how hurtful it can be because it's not actually the same as free.
Speaking as one who have been in the position to decide on this in a semi-large company, who constantly had to check that we didn't get any gpl software in which could poison the products.
But I should also say that I'm not in any sort of position within the simh project in any form. I've contributed some stuff to Bob way back, and I've contributed some stuff to Mark, but in general simh in itself is not my main interest. It's just a tool for me to play with what I actually want to play with. :-)
Johnny
toggle quoted message
Show quoted text
On 2022-06-04 00:17, e jaquay wrote: Almost everyone legally uses Linux (big data, super computers, databases, web servers, phones, tvs, cars, etc.) which is GPL. People who use it in products are forced to comply with GPL terms and I agree some would rather not have to.
i apreciate that you even consider my suggestion. The important thing for simh is that it is free to use and it remains so.
On Fri, Jun 3, 2022, 17:47 Johnny Billquist <bqt@... <mailto:bqt@...>> wrote:
GNU licenses are one of the major reasons in industry to not use some
software.
Johnny
On 2022-06-03 23:45, e jaquay wrote:
> Just a gut feeling that derivative works clauses in the gnu license
> might prevent a repeat of the issues causing this fork. As a
previous
> user of simh pdp and vax simulations for industry and one of the
> maintainers of a totally unrelated simulator project on github I
both
> understood how the issue arose and was also quite dismayed that
it did.
> In industry I would not have been able to use simh if there was any
> question about the licensing.
>
> On Fri, Jun 3, 2022, 17:08 Johnny Billquist <bqt@...
<mailto:bqt@...>
> <mailto:bqt@... <mailto:bqt@...>>> wrote:
>
> Can you give a good argument for that?
>
> Johnny
>
> On 2022-06-03 22:56, e jaquay wrote:
> > Please consider using gnu license going forward.
> >
> > On Fri, Jun 3, 2022, 16:21 Jordi Guillaumes
> <jg@... <mailto:jg@...>
<mailto:jg@... <mailto:jg@...>>
> > <mailto:jg@...
<mailto:jg@...>
> <mailto:jg@...
<mailto:jg@...>>>> wrote:
> >
> > Awesome! Thanks for your effort!
> >
> > Jordi Guillaumes Pons
> >
> >
> > > El 3 juny 2022, a les 21:53, Paul Koning
> <paulkoning@... <mailto:paulkoning@...>
<mailto:paulkoning@... <mailto:paulkoning@...>>
> > <mailto:paulkoning@...
<mailto:paulkoning@...>
> <mailto:paulkoning@...
<mailto:paulkoning@...>>>> va escriure:
> > >
> > > 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
<https://github.com/open-simh> <https://github.com/open-simh
<https://github.com/open-simh>>
> <https://github.com/open-simh <https://github.com/open-simh>
<https://github.com/open-simh <https://github.com/open-simh>>>
> > >
> > > A Git repository for the simulators themselves at
> > https://github.com/open-simh/simh
<https://github.com/open-simh/simh>
> <https://github.com/open-simh/simh
<https://github.com/open-simh/simh>>
> <https://github.com/open-simh/simh
<https://github.com/open-simh/simh>
<https://github.com/open-simh/simh <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
<https://github.com/open-simh/simtools>
> <https://github.com/open-simh/simtools
<https://github.com/open-simh/simtools>>
> > <https://github.com/open-simh/simtools
<https://github.com/open-simh/simtools>
> <https://github.com/open-simh/simtools
<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
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt@... <mailto:bqt@...>
<mailto:bqt@... <mailto:bqt@...>> ||
> Reading murder books
> pdp is alive! || tryin' to stay hip" -
B. Idol
>
>
>
>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... <mailto:bqt@...> || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
On Jun 3, 2022, at 5:45 PM, e jaquay <edj.jaquay@...> wrote:
Just a gut feeling that derivative works clauses in the gnu license might prevent a repeat of the issues causing this fork. As a previous user of simh pdp and vax simulations for industry and one of the maintainers of a totally unrelated simulator project on github I both understood how the issue arose and was also quite dismayed that it did. In industry I would not have been able to use simh if there was any question about the licensing. Your first point may be valid, but it comes at a high cost. GPL is a divisive thing; some people swear by it, others swear at it. On the use of SIMH in industry, you're right that such use requires clarity about the license. Note however that in a number of cases companies have chosen to avoid using GPL-licensed code because of the baggage that comes with it. In fact, I was co-founder of one such company (we built on NetBSD instead, for a couple of reasons but the license was a critical one). In any event, the primary purpose of our effort is to nail down that the SIMH license is the MIT style license you see in the repository, and that new contributions will be under that same license. As I said, it's unlikely the license will change, but one thing I can definitely state: even if it did, it will always be a proper open source license. That is our purpose, that is our commitment. paul
|
|
|
Thank you for doing this and for your hard work and continued efforts.
|
|
|
On Fri, 2022-06-03 15:52:08 -0400, Paul Koning <paulkoning@...> wrote: A Git repository for the simulators themselves at
https://github.com/open-simh/simh [...] 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). root@lili:/var/lib/laminar/cfg/jb-helpers# rm -rf /var/cache/git/simh{,-tools} root@lili:/var/lib/laminar/cfg/jb-helpers# ./update_repos.sh &> /dev/null root@lili:/var/lib/laminar/cfg/jb-helpers# grep '\<url\>' /var/cache/git/simh{,-tools}/.git/config /var/cache/git/simh/.git/config: url = https://github.com/open-simh/simh/var/cache/git/simh-tools/.git/config: url = https://github.com/open-simh/simtools The SIMH Steering Group
Clem Cole
Richard Cornwell
Paul Koning
Timothe Litt
Seth Morabito
Bob Supnik Thanks a lot, I updated my CI/CD setup. My regular checks as well as the the NetBSD VAX builds will now use open-simh. Thanks guys! MfG, JBG --
|
|
|
Congratulations, and my sincere thanks for this step.
Cordiales saludos / Kind Regards. --
Sergio Pedraja
--
El vie, 3 jun 2022 a las 21:52, Paul Koning (< paulkoning@...>) escribió: 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
|
|
|
I probably missed the memo, but what is the relationship between Version 3 and Version 4? I agree we should have one version going forward, without any restrictions on modification.
|
|
|
Version 4 was/is Mark Pizzolato's fork from version 3.
Johnny
toggle quoted message
Show quoted text
On 2022-06-05 17:45, Iron Spring Software wrote: I probably missed the memo, but what is the relationship between Version 3 and Version 4? I agree we should have one version going forward, without any restrictions on modification.
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
On Sunday, June 5, 2022 at 8:48 AM, Johnny Billquist wrote: Version 4 was/is Mark Pizzolato's fork from version 3. With differences specifically described at https://github.com/simh/simh. V4 includes all functional changes to the V3 codebase up through at least v3.11. On 2022-06-05 17:45, Iron Spring Software wrote:
I probably missed the memo, but what is the relationship between Version 3 and Version 4? I agree we should have one version going forward, without
any restrictions on modification.
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt@... || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
|
|
|
Paul Koning