autonomic-cooperative
/
hubl
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Improve federation example

This commit is contained in:
Rachel 2020-07-15 13:29:20 +00:00 committed by Jean-Baptiste Pasquier
parent 69faca7c9f
commit cf147cdba9
1 changed files with 7 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
.gitlab/issue_templates/new_instance
View File

@ -14,7 +14,7 @@
## Federation:
- Which current instance should see this new instance data? Please provide the info module by module.
- Do those current instances agree to share their public data with this new instance? Please provide the info module by module.
- Do those current instances agree to share their public data with this new instance? Yes / No => this can only be asked once per instance.
Example:
@ -23,15 +23,13 @@ Example:
*Instance G wants to be able to chat with users from A, B, C, D, E & F.*
*Instance G wants to be able to see A and B job offers*
*A, B, C, D, E & F are ok to share their data, but they don't want to see F's circles. But they are interested in all other F's modules. This means that F circles' would not be available for federation*.
Let's say every instances agree to this scenario, the issue should describe the following:
- Dashboard: F **Not available for federation**.
- Circles: A, B, C, D, E & F. **Not available for federation**
- Job offers: A, B, F **Available for federation**
- Users: A, B, C, D, E & F. **Available for federation**
- Profile directory: A, B, C, D, E & F. **Available for federation**
- Projects: No federation in any sense.
- Dashboard: G
- Circles: A, B, C, D, E, F & G
- Job offers: A, B, F, G
- Users: A, B, C, D, E, F & G
- Profile directory: A, B, C, D, E, F & G
- G agrees that any new instance can see their public data.
## Cosmetics