move @drhigsby 's boards into /drhigsby

[peepeetee]

Description

At this point in my series of board move PRs, I've started to move boards where I cannot reach the makers beforehand, and have to contact them via the PR itself.

This PR is made without contacting(or failing at contacting) @drhigsby first, so it would need them to approve it for it to go in.

As there was no prior communication before this PR, I have to ask a few questions:

• Is the folder name satisfactory?
• Did I leave anything out?
• Did I include anything I shouldn't have included?

One of the reasons I'm electing to do this is to get as many PRs in as possible before the breaking change deadline, please stop me in my tracks if this is inappropriate.

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.
• 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).

[drhigsby]

Heya, this is totally fine with me. I have not been as active in the keyboarding community lately, but this would be a welcome change :)

[drashna]

This has some merge conflicts that need to be resolved.

[peepeetee]

This has some merge conflicts that need to be resolved.

Resolved