Initial Release of Amino - Open Source Repo and Ecosystem

[prostil]

• [ ] Move Amino.Run out of Huawei-PaaS organisation
• [x] Create a new account for documentation (readthedocs.io) use docs.amino.os@gmail.com
• [ ] Setup the Amino.Run GitHub account with readthedocs.io
• [ ] Setup DNS records for Amino documentation in readthedocs admin section
• [ ] Create the following documents
  • [ ] Getting started
  • [ ] General concepts Amino.Run, Amino.Sync, Amino.Store
  • [ ] OMS, KernalServer, DM, Multi DM, Replication, Automatic Migration architecture
  • [ ] Dev Setup
  • [ ] Guides to running example applications, logs
  • [ ] TroubleShooting
• [ ] Setup Travis CI for the open repo
  • [ ] Travis must build when a PR is raised
  • [ ] Travis reports to be attached with the PR
• [x] Create a slack channel
• [ ] Amino.run blog website
• [ ] Gmail mailing group --- These have been created help.amino.os, docs.amino.os, contributors.amino.os
• [ ] Twitter account -- I am not sure if this is a must but it helps in gettting more traction to the project See #654.

[prostil]

I have created a new account with readthedocs.io using this email address docs.amino.os@gmail.com As of now it is not pointing to any repository. Once we move Amino.Run out of Huawei-PaaS we can set it up Login credentials please check with @prostil

[prostil]

I have created a slack channel https://aminoos.slack.com/messages/CHVSVCC5R/ email used is contributors.amino.os@gmail.com

Login credentials please check with @prostil

[skdwriting]

1. Github:
   • Github org name (consistent with website)
   • Amino.Run Repo
     • Move the internal code here
     • Should we move code with all history or not, all issues or not...
     • Cleanup of code needed before moving?
       • Header - Copyright "2019 The Authors of Amino Distributed OS"
       • Header - License
       • General Quality cleanup
       • Folder Structure, including documentation, test
     • ReadMe - What , Why, links to documentation, Links to Join
     • Developers Guide / Contribution Guide
     • Roadmap -Usecases/Demo Repo
     • We add all demos here along with readme's -Add members, admin etc
2. Website: -Domain Name (consistent with github) -Front page with What , Why, may be architecture, possible usecases... -Menu - Documention, Blogs,... 3.Slack Channel -Consistent with repo -Add members -Admin settings

[skdwriting]

github.com/AminoDistributedOS -- available and created

aminodistributedos.com aminodistributedos.net aminodistributedos.org aminodistributedos.io available

[skdwriting]

@quinton-hoole , please check the above comments and confirm. Then we go.

[quinton-hoole]

I prefer the github name with the hyphens (https://github.com/amino-distributed-os), because github and others lower case it, so your proposal becomes aminodistributedos which is pretty unreadable (and as I’ve mentioned before, ‘dos’ has connotations of denial of services, and bad operating systems. We already have the following registered (in December), as I’ve mentioned: amino-os.io, amino-os.net, amino-os.org, amino-os.com. I think lets just use what we already have, and stop wasting time. I will move the Amino.Run repo from github.com/HuaweiPaaS to github.com/amino-distributed-os. That’s trivial. But first we need to remove all the bad docs from it. I will do that too.

[quinton-hoole]

For what it's worth, most of the orgs and repos in Kubernetes also contain dashes, so I'm not the only one who prefers that approach:

https://github.com/kubernetes-sigs https://github.com/kubernetes

perf-tests kube-state-metrics legacy-cloud-providers test-infra cloud-provider-openstack cloud-provider-azure kube-openapi ingress-gce ingress-nginx etc, etc

[quinton-hoole]

This is a duplicate of what #656 is supposed to be. Please don't create a separate set of unlinked issues. Either move this info to #656, or move #656 to here. Don't keep two separate issues without links between them. Closing this one.