[Vote ended on 2022-10-11] Improve licensing rules for 'all other code' in the collection inclusion requirements #142
Replies: 10 comments
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
IANAL but as far as I understand this: +1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1, a good clarification/explanation of the existing rules. |
Beta Was this translation helpful? Give feedback.
-
|
+1 we should be as accurate as possible about anything licensing related. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Should the collection inclusion rules be updated to explicitly mention that code outside plugins/ can have other licenses? More precisely: should the update ansible-collections/overview#212 to the rules be merged?
Discussion topic: #123
Please vote with a +1 to merge ansible-collections/overview#212 or -1 to not merge it.
Beta Was this translation helpful? Give feedback.
All reactions