New Keyboard: HexBoard

[earboxer]

Added a new keyboard (with two revisions and two keymaps)

Description

The HexBoard is a MIDI Controller, but it also doubles as a 120% keyboard. Its default firmware focuses on the experience for musicians, but by running QMK firmware, it can be customized for all kinds of experiences.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• [-] I have read the PR Checklist document and have made the appropriate changes.
  • "readme.md: flash command is present, and has :flash at end" This command didn't work for me. Can we use a :flash command for RP2040-based boards?
  • "removed MIDI_ENABLE, FAUXCLICKY_ENABLE and HD44780_ENABLE" (I'm using MIDI, don't I need this?)
  • no “keymap only” features enabled : ENCODER_MAP_ENABLE (where should I enable this feature?
  • (please someone help with these so I can understand them)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  • Please squash-merge this PR
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[waffle87]

Code should not be duplicated where possible. eg.

hexboard
├── 1_1	# configuration that only applies to 1_1 hardware
│   ├── info.json
│   └── rules.mk
├── dev	# configuration that only applies to dev hardware
│   ├── info.json
│   └── rules.mk
├── hexboard.c	# code that applies to both revisions (eg. oled)
├── info.json	# configuration that applies to both models
└── keymaps
    └── default

Also, since OLEDs are enabled at the keyboard level, there needs to exist some keyboard level code to display something on them.

[waffle87]

There are also compilation issues with the dev firmware. They can be viewed in the "QMK CI Build" link below.

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[github-actions]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[earboxer]

(will this ever get merged?)

[drashna]

Mostly, it's waiting on a second review, and I've flagged it as awaiting review to help with that.