-
-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Project] Collective Export and Import #7475
Comments
The engineering team has decided on a plan for this project. Some assumptions first:
Based on that, 3 approaches were discussed:
Based on engineering discussions, we have decided to build upon @kewitz's existing work which was already implemented based on the 2nd approach. However, we reckon that the comments made on security risks are valid concerns and special attention will be given to make sure we don't export more than we should. Whenever possible, we'll try to re-use and put in common the permission logic used by GraphQL. |
This week |
Last week
This week
|
This week
|
To push forward decentralization, user independence and GDPR compliance, we want to allow users to export data from their collective and import it in a different instance of our open source software.
Engineering plan for this sprint
Extra
Follow-ups
Edit by @Betree: updated issue with the plan.
The text was updated successfully, but these errors were encountered: