Open Source and saying No #OpenSource #OSS @iBotPeaches
When should an open source software project say no to a feature request? Connor Tumbleson writes:
I’m exhausted from seeing a library abandoned because it expanded too much in features.
I’m exhaused from seeing a library buggy because it expanded too much in features.
I’m exhausted from internal debates rewriting a package and assuming that responsibility to have a smaller isolated feature set.
From an Open Source maintainer perspective, it’s extremely important to say “no” to requests/features that bloat a library too much. What has been seen occur many times played out is something like this:
Talented contributor Z delivers feature X to project Y.
Project Y accepts it.
Feature X has an issue in latest release.
Project Y didn’t start that feature so asks contributor Z for some help.
Contributor Z is not around and the fix is taken in by the project.
So a project shouldn’t think about the short term benefit of a new feature, but understand the long term implication of supporting such feature.
Stop breadboarding and soldering – start making immediately! Adafruit’s Circuit Playground is jam-packed with LEDs, sensors, buttons, alligator clip pads and more. Build projects with Circuit Playground in a few minutes with the drag-and-drop MakeCode programming site, learn computer science using the CS Discoveries class on code.org, jump into CircuitPython to learn Python and hardware together, TinyGO, or even use the Arduino IDE. Circuit Playground Express is the newest and best Circuit Playground board, with support for CircuitPython, MakeCode, and Arduino. It has a powerful processor, 10 NeoPixels, mini speaker, InfraRed receive and transmit, two buttons, a switch, 14 alligator clip pads, and lots of sensors: capacitive touch, IR proximity, temperature, light, motion and sound. A whole wide world of electronics and coding is waiting for you, and it fits in the palm of your hand.