frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2025-03-01 10:36:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs update

Browse Source
This commit is contained in:
Jordan McClintock 2022-02-23 15:39:24 -06:00
parent be2c1f1859
commit f093ef1bb1
No known key found for this signature in database
GPG Key ID: 0A4B92F4FF38EE82
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/code-contribution.md
View File

@ -2,7 +2,7 @@
Sparkles guide is forked from Node-red, which has a LOT of functionality in addition to the nice UI we use. As such, much code is not relevant for our purpose.
Since this is a derivative work, using an Apache 2.0 license. We MUST add a modification copyright to any changed files not originated by us. Add `2021 Modification Copyright - Defense Unicorns` as a comment to the top of any changed file.
Since this is a derivative work, using an Apache 2.0 license. We MUST add a modification copyright to any changed files not originated by us. Add `2022 Modification Copyright - Defense Unicorns` as a comment to the top of any changed file.
Finally, deleting code often has unintended consequences - you should, at a minimum, add cypress tests to confirm basic, common functionality to ensure functionality.

2
docs/sparkles-guides-contribution.md
View File

@ -11,7 +11,7 @@ At the simplest level:
## Conventions and Guidelines
- Topics within flows, build upon each other from left to right. For example, knowing containerization prior to kubernetes.
- Topics within flows, build upon each other from top to bottom. For example, knowing containerization prior to kubernetes.
- Use subflows when a common topic exists. Ex. Zarf requires golang, which is a learning topic itself, or BigBang requires kubernetes
- Add materials (youtube, course, SME, article, etc...) to the description of nodes.
- Add a * to materials that you found helpful