Closed pchainho closed 7 years ago
I would leave it for now as it is. The two locations are very topic specific (framework vs. runtime core). Moving things around at this stage of the project, i.e., close to the review and while writing deliverables might cause more issues than bringing benefits.
I would though support to start thinking about a structure for a single reTHINK repository that we create for the end of the project and that holds everything so that we can delete the other repositories. We have by far too many repositories already.
I understand your concerns @emmelmann-fokus but we would not delete the current location specs that would still be valid for phase 1 specs. The proposed specs repo would be for phase 2 ie we would collect phase 1 specs and copy to this new repo. On the other hand if you look into the framework specs it contains not just the framework specs but other specs transversal to several reTHINK elements eg the dynamic view and message specs covers at least Message Nodes, Runtime, Domain Registry and the Catalogue.
The data model spec itself is also transversal to reTHINK and would also be moved to this dedicated specs repo.
Regarding having a single reTHINK repo I don't think it is possible but we can try to reduce/improve its organisation. Anyway, I don't think having several repos for a project with such a broad scope as reTHINK is a big problem.
closing. any issue related with this new repo should be created there
Currently, specs are mainly provided in two separated repos (here and here). Having it in a dedicated repo (eg called "specs") would facilitate internal work and would also be easier for external parties interested to learn more about rethink.
@reTHINK-project/wp3 Let me know what you think