move @davidphilipbarr 's boards into /dpb

[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) @davidphilipbarr 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?

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

[peepeetee]

I might have made an egregious mistake ripping ferris sweep out of the ferris folder. discuss and show me the error of my ways

[filterpaper]

Please do not make this change. It will hurt the discovery of sweep. That PCB known to the community as the Ferris Sweep and is an iteration of Ferris.

I'm the maintainer of both macro3 and cradio. If it helps, macro3 maintainer can be me so you will not be obliged to store them into the same folder.

[peepeetee]

Please do not make this change. It will hurt the discovery of sweep. That PCB known to the community as the Ferris Sweep and is an iteration of Ferris.

I'm the maintainer of both macro3 and cradio. If it helps, macro3 maintainer can be me so you will not be obliged to store them into the same folder.

Got it, thanks! closed