Mono-repo: xen-orchestra

[julien-f]

1. [x] merge repos
   • [x] xen-api
   • [x] xo-server-auth-google
   • [x] xo-server-transport-slack
   • [x] xo-server-vmdk-to-vhd
   • [x] xo-server
   • [x] xo (documentation)
   • [x] xapi-explore-sr
   • [x] xo-import-servers-csv
2. [x] move xo-web to packages/xo-web
3. [x] merge xen-orchestra into xo-web
4. [x] rename xo-web to xen-orchestra

Questions

• Figure out how to have a stable branch?

[julien-f]

For xo-server and xo-web, I'm afraid it will invalidate all open PRs…

[julien-f]

@Fohdeesha @Marcpezin @olivierlambert I would like to migrate XO documentation from xo to this (xen-orchestra) repo, any objections?

Why?

• regroup all XO stuff in one and only repo
• give the devs the ability (responsability) to update the doc when changing/adding a feature

[Fohdeesha]

I like it, it makes sense to have it in the repo of the code it is documenting. And a very good idea to encourage devs to update documentation when pushing changes as this can be forgotten sometimes. Mono repo means they could do both code changes and docu changes in the same PR