Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this project still being developed? #1195

Open
gargarface2543 opened this issue Apr 10, 2024 · 2 comments
Open

Is this project still being developed? #1195

gargarface2543 opened this issue Apr 10, 2024 · 2 comments

Comments

@gargarface2543
Copy link

Hi, sorry for making this an issue post but I wanted to know if this project is still being updated.

@gargarface2543
Copy link
Author

Nevermind, moving my system to open-simh since this repo is not FOSS as of Issue #1163. I read up on the event and I have to say i'm ashamed that the maintainer would come to such a petty decision.

@markpizz
Copy link
Member

This was explained in the conversation here: https://groups.io/g/simh/topic/101942945#3258

  1. All functional simulator code changes in the open-simh/simh codebase since open-simh/simh forked from simh/simh are included in simh/simh codebase.
  2. The simh/simh codebase is freely usable by anyone who doesn't modify specific modules in the code (See the License.txt file for details).
  3. I personally added the very many extensions beyond Bob Supnick's original simulators during the almost a dozen years I exclusively managed the project at simh/simh. During that dozen year time, many folks added simulators to the resulting codebase along with helping with or providing new generic facilities for all simulators and the number of simulators grew from Bob's original 25 simulators to some 78 simulators today. I have continued to provide enhancements, bugfixes and extensions to the previous functionality since the open-simh project's fork of the then existing simh/simh repo was established in May 2022. The activity that led to the open-simh fork was due to a simh user who raised a complaint that some functionality that had been in the codebase for some 18 months didn't behave the way he wanted. Historically when users find problems with a particular simulators or general simulator facilities, the author of the specifically problematic code is engaged to address the issue. Since I was the author of the vast majority of the evolution of the codebase, the module in question had been authored by me. I fixed the problems raised by this user and provided several separate ways to disable or remove the details the user was offended by. The user didn't like the fact that he might have to disable the functionality and insisted that it must not exist or certainly needed to be explicitly enabled rather than being the default. Since I'd already addressed the issue several folks got together and said the default should be changed. I said no and subsequently added language to the license on simh/simh such that no one could change this feature and no one could use any of my future changes to simh/simh if they "needed" to change this functionality. This license is absolutely NOT FOSS, but all of the functionality is fully free for anyone to use who wants to use it as is.
    A group of folks declared themselves to be the simh steering committee and forked simh/simh into open-simh/simh so that they could keep the project fully FOSS. Meanwhile, as mentioned in set cpu idle return "Command not allowed" in NetBSD-5.1.2 #1 above, all simulator changes have been added to simh/simh. Additionally, as I've done for the previous 12 years, significant new functionality, and bug fixes have been added to both the shared simh components and especially the PDP11 and VAX simulators. The changes are summarized in the README.md at https://github.com/simh/simh. Going forward, I will continue to enhance and support what is there. The binaries for recent builds are available at https://github.com/simh/Development-Binaries

As a practical matter, there are very few folks who develop or make changes to simulators, while the vast majority of folks just want them to work so they can get to using the legacy systems they simulate. I'm here to maximize the functionality for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants