search

SonixQMK / qmk_firmware

Open-source keyboard firmware for Atmel AVR and Arm USB families
https://sonixqmk.github.io/qmk_docs/
GNU General Public License v2.0
517 stars 409 forks source link

mappings present in `sn32_master` missing from `sn32_develop` #420

Open Swiftb0y opened 1 week ago

Swiftb0y commented 1 week ago

There are a couple mappings present in sn32_master (such as the keychron K3) which are missing from the sn32_develop branch. Is there a reason for that? Whats the relation between these branches exactly? Is the divergence between these two branches intentional?

dexter93 commented 1 week ago

sn32_master / sn32_stable / sn32: older trees, functional but hacked up approach. Significantly harder to maintain. status: abandoned/archived. sn32_develop: rolling release based on qmk/develop, updated quarterly ( or when beneficial patches get merged upstream). Scalable, portable, minimally intrusive to upstream, easier to maintain. Currently the active tracking branch.

Missing mappings/keyboards: Maintainer issue. We dropped/didn't merge them to sn32_develop because significant changes mean active maintainers are needed to verify functionality and keep up with updating. We actively encourage people to migrate mappings from sn32* to sn32_develop and the process is easy, but it only makes sense if having the hardware to verify they work reliably.

Swiftb0y commented 1 week ago

We actively encourage people to migrate mappings from sn32* to sn32_develop and the process is easy, but it only makes sense if having the hardware to verify they work reliably.

Thanks. I'll look into doing that for the keychron K3. Is there more documentation (better than the 5000 commit log diff) on what exactly has changed between these branches and whats needed to migrate from the older trees to develop?

dexter93 commented 6 days ago

We actively encourage people to migrate mappings from sn32* to sn32_develop and the process is easy, but it only makes sense if having the hardware to verify they work reliably.

Thanks. I'll look into doing that for the keychron K3. Is there more documentation (better than the 5000 commit log diff) on what exactly has changed between these branches and whats needed to migrate from the older trees to develop?

The bulk of the changes are covered by the data driven migration and for RGB, the sn32f2xx RGB driver. You can see current configuration examples for sn32 here