After an email discussion with @tmontes , I guess we need a constitution for Mu so folks can see what rules (both technical and community) we follow, what we expect from contributors and so we can hold ourselves to account.

I'm very much for making things open and clear.

At the very least it should include:

• Rules of the road we (as admins) follow,
• Our expectations of contributors,

README.rst:    kbd = Keyboard()
README.rst:    kbd = Keyboard()
README.rst:    m = Mouse()
adafruit_hid/keyboard_layout_us.py:            kbd = Keyboard()

These now need usb_hid.descriptors passed to them.

For the mode method, the docstring, and hence the API, read as if the user passes a text string to set a new mode. However, these text strings are defined at the top of the module, outside of the class, and use the circuit python const feature. One can work around it by looking up the mode vs. hex value and passing either an integer or hex, but that doesn't seem like the right solution. The most

In the CircuitPython documentation, we have a matrix that shows the available built-in modules for each board. https://circuitpython.readthedocs.io/en/latest/shared-bindings/support_matrix.html

I feel the current location and layout are cumbersome, involve lots of scrolling, and not easy to find.

I would like to extend this information to circuitpython.org, so it's more visible to users. Th

The animate() function that provides the animation ability for the alphanumeric displays should be moved from the animation example to the library.

On the Arduino, the writeMicroseconds method of the Servo class is useful for calibrating servos that don't align directly with the 1-2ms range. An equivalent function or field in the servo class would be more convenient than setting the pulse width range to a wide value and calculating the actual limits.