If this is the rules that still apply, I see no major roadblocks from my point of view:
But, my binding might end up being rejected because of one of these points:
- Publishing add-ons that compete directly with an official add-on is not allowed; by “compete” we mean “forks” or alternative implementations offering similar functionality.
- Your contribution must be significantly different from other submissions (no copycats with minor changes). You are encouraged to work together as a community instead of proliferating multiple confusingly similar versions of the same thing.
Whether this “competes” with the official add-on is a question of how you interpret it. The official add-on doesn’t handle the local API of Mill devices, but it does handle Mill devices. The CLA prevents me from modifying the existing binding.
Before undertaking this work, I’d need to know that it won’t be rejected. How would I go about getting clarity about that?