75th/qmk_firmware

QMK, forked for ZSA's Oryx Configurator (to safeguard stability)

ZSA's fork of QMK Firmware

This purpose of this fork is maintain a clean repo that only contains the keyboard code that we need, and as little else as possible. This is to keep it lightweight, since we only need a couple of keyboards. This is the repo that the EZ Configurator will pull from.

Supported Keyboards

• ErgoDox EZ
• Planck EZ
• Moonlander Mark I

Building

To set up the local build enviroment to create the firmware image manually, head to the Newbs guide from QMK. And instead of using just qmk setup, you will want to run this instead:

qmk setup zsa/qmk_firmware -b firmware20

Maintainers

QMK is developed and maintained by Jack Humbert of OLKB with contributions from the community, and of course, Hasu. The ZSA branch is maintained by Drashna, ZSA's official QMK Liaison, and by Florian Didron, ZSA's lead developer, with input from Erez Zukerman (ZSA CEO).

Update Process

1. Check out branch from ZSA's master branch:
   1. git remote add zsa https://github.com/zsa/qmk_firmware.git
   2. git fetch --all
   3. git checkout -B branchname zsa/master
   4. git push -u zsa branchname
2. Check for core changes:
   • https://github.com/qmk/qmk_firmware/commits/master/quantum
   • https://github.com/qmk/qmk_firmware/commits/master/tmk_core
   • https://github.com/qmk/qmk_firmware/commits/master/util
   • https://github.com/qmk/qmk_firmware/commits/master/drivers
   • https://github.com/qmk/qmk_firmware/commits/master/lib
   • These folders are the important ones for maintaining the repo and keeping it properly up to date. Most, but not all, changes on this list should be pulled into our repo.
3. git cherry-pick the commits we want
   • git rm docs/* -r to remove the document updates when cherry picking. Repeat for any keyboard/keymap/etc that have changes that we aren't interested in
4. Commit update
   • Include commit info in [changelog.md](http://changelog.md)
5. Open Pull request, and include information about the commit

Strategy

To keep PRs small and easier to test, they should ideally be 1:1 with commits from QMK Firmware master. They should only group commits if/when it makes sense. Such as multiple commits for a specific feature (split RGB support, for instance)

Merging

Pull Requests should be merged/rebased, not squashed, so we can maintain a commit history that is close to QMK Firmware's, for ease of reference.