From 762bfd0c3ca6b581907962eb77dae00eddf35803 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Mon, 26 May 2025 15:20:18 +0200 Subject: [PATCH 01/11] Update roles reference --- content/collections/how-to/create.md | 2 +- content/collections/reference/governance.md | 82 --------- content/collections/reference/metadata.md | 2 +- content/collections/reference/roles.md | 185 ++++++++++++++++++++ content/collections/reference/status.md | 6 +- content/federation/reference/criteria.md | 2 +- docs/ota-tracking.md | 9 + 7 files changed, 200 insertions(+), 88 deletions(-) delete mode 100644 content/collections/reference/governance.md create mode 100644 content/collections/reference/roles.md create mode 100644 docs/ota-tracking.md diff --git a/content/collections/how-to/create.md b/content/collections/how-to/create.md index c48a4295..d471f386 100644 --- a/content/collections/how-to/create.md +++ b/content/collections/how-to/create.md @@ -25,7 +25,7 @@ You can inform the community by posting on the instant messaging system, or [sen ## Define governance -Setting up and maintaining a collection over time needs fulfilling certain tasks on a regular basis. These tasks are handled through roles. To make sure that all these roles are covered, define the [governance]({{< relref "collections/reference/governance" >}}) of your collection. +Setting up and maintaining a collection over time needs fulfilling certain tasks on a regular basis. These tasks are handled through roles. To make sure that all these roles are covered, define the [governance]({{< relref "collections/reference/roles" >}}) of your collection. At any time, feel free to ask for help or partners in the community. diff --git a/content/collections/reference/governance.md b/content/collections/reference/governance.md deleted file mode 100644 index a53a1667..00000000 --- a/content/collections/reference/governance.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Governance -weight: 1 -aliases: /collections/governance/ ---- - -# Collection governance - -Setting up and maintaining a collection entails fulfilling specific tasks. These tasks are handled through roles. Each of these roles can be volunteer or paid, and can be handled by one or several different entities. - -This reference documentation details all roles that must be involved in a collection's governance to ensure its proper operation and maintenance. - -## Roles - -### Host - -Ensures the availability of the infrastructure required for the collection's operation. - -#### Responsibilities - -- Provide the server infrastructure (self-hosted or rented). -- Apply hypervisor security updates if relevant. -- Guarantee reliable internet connectivity for the server to fetch terms. - ---- - -### Administrator - -Manages the technical operation of the collection's software, ensuring it runs smoothly, stays updated, and remains secure. - -#### Responsibilities - -- Ensure the engine runs at the specified schedule. -- Ensure the public publishing of snapshots, versions, and datasets. -- Keep the engine and deployment systems up-to-date. -- Apply operating system security updates. - ---- - -### Curator - -Defines the collection's focus and ensures all included content aligns with that scope. - -#### Responsibilities - -- Clearly define the collection's scope. -- Make the collection scope publicly available via the metadata file. -- Verify that included services and terms match the defined scope. - ---- - -### Maintainer - -Guarantees the integrity and quality of the collection's data by reviewing incoming contributions. - -#### Responsibilities - -- Review contributions. -- Maintain the quality of tracked versions (e.g. removing noise, ensuring completeness). - ---- - -### Contributor - -Updates terms tracking and adds new entries. - -#### Responsibilities - -- Add service declarations. -- Keep service declarations up to date. - ---- - -### Sponsor - -Provides non-operational support such as funding or resources to facilitate the collection's success. - -#### Responsibilities - -- Provide funding or in-kind contributions for collection operations. -- Provide political or institutional support. -- Make other relevant non-operational contributions. diff --git a/content/collections/reference/metadata.md b/content/collections/reference/metadata.md index b124420a..41b7f742 100644 --- a/content/collections/reference/metadata.md +++ b/content/collections/reference/metadata.md @@ -207,7 +207,7 @@ fr: {{< refItem name="roles" type="array of strings" - description="Roles of the entity within the governance, see [collection governance](https://docs.opentermsarchive.org/collections/reference/governance/)" + description="Roles of the entity within the governance, see [collection governance](https://docs.opentermsarchive.org/collections/reference/roles/)" allowedValues="host, administrator, curator, maintainer, sponsor" example="[host, administrator]" required=true diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md new file mode 100644 index 00000000..13a67353 --- /dev/null +++ b/content/collections/reference/roles.md @@ -0,0 +1,185 @@ +--- +title: Collection roles reference +linkTitle: Roles +weight: 1 +aliases: + - /collections/governance/ + - /collections/reference/roles/ +--- + +# Collection roles reference + +A collection in Open Terms Archive is a set of tracked terms from various services, organized around a specific purpose or theme. This document outlines the different roles involved in operating and maintaining a collection. + +Each role represents a set of responsibilities and tasks that contribute to the collection's success. A role can be filled by one or multiple people, and one person can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection's resources and needs. + +This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. + +## Roles + +### Host + +Ensures the availability of the infrastructure required for the collection's operation. + +#### Responsibilities + +- Maintain reliable and secure infrastructure for collection operations +- Ensure infrastructure meets technical requirements for collection operation +- Provide necessary access and documentation for system administration + +#### Tasks + +- Set up and maintain server infrastructure (self-hosted or rented) +- Implement and maintain security measures +- Configure server for required outbound requests +- Provide server access credentials to administrator +- Document access procedures +- Perform regular server maintenance +- Coordinate maintenance windows with administrator + +--- + +### System administrator (sysadmin) + +Manages the technical operation of the collection's engine, ensuring it runs smoothly, stays updated, and remains secure. + +#### Responsibilities + +- Maintain reliable and secure operation of collection engine +- Ensure timely and accurate terms publication +- Keep collection engine and server up-to-date and secure + +#### Tasks + +- Update and maintain collection configuration files (metadata, deployment, engine) +- Update Open Terms Archive engine and deployment system +- Monitor and restart engine if needed +- Investigate and resolve technical issues through log analysis +- Verify regular updates of snapshots, versions, and datasets +- Report bugs and suggest improvements to engine repository + +--- + +### Curator + +Defines the purpose of the collection, defines its boundaries and ensures all included content aligns with that purpose. + +#### Responsibilities + +- Define and maintain collection's strategic direction +- Ensure collection content aligns with defined purpose +- Guide collection's evolution and growth + +#### Tasks + +- Define and document collection scope +- Review and approve scope changes +- Communicate scope decisions to maintainers and contributors +- Evaluate collection's alignment with purpose + +--- + +### Maintainer + +Ensures the integrity, quality, and accuracy of the collection's terms while managing community contributions. + +#### Responsibilities + +- Ensure quality and accuracy of collection terms +- Manage and facilitate community contributions +- Maintain quality of tracked terms + +#### Tasks + +- Review and validate new service declarations +- Verify service declarations against scope criteria +- Check service names match official branding +- Validate completeness of extracted terms +- Manage repository issues and pull requests +- Provide feedback to contributors +- Report issues to system administrator +- Suggest scope improvements to curator +- Report issues on the engine repository + +--- + +### Contributor + +Expands and maintains the collection's coverage by contributing and updating service terms within the defined scope. + +#### Responsibilities + +- Expand collection coverage within defined scope +- Maintain accuracy of service declarations +- Support collection's growth and quality + +#### Tasks + +- Research and identify new services to track +- Create and update service declarations +- Verify terms URLs and accessibility +- Validate terms selection and extraction +- Report issues to maintainers +- Update outdated service information +- Report issues on the engine repository + +--- + +### Sponsor + +Provides non-operational support such as funding or resources to facilitate the collection's success. + +#### Responsibilities + +- Ensure long-term financial sustainability +- Provide necessary resources for operations +- Enhance collection's reputation and reach + +#### Tasks + +- Provide and manage funding +- Allocate required resources +- Support collection promotion +- Leverage network for visibility +- Advocate for collection adoption + +--- + +### Analyst + +Analyzes terms changes to identify significant modifications and produce actionable insights. + +#### Responsibilities + +- Identify and analyze meaningful terms changes +- Produce insights from changes + +#### Tasks + +- Monitor and review terms changes +- Identify significant modifications +- Write detailed analysis reports +- Create regular digest reports +- Flag critical changes to maintainers +- Provide analysis materials to diffusers +- Report issues affecting analysis + +--- + +### Diffuser + +Promotes collection and disseminates analysis to relevant audiences. + +#### Responsibilities + +- Maximize collection visibility and impact +- Ensure effective communication of findings +- Build and grow collection's community + +#### Tasks + +- Create and manage communication channels +- Publish and distribute analysis reports +- Maintain social media presence +- Track communication metrics +- Engage with community diff --git a/content/collections/reference/status.md b/content/collections/reference/status.md index a06a67e3..8684e6b3 100644 --- a/content/collections/reference/status.md +++ b/content/collections/reference/status.md @@ -13,7 +13,7 @@ The optimal operational state for a collection. - The collection saves records regularly through actively maintained and updated terms declarations. The number of tracked terms remains stable or increases over time. The versions quality is high. - Technical maintenance includes regular dependency updates, access to the latest engine features, and benefits from all infrastructure updates. -- All [roles]({{< relref "collections/reference/governance" >}}) are fulfilled. +- All [roles]({{< relref "collections/reference/roles" >}}) are fulfilled. --- @@ -23,7 +23,7 @@ Collection may be functional but shows clear signs of neglect. - Operational status has deteriorated significantly with unknown record saving status, no updates to terms declarations, declining number of tracked terms, and decreasing versions quality. - Technical maintenance has ceased completely, with no dependency updates, missing latest engine features, and no infrastructure updates. -- All [roles]({{< relref "collections/reference/governance" >}}) are inactive. +- All [roles]({{< relref "collections/reference/roles" >}}) are inactive. --- @@ -33,4 +33,4 @@ Collection has voluntarily ceased all operational activities. - No terms are tracked anymore, though historical records remain accessible for reference purposes. - No technical maintenance is performed. -- All [roles]({{< relref "collections/reference/governance" >}}) are inactive. +- All [roles]({{< relref "collections/reference/roles" >}}) are inactive. diff --git a/content/federation/reference/criteria.md b/content/federation/reference/criteria.md index a4c5a831..15f31ab6 100644 --- a/content/federation/reference/criteria.md +++ b/content/federation/reference/criteria.md @@ -8,7 +8,7 @@ weight: 3 A **collection** can **join** the Open Terms Archive **federation** if it abides by the following quality criteria: 1. Clearly defined [collection metadata]({{< relref "collections/reference/metadata" >}}). -2. Clearly defined [collection governance]({{< relref "collections/reference/governance" >}}). +2. Clearly defined [collection governance]({{< relref "collections/reference/roles" >}}). 3. The vast majority of **versions** are readable, as evidenced by a sample assessment. 4. **Frequency** of at least one track a day, as evidenced by snapshots. 5. Public and open-licensed **declarations**, as evidenced by the `LICENSE` file in the declarations repository. diff --git a/docs/ota-tracking.md b/docs/ota-tracking.md new file mode 100644 index 00000000..9afd8558 --- /dev/null +++ b/docs/ota-tracking.md @@ -0,0 +1,9 @@ +# OTA tracking investigation + +## Overview + +This document analyzes the tracking behavior of various OTA (Online Travel Agency) services, focusing on services that implement bot detection. + +## Tracking logs + +I've included a representative sample of tracking logs from the bot-blocked services. While I didn't save every log, the collected data provides sufficient evidence for our analysis. I focused testing on the bot-blocked services to optimize the investigation time. From b93b97c0814e7b5cd42a7d7f0b5cb9d2e614a6a6 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:02:07 +0200 Subject: [PATCH 02/11] Improve tasks Co-authored-by: Matti Schneider --- content/collections/reference/roles.md | 33 +++++++++++--------------- 1 file changed, 14 insertions(+), 19 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index 13a67353..ad99e53a 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -9,9 +9,8 @@ aliases: # Collection roles reference -A collection in Open Terms Archive is a set of tracked terms from various services, organized around a specific purpose or theme. This document outlines the different roles involved in operating and maintaining a collection. -Each role represents a set of responsibilities and tasks that contribute to the collection's success. A role can be filled by one or multiple people, and one person can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection's resources and needs. +Each role represents a set of responsibilities and tasks that contribute to the collection’s success. A role can be filled by one or multiple people or organisations, and one entity can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection’s resources and needs. This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. @@ -55,39 +54,38 @@ Manages the technical operation of the collection's engine, ensuring it runs smo - Update Open Terms Archive engine and deployment system - Monitor and restart engine if needed - Investigate and resolve technical issues through log analysis -- Verify regular updates of snapshots, versions, and datasets +- Ensure that snapshots, versions and datasets are published - Report bugs and suggest improvements to engine repository --- ### Curator -Defines the purpose of the collection, defines its boundaries and ensures all included content aligns with that purpose. +Defines the purpose and scope of the collection and ensures all included content aligns with it. #### Responsibilities -- Define and maintain collection's strategic direction +- Define and maintain the collection’s strategic direction - Ensure collection content aligns with defined purpose -- Guide collection's evolution and growth #### Tasks - Define and document collection scope -- Review and approve scope changes -- Communicate scope decisions to maintainers and contributors -- Evaluate collection's alignment with purpose +- Define and document level of openness to third-party contributions +- Answer any questions related to scope that emerge from maintainers and contributors +- Communicate scope updates to maintainers and contributors +- Ensure collection’s alignment with original purpose --- ### Maintainer -Ensures the integrity, quality, and accuracy of the collection's terms while managing community contributions. +Ensures the integrity, quality, and accuracy of the collection’s terms. Manages incoming contributions. #### Responsibilities - Ensure quality and accuracy of collection terms -- Manage and facilitate community contributions -- Maintain quality of tracked terms +- Manage and facilitate contributions #### Tasks @@ -98,7 +96,7 @@ Ensures the integrity, quality, and accuracy of the collection's terms while man - Manage repository issues and pull requests - Provide feedback to contributors - Report issues to system administrator -- Suggest scope improvements to curator +- Refer scope conflicts in contributions to curator to open potential scope updates - Report issues on the engine repository --- @@ -138,7 +136,6 @@ Provides non-operational support such as funding or resources to facilitate the #### Tasks - Provide and manage funding -- Allocate required resources - Support collection promotion - Leverage network for visibility - Advocate for collection adoption @@ -147,7 +144,7 @@ Provides non-operational support such as funding or resources to facilitate the ### Analyst -Analyzes terms changes to identify significant modifications and produce actionable insights. +Analyses terms changes to identify significant changes and produce reports in various formats. #### Responsibilities @@ -157,11 +154,9 @@ Analyzes terms changes to identify significant modifications and produce actiona #### Tasks - Monitor and review terms changes -- Identify significant modifications -- Write detailed analysis reports -- Create regular digest reports +- Identify significant changes +- Produce reports - Flag critical changes to maintainers -- Provide analysis materials to diffusers - Report issues affecting analysis --- From 744fadb76c2d1b9bde93a6bf6c0d39d8e0a0ef07 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:03:09 +0200 Subject: [PATCH 03/11] Remove unrelevant file --- docs/ota-tracking.md | 9 --------- 1 file changed, 9 deletions(-) delete mode 100644 docs/ota-tracking.md diff --git a/docs/ota-tracking.md b/docs/ota-tracking.md deleted file mode 100644 index 9afd8558..00000000 --- a/docs/ota-tracking.md +++ /dev/null @@ -1,9 +0,0 @@ -# OTA tracking investigation - -## Overview - -This document analyzes the tracking behavior of various OTA (Online Travel Agency) services, focusing on services that implement bot detection. - -## Tracking logs - -I've included a representative sample of tracking logs from the bot-blocked services. While I didn't save every log, the collected data provides sufficient evidence for our analysis. I focused testing on the bot-blocked services to optimize the investigation time. From d5a9513d88515a4d11400edd4f19486b95c3e719 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:04:08 +0200 Subject: [PATCH 04/11] Update intro Co-authored-by: Matti Schneider --- content/collections/reference/roles.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index ad99e53a..9bab47e7 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -9,11 +9,8 @@ aliases: # Collection roles reference - Each role represents a set of responsibilities and tasks that contribute to the collection’s success. A role can be filled by one or multiple people or organisations, and one entity can fulfill multiple roles. All roles can be either volunteer or paid positions, depending on the collection’s resources and needs. -This reference guide serves as a practical tool for collection organizers. It helps them understand the different roles needed for a collection, assign responsibilities effectively, ensure all necessary tasks are covered, and plan for long-term sustainability. - ## Roles ### Host From a5bb654f7856a5423c7e8dc57359399c9685263a Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:08:37 +0200 Subject: [PATCH 05/11] Reorganize roles order --- content/collections/reference/roles.md | 38 +++++++++++++------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index 9bab47e7..dc0b550c 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -120,25 +120,6 @@ Expands and maintains the collection's coverage by contributing and updating ser --- -### Sponsor - -Provides non-operational support such as funding or resources to facilitate the collection's success. - -#### Responsibilities - -- Ensure long-term financial sustainability -- Provide necessary resources for operations -- Enhance collection's reputation and reach - -#### Tasks - -- Provide and manage funding -- Support collection promotion -- Leverage network for visibility -- Advocate for collection adoption - ---- - ### Analyst Analyses terms changes to identify significant changes and produce reports in various formats. @@ -175,3 +156,22 @@ Promotes collection and disseminates analysis to relevant audiences. - Maintain social media presence - Track communication metrics - Engage with community + +--- + +### Sponsor + +Provides non-operational support such as funding or resources to facilitate the collection's success. + +#### Responsibilities + +- Ensure long-term financial sustainability +- Provide necessary resources for operations +- Enhance collection's reputation and reach + +#### Tasks + +- Provide and manage funding +- Support collection promotion +- Leverage network for visibility +- Advocate for collection adoption From 7fb2e34c2b6d548f7f3cd1e5843623be9ad93079 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:18:54 +0200 Subject: [PATCH 06/11] Improve tasks --- content/collections/reference/roles.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index dc0b550c..b1b28e5c 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -88,13 +88,13 @@ Ensures the integrity, quality, and accuracy of the collection’s terms. Manage - Review and validate new service declarations - Verify service declarations against scope criteria -- Check service names match official branding +- Ensure service declarations follow Open Terms Archive guidelines (service names, service IDs, terms types, filters, history, …) - Validate completeness of extracted terms - Manage repository issues and pull requests - Provide feedback to contributors - Report issues to system administrator - Refer scope conflicts in contributions to curator to open potential scope updates -- Report issues on the engine repository +- Refer issues identified in contributions to the most relevant actor (scope conflicts to curator, tracking issues to system administrator, bugs to the core team…) --- @@ -112,11 +112,9 @@ Expands and maintains the collection's coverage by contributing and updating ser - Research and identify new services to track - Create and update service declarations -- Verify terms URLs and accessibility - Validate terms selection and extraction - Report issues to maintainers -- Update outdated service information -- Report issues on the engine repository +- Report issues affecting contributions to maintainers --- @@ -134,8 +132,7 @@ Analyses terms changes to identify significant changes and produce reports in va - Monitor and review terms changes - Identify significant changes - Produce reports -- Flag critical changes to maintainers -- Report issues affecting analysis +- Report issues affecting analysis to maintainers --- From 4f55d3ef758c6ac9e1eae08529bfee8106b4f72c Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:19:38 +0200 Subject: [PATCH 07/11] Remove useless precision --- content/collections/reference/roles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index b1b28e5c..09932da1 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -81,7 +81,7 @@ Ensures the integrity, quality, and accuracy of the collection’s terms. Manage #### Responsibilities -- Ensure quality and accuracy of collection terms +- Ensure quality of collection terms - Manage and facilitate contributions #### Tasks From 0bf30d9edd8922f844af15b2c8f299e3aeeacf6e Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:20:42 +0200 Subject: [PATCH 08/11] Remove redundant entry --- content/collections/reference/roles.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index 09932da1..b3c4effd 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -93,7 +93,6 @@ Ensures the integrity, quality, and accuracy of the collection’s terms. Manage - Manage repository issues and pull requests - Provide feedback to contributors - Report issues to system administrator -- Refer scope conflicts in contributions to curator to open potential scope updates - Refer issues identified in contributions to the most relevant actor (scope conflicts to curator, tracking issues to system administrator, bugs to the core team…) --- From b2b7af6aa96270939a9d5201bdc53c91e72d6d2f Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 16:38:46 +0200 Subject: [PATCH 09/11] Remove redundant entry --- content/collections/reference/roles.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index b3c4effd..0c2bb7d8 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -92,7 +92,6 @@ Ensures the integrity, quality, and accuracy of the collection’s terms. Manage - Validate completeness of extracted terms - Manage repository issues and pull requests - Provide feedback to contributors -- Report issues to system administrator - Refer issues identified in contributions to the most relevant actor (scope conflicts to curator, tracking issues to system administrator, bugs to the core team…) --- From a370d9596eb872145e2ee0194d9a43da13c0257b Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Wed, 28 May 2025 17:55:46 +0200 Subject: [PATCH 10/11] Improve tasks Co-authored-by: Matti Schneider --- content/collections/reference/roles.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index 0c2bb7d8..95e9c007 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -110,8 +110,6 @@ Expands and maintains the collection's coverage by contributing and updating ser - Research and identify new services to track - Create and update service declarations -- Validate terms selection and extraction -- Report issues to maintainers - Report issues affecting contributions to maintainers --- From d43b4ff752d7114c28390f252f461608bce00b81 Mon Sep 17 00:00:00 2001 From: Nicolas Dupont Date: Thu, 29 May 2025 09:05:05 +0200 Subject: [PATCH 11/11] Improve tasks --- content/collections/reference/roles.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/collections/reference/roles.md b/content/collections/reference/roles.md index 95e9c007..0aac6725 100644 --- a/content/collections/reference/roles.md +++ b/content/collections/reference/roles.md @@ -30,7 +30,6 @@ Ensures the availability of the infrastructure required for the collection's ope - Configure server for required outbound requests - Provide server access credentials to administrator - Document access procedures -- Perform regular server maintenance - Coordinate maintenance windows with administrator --- @@ -90,7 +89,7 @@ Ensures the integrity, quality, and accuracy of the collection’s terms. Manage - Verify service declarations against scope criteria - Ensure service declarations follow Open Terms Archive guidelines (service names, service IDs, terms types, filters, history, …) - Validate completeness of extracted terms -- Manage repository issues and pull requests +- Facilitate discussions in issues and pull requests - Provide feedback to contributors - Refer issues identified in contributions to the most relevant actor (scope conflicts to curator, tracking issues to system administrator, bugs to the core team…)