English fork of the Japanese RaSCSI project. RaSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices.
Go to file
Daniel Markstedt 071fdd2dd5
Move os_integration to root level (#1085)
* Move the os_integration dir from cpp/ to root level

Co-authored-by: nucleogenic <nr@nucleogenic.com>
2023-01-28 15:03:41 -08:00
.github Introduce FTP server option; sundry bug fixes (#1028) 2022-12-09 21:00:31 -08:00
cpp Move os_integration to root level (#1085) 2023-01-28 15:03:41 -08:00
doc Introduce a logo for PiSCSI (#1074) 2023-01-22 10:03:47 -08:00
docker Move os_integration to root level (#1085) 2023-01-28 15:03:41 -08:00
hw Moved hw directory to its own repository (#1011) 2022-12-01 19:20:52 -06:00
os_integration Move os_integration to root level (#1085) 2023-01-28 15:03:41 -08:00
python Fix handling of properties files when they're in subdirs (#1082) 2023-01-28 14:36:07 -08:00
_config.yml Set theme jekyll-theme-midnight 2020-07-04 20:39:04 -05:00
.dockerignore Move os_integration to root level (#1085) 2023-01-28 15:03:41 -08:00
.gitignore Rebrand project to PiSCSI (#1016) 2022-12-05 09:58:23 -08:00
easyinstall.sh Move os_integration to root level (#1085) 2023-01-28 15:03:41 -08:00
LICENSE Rebrand project to PiSCSI (#1016) 2022-12-05 09:58:23 -08:00
README.md Add credit for the logo (#1078) 2023-01-26 18:10:12 -08:00

What is PiSCSI?

PiSCSI is a virtual SCSI device emulator that runs on a Raspberry Pi. It runs in userspace, and can emulate several SCSI devices at one time. There is a control interface to attach / detach drives during runtime, as well as insert and eject removable media. This project is aimed at users of vintage Macintosh and Atari computers and more (see compatibility list) from the 1980's and 1990's.

Please check out the full story with much more detail on the wiki!

How do I contribute?

PiSCSI is using the Gitflow Workflow. A quick overview:

  • The master branch should always reflect the contents of the last stable release
  • The develop branch should contain the latest tested & approved updates. Pull requests should be used to merge changes into develop.
  • The rest of the feature branches are for developing new features
  • A tag will be created for each "release". The releases will be named .. where the release number is incremented for each subsequent release tagged in the same calendar month. The first release of the month of January 2021 is called "21.01.01", the second one in the same month "21.01.02" and so on.

Typically, releases will only be planned every few months.

When you are ready to contribute code to PiSCSI, follow the GitHub Forking and Pull Request workflow to create your own fork where you can make changes, and then contribute it back to the project. Please remember to always make Pull Requests against the develop branch.

If you want to add a new translation, or improve upon an existing one, please follow the instructions in the Web Interface README. Once the translation is complete, please use the same workflow as above to contribute it to the project.

I sell on TindieSonarCloud

GitHub Sponsors

Thank you to all of the GitHub sponsors who support the development community!

Special thank you to the Gold level sponsors!

Special thank you to the Silver level sponsors!

Thank you to Lin van der Slikke for the red panda logo design!