forked from governance-game/governance-game
-
Notifications
You must be signed in to change notification settings - Fork 0
/
standard-for-public-code-assessment.html
1512 lines (1247 loc) · 23.2 KB
/
standard-for-public-code-assessment.html
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
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en" dir="ltr">
<!-- SPDX-License-Identifier: CC0-1.0 -->
<!-- SPDX-FileCopyrightText: 2022-2024 by The Foundation for Public Code <info@publiccode.net>, https://standard.publiccode.net/AUTHORS -->
<head>
<meta charset="UTF-8">
<title>The Governance Game and the Standard for Public Code</title>
<style>
html, body {
font-family: Mulish;
font-size: 11pt;
}
h1, h2 {
font-weight: normal;
position: relative;
}
h1 {
margin-top: 0;
font-size: 1.5cm;
border-bottom: none;
}
h2 {
font-size: 1.5em;
}
@media print {
a {
color: #111;
text-decoration: none;
}
th {
font-weight: 600;
}
td {
padding: 6px 13px;
border: 1px solid #dfe2e5;
}
tr {
background-color: #fff;
border-top: 1px solid #c6cbd1;
}
tr:nth-child(2n) {
background-color: #f6f8fa;
}
}
</style>
</head>
<body>
<h1>The Governance Game and the Standard for Public Code version 0.7.0</h1>
Link to commitment to meet the Standard for Public Code: <a href="./README.md">README</a>
<h2><a href="https://standard.publiccode.net/criteria/code-in-the-open.html">Code in the open</a></h2>
☑<!-- ☑ --> criterion met.
<table id="code-in-the-open" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
All source code for any policy in use (unless used for fraud detection) MUST be published and publicly accessible.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
All source code for any software in use (unless used for fraud detection) MUST be published and publicly accessible.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST NOT contain sensitive information regarding users, their organization or third parties.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Any source code not currently in use (such as new versions, proposals or older versions) SHOULD be published.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Documenting which source code or policy underpins any specific interaction the general public may have with an organization is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/bundle-policy-and-source-code.html">Bundle policy and source code</a></h2>
☑<!-- ☑ --> criterion met.
<table id="bundle-policy-and-source-code" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
N/A
</td>
<td>
The codebase MUST include the policy that the source code is based on.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
If a policy is based on source code, that source code MUST be included in the codebase, unless used for fraud detection.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Policy SHOULD be provided in machine readable and unambiguous formats.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Continuous integration tests SHOULD validate that the source code and the policy are executed coherently.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/make-the-codebase-reusable-and-portable.html">Make the codebase reusable and portable</a></h2>
☐<!-- ☑ --> criterion met.
<table id="make-the-codebase-reusable-and-portable" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST be developed to be reusable in different contexts.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST be independent from any secret, undisclosed, proprietary or non-open licensed software or services for execution and understanding.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase SHOULD be in use by multiple parties.
</td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
The roadmap SHOULD be influenced by the needs of multiple parties.
</td>
<td>
GitHub issues and the roadmap are open, but little outside input yet.
</td>
</tr>
<tr>
<td>
</td>
<td>
The development of the codebase SHOULD be a collaboration between multiple parties.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Configuration SHOULD be used to make source code adapt to context specific needs.
</td>
<td>
So far, nothing to configure; different printing options are included
</td>
</tr>
<tr>
<td>
</td>
<td>
The codebase SHOULD be localizable.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Source code and its documentation SHOULD NOT contain situation-specific information.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Codebase modules SHOULD be documented in such a way as to enable reuse in codebases in other contexts.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The software SHOULD NOT require services or platforms available from only a single vendor.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/welcome-contributors.html">Welcome contributors</a></h2>
☑<!-- ☑ --> criterion met.
<table id="welcome-contributors" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST allow anyone to submit suggestions for changes to the codebase.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST include contribution guidelines explaining what kinds of contributions are welcome and how contributors can get involved, for example in a `CONTRIBUTING` file.
</td>
<td>
<a href="https://github.com/publiccodenet/governance-game/blob/develop/CONTRIBUTING.md">CONTRIBUTING.md</a>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST document the governance of the codebase, contributions and its community, for example in a `GOVERNANCE` file.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase SHOULD advertise the committed engagement of involved organizations in the development and maintenance.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase SHOULD have a publicly available roadmap.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase SHOULD publish codebase activity statistics.
</td>
<td>
<a href="https://github.com/publiccodenet/governance-game/pulse">GitHub Pulse</a>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Including a code of conduct for contributors in the codebase is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/make-contributing-easy.html">Make contributing easy</a></h2>
☑<!-- ☑ --> criterion met.
<table id="make-contributing-easy" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST have a public issue tracker that accepts suggestions from anyone.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation MUST link to both the public issue tracker and submitted codebase changes, for example in a `README` file.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST have communication channels for users and developers, for example email lists.
</td>
<td>
<a href="https://github.com/publiccodenet/governance-game/discussions">GitHub Discussions</a>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
There MUST be a way to report security issues for responsible disclosure over a closed channel.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation MUST include instructions for how to report potentially security sensitive issues.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/maintain-version-control.html">Maintain version control</a></h2>
☑<!-- ☑ --> criterion met.
<table id="maintain-version-control" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
All files in the codebase MUST be version controlled.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
All decisions MUST be documented in commit messages.
</td>
<td>
(since 1.0.0)
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Every commit message MUST link to discussions and issues wherever possible.
</td>
<td>
(since 1.0.0)
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The codebase SHOULD be maintained in a distributed version control system.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Contribution guidelines SHOULD require contributors to group relevant changes in commits.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Maintainers SHOULD mark released versions of the codebase, for example using revision tags or textual labels.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Contribution guidelines SHOULD encourage file formats where the changes within the files can be easily viewed and understood in the version control system.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
It is OPTIONAL for contributors to sign their commits and provide an email address, so that future contributors are able to contact past contributors with questions about their work.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/require-review-of-contributions.html">Require review of contributions</a></h2>
☐<!-- ☑ --> criterion met.
<table id="require-review-of-contributions" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
All contributions that are accepted or committed to release versions of the codebase MUST be reviewed by another contributor.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Reviews MUST include source, policy, tests and documentation.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Reviewers MUST provide feedback on all decisions to not accept a contribution.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The review process SHOULD confirm that a contribution conforms to the standards, architecture and decisions set out in the codebase in order to pass review.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Reviews SHOULD include running both the software and the tests of the codebase.
</td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
Contributions SHOULD be reviewed by someone in a different context than the contributor.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Version control systems SHOULD NOT accept non-reviewed contributions in release versions.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Reviews SHOULD happen within two business days.
</td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
Performing reviews by multiple reviewers is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/document-codebase-objectives.html">Document codebase objectives</a></h2>
☑<!-- ☑ --> criterion met.
<table id="document-codebase-objectives" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
The codebase MUST contain documentation of its objectives, like a mission and goal statement, that is understandable by developers and designers so that they can use or contribute to the codebase.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Codebase documentation SHOULD clearly describe the connections between policy objectives and codebase objectives.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Documenting the objectives of the codebase for the general public is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/document-the-code.html">Document the code</a></h2>
☑<!-- ☑ --> criterion met.
<table id="document-the-code" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
All of the functionality of the codebase, policy as well as source code, MUST be described in language clearly understandable for those that understand the purpose of the codebase.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation of the codebase MUST contain a description of how to install and run the software.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation of the codebase MUST contain examples demonstrating the key functionality.
</td>
<td>
video linked in README
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation of the codebase SHOULD contain a high level description that is clearly understandable for a wide audience of stakeholders, like the general public and journalists.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation of the codebase SHOULD contain a section describing how to install and run a standalone version of the source code, including, if necessary, a test dataset.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
The documentation of the codebase SHOULD contain examples for all functionality.
</td>
<td>
video and README
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
The documentation SHOULD describe the key components or modules of the codebase and their relationships, for example as a high level architectural diagram.
</td>
<td>
There are .tex files and a Makefile, no architecture
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
There SHOULD be continuous integration tests for the quality of the documentation.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Including examples that make users want to immediately start using the codebase in the documentation of the codebase is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/use-plain-english.html">Use plain English</a></h2>
☑<!-- ☑ --> criterion met.
<table id="use-plain-english" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
Ok
</td>
<td>
All codebase documentation MUST be in English.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
All source code MUST be in English, except where policy is machine interpreted as code.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
All bundled policy not available in English MUST have an accompanying summary in English.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Any translation MUST be up to date with the English version and vice versa.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
There SHOULD be no acronyms, abbreviations, puns or legal/non-English/domain specific terms in the codebase without an explanation preceding it or a link to an explanation.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Documentation SHOULD aim for a lower secondary education reading level, as recommended by the <a href="https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=315#readable">Web Content Accessibility Guidelines 2</a>.
</td>
<td>
</td>
</tr>
<tr>
<td>
</td>
<td>
Providing a translation of any code, documentation or tests is OPTIONAL.
</td>
<td>
</td>
</tr>
</table>
<h2><a href="https://standard.publiccode.net/criteria/use-open-standards.html">Use open standards</a></h2>
☑<!-- ☑ --> criterion met.
<table id="use-open-standards" style="width:100%">
<tr><th>Meets</th><th>Requirement</th><th style="width:25%">Notes and links</th></tr>
<tr>
<td>
N/A
</td>
<td>
For features of the codebase that facilitate the exchange of data the codebase MUST use an open standard that meets the <a href="https://opensource.org/osr">Open Source Initiative Open Standard Requirements</a>.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Any non-open standards used MUST be recorded clearly as such in the documentation.
</td>
<td>
</td>
</tr>
<tr>
<td>
Ok
</td>
<td>
Any standard chosen for use within the codebase MUST be listed in the documentation with a link to where it is available.
</td>
<td>
</td>
</tr>
<tr>
<td>
N/A
</td>
<td>
Any non-open standards chosen for use within the codebase MUST NOT hinder collaboration and reuse.
</td>
<td>
</td>
</tr>