forked from OpenChain-Project/conformance-questionnaire
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathquestionnaire.json
434 lines (434 loc) · 14.4 KB
/
questionnaire.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
{
"specVersion": "2.1.1",
"language": "en",
"title": "Conformance in Questions",
"contextText": "Context",
"questionsText": "Questions",
"completedText": "Completed?",
"statusText": "Status",
"answerColumnText": "Answer",
"sectionColumnText": "Section",
"numberColumnText": "Number",
"specRefColumnText": "Spec Ref",
"questionColumnText": "Question Text",
"tocText": "Table of Contents",
"preambleText": "The OpenChain Project builds trust in open source by making license compliance simpler and more consistent. It maintains the OpenChain Specification to define a core set of requirements every quality compliance program must satisfy. The result is that open source license compliance becomes more predictable, understandable and efficient for participants of the software supply chain.\nThis document contains a series of questions to determine whether a company has an OpenChain Conformant program. If each of these questions can be answered with a \"yes\" then that company meets all the requirements of conformance to the OpenChain Specification version 2.1 (functionally identical to ISO/IEC DIS 5230:2020(e)). If any of the questions are answered with a \"no\" then the company can clearly identify where additional investment is needed to improve the compliance process.",
"sections": [
{
"name": "Part 1",
"title": "1. Program foundation",
"questions": [
{
"correctAnswer": "Yes",
"question": "Do you have a documented policy governing the open source license compliance of the Supplied Software?",
"number": "1.a",
"type": "YES_NO",
"specReference": [
"1.1",
"1.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure to communicate the existence of the open source policy to all Software Staff",
"number": "1.b",
"type": "YES_NO",
"specReference": [
"1.1",
"1.1.2"
]
},
{
"correctAnswer": "Yes",
"question": "Have you identified the roles and responsibilities that affect the performance and effectiveness of the Program?",
"number": "1.c",
"type": "YES_NO",
"specReference": [
"1.2",
"1.2.1"
]
},
{
"correctAnswer": "Yes",
"question": "Have you identified and documented the competencies required for each role?",
"number": "1.d",
"type": "YES_NO",
"specReference": [
"1.2",
"1.2.2"
]
},
{
"correctAnswer": "Yes",
"question": "Have you documented the assessed competence for each Program participant?",
"number": "1.e",
"type": "YES_NO",
"specReference": [
"1.2",
"1.2.3"
]
},
{
"question": "Have you documented the awareness of your Program participants on the following topics?",
"number": "1.f",
"type": "SUBQUESTIONS",
"specReference": [
"1.3",
"1.3.1"
],
"minNumberValidatedAnswers": 4,
"subQuestions": {
"1.f.i": {
"correctAnswer": "Yes",
"question": "The open source policy and where to find it;",
"number": "1.f.i",
"type": "YES_NO",
"specReference": [
"1.3"
]
},
"1.f.ii": {
"correctAnswer": "Yes",
"question": "Relevant open source objectives;",
"number": "1.f.ii",
"type": "YES_NO",
"specReference": [
"1.3"
]
},
"1.f.iii": {
"correctAnswer": "Yes",
"question": "Contributions expected to ensure the effectiveness of the Program;",
"number": "1.f.iii",
"type": "YES_NO",
"specReference": [
"1.3"
]
},
"1.f.iv": {
"correctAnswer": "Yes",
"question": "The implications of failing to follow the Program requirements.",
"number": "1.f.iv",
"type": "YES_NO",
"specReference": [
"1.3"
]
}
}
},
{
"correctAnswer": "Yes",
"question": "Do you have a process for determining the scope of your Program?",
"number": "1.g",
"type": "YES_NO",
"specReference": [
"1.4",
"1.4.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a written statement clearly defining the scope and limits of the Program?",
"number": "1.h",
"type": "YES_NO",
"specReference": [
"1.4",
"1.4.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure to review and document open source license obligations, restrictions and rights?",
"number": "1.i",
"type": "YES_NO",
"specReference": [
"1.5",
"1.5.1"
]
}
]
},
{
"name": "Part 2",
"title": "2. Relevant tasks defined and supported",
"questions": [
{
"correctAnswer": "Yes",
"question": "Have you assigned individual(s) responsibility for receiving external open source compliance inquiries?",
"number": "2.a",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.1"
]
},
{
"correctAnswer": "Yes",
"question": "Is the external open source compliance contact publicly identified (e.g. via an email address or the Linux Foundation Open Compliance Directory)?",
"number": "2.b",
"type": "YES_NO",
"specReference": [
"2.1",
"2.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure for receiving and responding to open source compliance inquiries?",
"number": "2.c",
"type": "YES_NO",
"specReference": [
"2.1",
"2.1.2"
]
},
{
"correctAnswer": "Yes",
"question": "Have you documented the persons, group or function supporting the Program role(s) identified?",
"number": "2.d",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.1"
]
},
{
"correctAnswer": "Yes",
"question": "Have the identified Program roles been properly staffed and adequately funded?",
"number": "2.e",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.2"
]
},
{
"correctAnswer": "Yes",
"question": "Has legal expertise to address internal and external open source compliance been identified?",
"number": "2.f",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.3"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure assigning internal responsibilities for open source compliance?",
"number": "2.g",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.4"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure for handling review and remediation of non-compliant cases?",
"number": "2.h",
"type": "YES_NO",
"specReference": [
"2.1",
"2.2.5"
]
}
]
},
{
"name": "Part 3",
"title": "3 Open source content review and approval",
"questions": [
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure for identifying, tracking and archiving information about the open source components in a Supplied Software release?",
"number": "3.a",
"type": "YES_NO",
"specReference": [
"3.1",
"3.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have open source component records for the Supplied Software which demonstrate the documented procedure was properly followed?",
"number": "3.b",
"type": "YES_NO",
"specReference": [
"3.1",
"3.1.2"
]
},
{
"question": "Do you have a documented procedure that covers these common open source license use cases for open source components in the Supplied Software?",
"number": "3.c",
"type": "SUBQUESTIONS",
"specReference": [
"3.2",
"3.2.1"
],
"minNumberValidatedAnswers": 6,
"subQuestions": {
"3.c.i": {
"correctAnswer": "Yes",
"question": " Distribution in binary form;",
"number": "3.c.i",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
},
"3.c.ii": {
"correctAnswer": "Yes",
"question": " Distribution in source form;",
"number": "3.c.ii",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
},
"3.c.iii": {
"correctAnswer": "Yes",
"question": " Integration with other open source that may trigger additional obligations;",
"number": "3.c.iii",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
},
"3.c.iv": {
"correctAnswer": "Yes",
"question": " Containing modified open source;",
"number": "3.c.iv",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
},
"3.c.v": {
"correctAnswer": "Yes",
"question": " Containing open source or other software under incompatible licenses for interaction with other components in the Supplied Software;",
"number": "3.c.v",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
},
"3.c.vi": {
"correctAnswer": "Yes",
"question": " Containing open source with attribution requirements.",
"number": "3.c.vi",
"type": "YES_NO",
"specReference": [
"3.2",
"3.2.1"
]
}
}
}
]
},
{
"name": "Part 4",
"title": "4. Compliance artifact creation and delivery",
"questions": [
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure describing the process for ensuring the Compliance Artifacts are distributed with Supplied Software as required by the Identified Licenses?",
"number": "4.a",
"type": "YES_NO",
"specReference": [
"4.1",
"4.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure for archiving copies of Compliance Artifacts for the Supplied Software?",
"number": "4.b",
"type": "YES_NO",
"specReference": [
"4.1",
"4.1.2"
]
},
{
"correctAnswer": "Yes",
"question": "Are the Compliance Artifacts archived at least as long as the Supplied Software is offered and as required by the Identified Licenses?",
"number": "4.c",
"type": "YES_NO",
"specReference": [
"4.1",
"4.1.2"
]
}
]
},
{
"name": "Part 5",
"title": "5. Understanding open source community engagements",
"questions": [
{
"correctAnswer": "Yes",
"question": "Do you have a policy for contribution to open source projects on behalf of the organization?",
"number": "5.a",
"type": "YES_NO",
"specReference": [
"5.1",
"5.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure governing open source contributions?",
"number": "5.b",
"type": "YES_NO",
"specReference": [
"5.1",
"5.1.2"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have a documented procedure for making all Software Staff aware of the open source contribution policy?",
"number": "5.c",
"type": "YES_NO",
"specReference": [
"5.1",
"5.1.3"
]
}
]
},
{
"name": "Part 6",
"title": "6. Adherence to the specification requirements",
"questions": [
{
"correctAnswer": "Yes",
"question": "Do you have documentation confirming that your Program meets all the requirements of this specification?",
"number": "6.a",
"type": "YES_NO",
"specReference": [
"6.1",
"6.1.1"
]
},
{
"correctAnswer": "Yes",
"question": "Do you have documentation confirming that your Program conformance was reviewed within the last 18 months?",
"number": "6.b",
"type": "YES_NO",
"specReference": [
"6.2",
"6.2.1"
]
}
]
}
]
}