@@ -29,3 +29,33 @@ mailing list as well.
29
29
30
30
### Other useful links
31
31
* [ Public group email archive] ( https://lists.w3.org/Archives/Public/public-vc-wg/ )
32
+
33
+ ## Process Overview for VC Data Model Pull Requests
34
+ 1 . For now, we will focus only on merging new errata PRs into this repository,
35
+ but encourage activity related to new features.
36
+ 2 . Once a PR is opened, chairs and editors make judgement call on whether
37
+ changes are substantive or editorial.
38
+ <dl >
39
+ <dt >Editorial</dt >
40
+ <dd >Mark with "editorial" tag, merge into branch "v1.1"</dd >
41
+ <dt >Substantive</dt >
42
+ <dd >Mark with "substantial" tag. Bugfixes are merged into separate branch "v1.2". New Features stay around as an open PR.</dd >
43
+ </dl >
44
+ 3 . W3C CCG is notified of PRs that will be merged in the next 14 days if there
45
+ are no objections.
46
+ 4 . When it's determined a new reccomendation should go out, the W3C Verifiable
47
+ Credentials Working Group members meet, review all the PRs that have been
48
+ merged, and make a formal recommendation if agreement is reached.
49
+
50
+ ### Roadmap for 2021
51
+ - 1 editorial update (v1.1?)
52
+ - 1 substantive update (v1.2?)
53
+ - VC Test Suite Refactoring
54
+ - Start planning VC v2 Work, request a rechartering 3-6 months before end of
55
+ year to keep VC WG functioning.
56
+
57
+ ### Focus areas
58
+ - [ v1] Fixing a specific bug
59
+ - [ v1] Update examples in the spec to make them modern
60
+ - [ v2] VC ` @context ` needs updating, possibly with security vocab modularized
61
+ into smaller components instead of all included into a large context file.
0 commit comments