-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
ess-legacy-v2Issues for ess-legacy-v2.Issues for ess-legacy-v2.good first issueGood for newcomersGood for newcomers
Description
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
essrepo (this repo) to another name and start a newessrepository. - Organize
ess*repositories'documentationto be in a subdirectory.
i.e.docs/should be underdocs/instruments/*ordocs/techniques/*including logos - Organize
ess*repositories'teststo be in a subdirectory.
i.e. tests should be undertests/instruments/*ortests/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 (?)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ess-legacy-v2Issues for ess-legacy-v2.Issues for ess-legacy-v2.good first issueGood for newcomersGood for newcomers