Skip to content

Bring back the ess mono-repo, merge all ess* projects into one repository. #7

@YooSunYoung

Description

@YooSunYoung

Reasons why we should bring back the mono repos

  • It is not easy to search for certain functionalities across different ess*packages in the documentation.
  • Dependencies between ess* packages not so easy to detect despite of nightly tests.

I think the mono-documentation, where we can search for all functionalities, will be more and more important.
It's not necessarily mono-repo problem but it will be easier to build the documentation if ess* are all in one repository.

Steps to merge repositories

- [ ] Clean up ess repository and make it up to date with the templates.

  • Rename the old ess repo (this repo) to another name and start a new ess repository.
  • Organize ess* repositories' documentation to be in a subdirectory.
    i.e. docs/ should be under docs/instruments/* or docs/techniques/* including logos
  • Organize ess* repositories' tests to be in a subdirectory.
    i.e. tests should be under tests/instruments/* or tests/techniques/*
  • Organize CI tests to have matrix per technique/instrument so that we can easily see which part of tests are failing. (?)
  • Merge repositories using git(?)
  • Remove ess_template (?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions