Skip to content
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

Export the db structure (of a group) so I can setup my own crabcrass #382

Open
gerdneuman opened this issue Feb 15, 2016 · 0 comments
Open

Comments

@gerdneuman
Copy link

Spawned from #236 (comment):

Main idea is to be able to export one's (group) dataset in order to import it into another crabgrass instance.

The ability to export one's dataset makes using the hosted Crabgrass instance much more approachable because it means that one's data is not forever in some format that is only meaningfully accessible if the remote service is available.

Further, I work in some environments where the absense of a local backup precludes the use of Crabgrass by policy. Adding this feature would help me make the case to certain groups to move to Crabgrass away from less safe and less philosophically aligned alternatives such as Gogle Docs.

See also the many, many dupes of this feature request:

https://labs.riseup.net/code/issues/475
https://labs.riseup.net/code/issues/754
https://labs.riseup.net/code/issues/1270
https://labs.riseup.net/code/issues/1702
https://labs.riseup.net/code/issues/4099
https://labs.riseup.net/code/issues/4419

TL;DR: Please implememt this feature regardless of commitments to keep we.riseup.net alive. It is an important data portability issue and software libre issue on its own merit. Thank you!

@meitar cc

@gerdneuman gerdneuman changed the title Allow a group's commitee to export a database dump (for importing it into another crabgrass instance) Export the db structure (of a group) so I can setup my own crabcrass Feb 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant