Moving DigitalOcean Spaces Storage Engine under upspin org

[alinz]

Hello, Thanks for this amazing project.

I have developed a storage-engine for digitalocean's spaces. I would like to ask if it is possible to move it under upspin org as it has more traffic and also it helps the adaptation of project.

Thanks,

[adg]

Sure, I think we could add a Digital Ocean repo. Is "do" the canonical abbreviation for Digital Ocean? I'd probably err on the side of something more explicit for a repository name (digitalocean.upspin.io perhaps). What do you think?

[alinz]

@adg thanks for the feed back, I think internally they refer to it as "do", here's the article that they describe their development source directory. However, digitalocean would be more explicit and it would be more obvious and less error-prone.

What is the procedure to transfer a repo to upspin org? Are you guys clone the repo and add it to org or use the github transfer ownership?

[adg]

Either 'digitalocean' or just 'ocean' would be unambiguous enough for my tastes.

cc @robpike do you have opinions/preferences for the new repository name?

What is the procedure to transfer a repo to upspin org? Are you guys clone the repo and add it to org or use the github transfer ownership?

I will create the repository and then ask you to send a change to add the code to that repo. You can then retire your github repo.

[robpike]

I would slightly prefer digitalocean but ocean is fine.

[alinz]

@adg whenever you create a repo, let me know so we can get this done.

[adg]

@alinz the repo has been created, you can check it out with:

$ go get -d digitalocean.upspin.io

and then follow our contribution instructions to send your changes as a Gerrit code review. Thank you so much!

[alinz]

@adg I have made a PR using upspin's gerrit. Thank you.

[palmamartin]

Following the comments on the PR 19180 maybe it makes sense to have a general S3 (cloud/storage/s3) backend, as Andrew suggested, which can be used for different S3 compatible backends like AWS, DO, Ceph,...?