feat(shield): add support of BabyvBle shield

[MakerJake01]

Hello, this is my first pr and shield for zmk. The board is working on my pcb. I think I have filled out the checklist properly. I used current shield files as the base for the main structure of my files. Eye oh designs has approved the board's name. DFTBA.

Board/Shield Check-list

• This board/shield is tested working on real hardware
• Definitions follow the general style of other shields/boards upstream (Reference)
• .zmk.yml metadata file added
• Proper Copyright + License headers added to applicable files
• General consistent formatting of DeviceTree files
• Keymaps do not use deprecated key defines (Check using the upgrader tool)
• &pro_micro used in favor of &pro_micro_d/a if applicable
• .conf file has optional extra features commented out

[dxmh]

Hey! I took a quick first glance over the shield and left a few small comments.

[MakerJake01]

Thank you for the feedback I have made the changes!

[dxmh]

Thanks for making the changes so quickly! It’s a tidy looking shield. 👍

I have a couple questions for @petejohanson:

1. Is SHIELD_babyvble ok to be mixed case? I’m not sure if uppercase is required for any technical reason but may be best for consistency with other shields and similar references.

zmk/app/boards/shields/babyvble/Kconfig.shield

Line 4 in fb550e5

config SHIELD_babyvble

2. Is there a standard/preference for the copyright headers that shields should use, with regards to The ZMK Contributors vs named individuals?

zmk/app/boards/shields/babyvble/babyvble.keymap

Line 2 in fb550e5

* Copyright (c) 2021 The ZMK Contributors

zmk/app/boards/shields/babyvble/babyvble.overlay

Line 2 in fb550e5

* Copyright (c) 2021 Pete Johanson, Richard Jones

[MakerJake01]

Based on pr #978 I have changed the copyright to "The ZMK Contributors" in the documents that have a copyright section.

[dxmh]

Thanks @MakerJake01! I’ve suggested just a few minor changes below for consistency with other shields. We’ll then need @petejohanson or @Nicell to review.

Also, I couldn’t quite tell from the link in the metadata file - what is the general availability of this keyboard? Is it open-source, is there a GB planned, or is it stocked somewhere?

[MakerJake01]

@dxmh At the moment I have been selling the extra PCBs that I have bought. I plan on doing something either in-stock, GB, or open-source. It's up in the air and I don't have a site that I update often. Most of my updates are in my discord server so to me it made the most sense to have that as the link.

[MakerJake01]

I'm starting to think I might need a .dtsi file. I will make one of those very soon. Edit: after some checking, it sounds like it's more need/helpful for split keyboards but as this is not a split I won't make one.

[lesshonor]

After rebasing on main, you'll definitely need to install and run pre-commit to deal with formatting issues (tabs, trailing whitespace, etc). Squashing your commits would also be a very good idea.

[lesshonor]

Suggested change

label = "KSCAN";

This label is now deprecated.

[lesshonor]

Suggested change

#include <dt-bindings/zmk/mouse.h>

...Funnily enough, now that d7d9eed has been merged this would actually build. But you aren't using any mouse behaviors in this keymap, so there isn't much reason to include it.