Skip to content

Commit 92564a6

Browse files
committed
Added SIG page
1 parent 94e405f commit 92564a6

File tree

4 files changed

+38
-15
lines changed

4 files changed

+38
-15
lines changed

docs/project_organisation.md

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -53,19 +53,7 @@ topic just within the weekly Rucio meeting. A SIG topic can involve one or multi
5353
Rucio components, or even the entire system. SIGs are open to any interrested community
5454
member.
5555

56-
Each SIG must define
57-
58-
- A well-defined objective of the group (Creation of a report, Development of
59-
a functionality, ...)
60-
- An expected end-date
61-
- Means to achieve the objective, such as regular meetings, a mailing-list, mattermost
62-
channel, a workshop, ...
63-
- A convener
64-
65-
Currently there are two Rucio special interest groups:
66-
67-
- Quality of Service (QoS)
68-
- [Metadata](sig_metadata.md)
56+
Detailed information for Rucio SIGs can be found [here](special_interest_groups.md).
6957

7058
## Contributors / Developers
7159

docs/sig_metadata.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,10 @@ End of 2023
1919

2020
## Means to achieve the objective
2121

22-
A general mattermost channel + ad hoc meetings with interested communities either
23-
over Zoom or asynchronously over Mattermost.
22+
- Mattermost channel: [#metadata](https://mattermost.web.cern.ch/rucio/channels/metadata)
23+
- eMail list: [email protected]
24+
- ad hoc meetings with interested communities either over Zoom or asynchronously
25+
over Mattermost.
2426

2527
## Convener
2628

docs/special_interest_groups.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
id: special_interest_groups
3+
title: Special Interest Groups
4+
---
5+
6+
## Special Interest Groups
7+
8+
Rucio Special Interest Groups (SIG) serve the purpose to offer a forum for interested users,
9+
operators, and developers to discuss and plan the evolution of a specific part of Rucio.
10+
The topic of a SIG needs to be well-defined and the community interest on the topic
11+
needs to be above a threshold to justify the creation of a SIG, instead of covering the
12+
topic just within the weekly Rucio meeting. A SIG topic can involve one or multiple
13+
Rucio components, or even the entire system. SIGs are open to any interrested community
14+
member.
15+
16+
## Structure
17+
18+
Each SIG must define
19+
20+
- A well-defined objective of the group (Creation of a report, Development of
21+
a functionality, ...)
22+
- An expected end-date
23+
- Means to achieve the objective, such as regular meetings, a mailing-list, mattermost
24+
channel, a workshop, ...
25+
- A convener
26+
27+
## Current Special Interest Groups
28+
29+
| Name | Start | est. End | Convener |
30+
| --------------------------- | -------- | -------- | ---------------------------------------------- |
31+
| Quality of Service | Jul-2021 | | |
32+
| [Metadata](sig_metadata.md) | Jul-2021 | Dec-2023 | [Rob Barnsley](https://github.com/robbarnsley) |

website/sidebars.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,7 @@
8383
"project_organisation",
8484
"rucio_advisory_board",
8585
"component_leads",
86+
"special_interest_groups",
8687
"about_our_contributors",
8788
"contact_us"
8889
]

0 commit comments

Comments
 (0)