WIP: google-drive-blog-post #56

Draft
kawaiipunk wants to merge 4 commits from google-drive-blog-post into main
Owner
No description provided.
kawaiipunk added 2 commits 2021-02-16 12:18:26 +00:00
kawaiipunk added 1 commit 2021-02-16 12:19:27 +00:00
decentral1se requested changes 2021-02-16 12:50:16 +00:00
decentral1se left a comment
Owner

LGTM! Thanks for writing!

I would personally just publish the unfinished source code because the more eyes the better for getting into a finished state. People can already then take it for a test ride or review it. That is up to the ones who wrote it though.

LGTM! Thanks for writing! I would personally just publish the unfinished source code because the more eyes the better for getting into a finished state. People can already then take it for a test ride or review it. That is up to the ones who wrote it though.
@ -0,0 +7,4 @@
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.

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).

Also propietary -> proprietary

Also `propietary` -> `proprietary`

decision -> decisions

`decision` -> `decisions`
@ -0,0 +9,4 @@
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.
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.

extremly-> extremely

`extremly`-> `extremely`
@ -0,0 +14,4 @@
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.

reduncancy -> redundancy

`reduncancy` -> `redundancy`
femmefaytale reviewed 2021-02-16 15:25:31 +00:00
@ -0,0 +20,4 @@
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).

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 reviewed 2021-02-16 15:30:44 +00:00
@ -0,0 +21,4 @@
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).

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.
decentral1se added 1 commit 2021-05-10 08:31:06 +00:00
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: autonomic-cooperative/autonomic.zone#56
No description provided.