Skip to content

Commit 429329c

Browse files
committed
Improve collection governance reference
1 parent b1f19b3 commit 429329c

File tree

1 file changed

+60
-12
lines changed

1 file changed

+60
-12
lines changed

content/collections/reference/governance.md

Lines changed: 60 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,26 +10,74 @@ Setting up and maintaining a collection needs fulfilling certain tasks. These ta
1010

1111
This reference documentation details all available roles that can be involved in a collection's governance to ensure its proper operation and maintenance.
1212

13-
### Host
13+
## Roles
1414

15-
This role ensures that a server and internet access is available to run the engine on and fetch the terms, either by using its own infrastructure or renting a server on a hosting provider.
15+
### `Host`
1616

17-
### Administrator
17+
Ensures the foundational infrastructure required for the collection's operation is available.
1818

19-
This role takes responsibility for ensuring that the engine and associated software tools are functional and up to date.
19+
**Responsibilities:**
2020

21-
### Curator
21+
- Provide the server infrastructure (self-hosted or rented).
22+
- Guarantee reliable internet connectivity for the server to fetch terms.
2223

23-
This role decides which services and terms are welcome in the collection.
24+
---
25+
26+
### `Administrator`
27+
28+
Manages the technical operation of the collection's software, ensuring it runs smoothly, stays updated, and remains secure.
29+
30+
**Responsibilities:**
31+
32+
- Keep the engine operational.
33+
- Ensure terms are tracked.
34+
- Ensure the public publishing of snapshots, versions, and datasets.
35+
- Maintain and update the engine-related infrastructure.
36+
- Apply necessary security patches to the infrastructure.
37+
38+
---
39+
40+
### `Curator`
41+
42+
Defines the collection's focus and ensures all included content aligns with that scope.
2443

25-
### Maintainer
44+
**Responsibilities:**
45+
46+
- Clearly define the collection's scope.
47+
- Make the collection scope publicly available via the metadata file.
48+
- Verify that included services and terms adhere to the defined scope.
49+
50+
---
2651

27-
This role guarantees the quality of the tracked versions by reviewing contributions.
52+
### `Maintainer`
53+
54+
Guarantees the integrity and quality of the collection's data by reviewing incoming contributions.
55+
56+
**Responsibilities:**
57+
58+
- Review contributions.
59+
- Maintain the quality of tracked versions (e.g., removing noise, ensuring completeness).
60+
61+
---
62+
63+
### `Contributor`
64+
65+
Actively adds new service information and keeps existing entries current.
66+
67+
**Responsibilities:**
68+
69+
- Add service declarations.
70+
- Keep service declarations up to date.
71+
72+
---
2873

29-
### Contributor
74+
### `Sponsor`
3075

31-
This role adds declarations and keeps them up to date.
76+
Provides essential non-operational support, such as funding or resources, to facilitate the collection's success.
3277

33-
### Sponsor
78+
**Responsibilities:**
3479

35-
This optional role supports the existence of the collection by funding other roles, providing agent time, political support, or any other relevant non-operational contribution.
80+
- Provide funding for collection operations.
81+
- Provide agent time for other roles.
82+
- Provide political or institutional support.
83+
- Make other relevant non-operational contributions.

0 commit comments

Comments
 (0)