We've been given the green light to move the Topiary repository from the Tweag GitHub organisation to this new Topiary organisation, providing we maintain appropriate Tweag branding (e.g., in the README).

As far as branding is concerned, this is a triviality, so its discussion isn't necessary. (Moreover, Tweag branding already exists in the Topiary organisation's README, so we've already partially satisfied this.)

It occurs to me that this could be a worthwhile opportunity to breakup the Topiary monorepo to a certain extent. There are a few components which should probably not be in there; namely the playground and the website (and, perhaps, even the documentation/book). There is also topiary-opam (@Niols).

To dogfood the BUD process, let's initiate the discussion on what is and isn't in scope. Discussion points:

• Should we migrate tweag/topiary to topiary/topiary at all?

  Pros: Better discoverability; Topiary becomes a "first class" citizen, in a sense
  Cons: Indirect link back to Tweag; Everyone has to update their remotes; Non-trivial process

• If we migrate, which, if any, subcomponents should we break out of the monorepo in to their own repositories?

  • Topiary website?
  • Topiary playground?
  • Topiary Book and/or manpages?
  • Others?

• Open questions, if we migrate:

  • Should topiary-opam also be migrated and what changes are required, if done so?
  • Can we still use the Tweag Cachix account?
  • The website deployment will necessarily change, whether it's broken out from the monorepo or otherwise. I suspect this will just need a DNS change against topiary.tweag.io and appropriate GitHub Pages configuration, but I'm not completely sure! This isn't really a question...so, does anyone have any better ideas about this?