-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Formalise Certified Nodes process #3840
Comments
I think there's a few things here to fix:
|
@joepavitt Who started this work? |
Now? Or for the nodes already done? For the latter, my understanding was it was all Marian? |
Sorry, I meant now. I figured it should've been assigned to someone and I wasn't sure who. The original work I'm aware of :) |
Sorry, yeah, the "Planning" repo says "Started" as it was started in the past, but the "Development" board entry I've just added shows it's "todo" for someone to take in the immediate future |
@joepavitt Just to shortcut the development and for me to hack in my evening I've created https://github.com/FlowFuse/certified-nr-nodes/pull/5/files. I don't think it's production ready, but might shave a few hours of another engineers time. Hope it helps. It's not my intention to complete this, as my output is unpredictable in delivery time at best. |
To start with, I'm writing down what we have in place today to make sense of how it ties together.
|
With our certified nodes program, we have a collection of widgets that customers can trust.
With Marian leaving though, we don't seem to ahve a formally documented process by which new nodes can be added to this list. As such, we should have, documented likely in the Handbook, a clearly defined process by which a set of nodes can be considered "certified"
The text was updated successfully, but these errors were encountered: