adds rot13labs hackboard

[c0ldbru]

Description

Adds rot13labs hackboard as a new keyboard

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

• n/a

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.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• 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).

[dunk2k]

it appears layout information in info.json and readme.md image don't match. When compared, the info.json matrix has an additional key on top row - is this intended?

[c0ldbru]

@dunk2k yeah, the button itself is very unique and im basically just hijacking an open spot in the grid so the button can be programmed via QMK as if it was a switch. I designed the hardware before I fully understood QMK so its not ideal, but it still works very well for my needs.

TL:DR; functionally the layout you posted is correct, even though visually the keyboard appears to match the standard community layout.

[dunk2k]

Thanks for explaining, it's that extra button is what was putting the community layout awry. Would the unique button be better placed a row, of sorts, above the Function row?

[c0ldbru]

Oh, yeah as long as its just for visuals sake I think that would be great! How/where can I do that so it wont affect the functionality?

[dunk2k]

1. info.json:+1 to all "y" co-ordinates in layouts, and move the unique key to "y": 0. Would it be correct to assume, from the readme.md image, that the unique button has a red LED and his positioned top left of the micro controller on PCB?
2. <keymap_dir>/keymap.c: move the unique button's keycode position in sequence from 2nd to 1st. Could even place it on its own row to match layouts in info.json.

[dunk2k]

conforms to PR Checklist regarding physical layout(s)

[c0ldbru]

1. info.json:+1 to all "y" co-ordinates in layouts, and move the unique key to "y": 0. Would it be correct to assume, from the readme.md image, that the unique button has a red LED and his positioned top left of the micro controller on PCB?
2. <keymap_dir>/keymap.c: move the unique button's keycode position in sequence from 2nd to 1st. Could even place it on its own row to match layouts in info.json.

Sweet! Thanks! Thats been updated now.

[dunk2k]

@c0ldbru
To follow up on an earlier question: does the unique button, now on top row, have a red LED and his positioned top left of the micro controller on PCB?

[c0ldbru]

nah, its to the left of the boot and reset buttons; above F4/F5

[c0ldbru]

@dunk2k Just checking in to make sure theres nothing waiting on me for this? Let me know if theres anything I missed!

[c0ldbru]

@drashna Any chance you can review this? I believe your approval is all its waiting on.

[c0ldbru]

@dunk2k is it possible to merge this with just your approval? @drashna seems to have disappeared from this PR but I still would like to get this added for people out there using the hackboard.

[dunk2k]

@dunk2k is it possible to merge this with just your approval? @drashna seems to have disappeared from this PR but I still would like to get this added for people out there using the hackboard.

@c0ldbru, unfortunately I'm not a QMK maintainer, thus I'm unable to merge PRs. Could I suggest on the qmk_firmware channel of the QMK Discord, relay this PR's number and ask if it could be given a look over 🙂