autonomic-cooperative
/
autonomic.zone
Archived
5
0
Fork 0
Code Issues 15 Pull Requests 2 Releases Activity

WIP: google-drive-blog-post #56

Draft
kawaiipunk wants to merge 4 commits from google-drive-blog-post into main
pull from: google-drive-blog-post
merge into: autonomic-cooperative:main
Conversation 0 Commits 4 Files Changed 1 +25
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
src/_posts/2021-02-11-google-drive.md Normal file
View File

@ -0,0 +1,25 @@
---
layout: post
title: Escaping the Google silo
description: Opening up your Google Drive and Docs files using open source software
image:
category: technology
date: 2021-02-11
---
At Autonomic we always promote using [libre software](https://en.wikipedia.org/wiki/Free_software) whereever possible but we understand that many clients have committed to using [propietary software](https://en.wikipedia.org/wiki/Proprietary_software) either due to legacy decision or because the non-libre solutions are simply more effective and mature.
decentral1se commented 2021-02-16 12:45:48 +00:00
Review
Copy Link

Ok, at this point, you've already used 3 terms to refer to the same thing.

  • open source software
  • libre software
  • free software (on the wiki page)

Stick with one, I'd say (any will do imho).

Ok, at this point, you've already used 3 terms to refer to the same thing. - open source software - libre software - free software (on the wiki page) Stick with one, I'd say (any will do imho).
decentral1se commented 2021-02-16 12:46:21 +00:00
Review
Copy Link

Also propietary -> proprietary

Also `propietary` -> `proprietary`
decentral1se commented 2021-02-16 12:46:48 +00:00
Review
Copy Link

decision -> decisions

`decision` -> `decisions`
The Google Workspace set of tools including Google Drive and Google Docs is one such solution. Once your organisation has deployed and is using these Google services, it's extremly difficult to migrate away. Google Docs files are not easy to extract from their propietary format and users are strongly encouragaged to only interact with the documents via the Google Workspace web apps.
decentral1se commented 2021-02-16 12:47:36 +00:00
Review
Copy Link

extremly-> extremely

`extremly`-> `extremely`
This is problematic for organisations that want to approach their data storage with a stratergy that suits them, rather than the Google™️ mandated workflow.
There are also [so many criticims](https://en.wikipedia.org/wiki/Criticism_of_Google) that could be made of Google in so many areas (as a [worker's co-operative of privacy advocates](/our-founding-principles), we're of course very biased).
There is also the question of [Google outages](https://en.wikipedia.org/wiki/2020_Google_services_outages) which happened multiple times in 2020. Of course, service outages can and do happen at any scale but it is interesting to note that they are even fairly regular occurance at many of the largest technology companies. When it comes to critical services, offering reduncancy and decentralisation is very difficult to do at the monolithic scale of the tech ginats.
decentral1se commented 2021-02-16 12:48:29 +00:00
Review
Copy Link

reduncancy -> redundancy

`reduncancy` -> `redundancy`
We have been working on a solution for a client to try and make it easier for organisatons to in the short term keep non-Google hosted copies of their data and in the long term, be in a better position to migrate away from Google Workspace all together. Luckily, there is an extensive [Drive](https://developers.google.com/drive/) and [Docs API](https://developers.google.com/docs/api/) which is well documentated and relativley stable.
Our system is designed to pull all of your data out of the Google [walled garden](https://en.wikipedia.org/wiki/Closed_platform) and directly into your control. We host a server for you which runs our code to extract all of your files from Google Drive and covert all of your Google Docs into open document formats (.odt .docx etc.). The files are then made available to your organisation as standard filesystem on your own [Nextcloud](https://nextcloud.com/) instance and then you can do what you want with them. You'll also be able to draw up a support contract with us that suits your needs for both maintaining the server and supporting your users.
We intend to release the source code for our system under a libre license as soon whens we feel it's ready but it still needs some cleaning up and documentation which takes time. When it's released, you'll be able to find on our [Gitea instance](https://git.autonomic.zone/autonomic-cooperative).
femmefaytale commented 2021-02-16 15:25:31 +00:00
Review
Copy Link

We haven't made any agreement with TSA about whether or not we can release this under a libre license at all, I don't think it's a good idea to make this promise quite yet!

We haven't made any agreement with TSA about whether or not we can release this under a libre license at all, I don't think it's a good idea to make this promise quite yet!
femmefaytale commented 2021-02-16 15:30:44 +00:00
Review
Copy Link

As a separate point I personally am very hesitant to say we'll release it as open source even with permission, given the state that the code is in. Not only does "some cleaning up and documentation" misrepresent the current code base in my mind but it might be best not to portray the product that we have told our client is completed as unifinished.

As a separate point I personally am very hesitant to say we'll release it as open source even with permission, given the state that the code is in. Not only does "some cleaning up and documentation" misrepresent the current code base in my mind but it might be best not to portray the product that we have told our client is completed as unifinished.
If you're interested in hosting this solution for your organsation, feel free to [get in touch](mailto:helo@autonomic.zone).