xOpera project is constantly evolving and bringing new parts, tools, functionalities. Because of that we also have more repositories that are connected directly with xOpera and they usually start with xopera-. To manage and to join all these parts I propose creating a new GitHub organization (we can call it xOpera or even something else if we decide to change the name) which would hold all the repositories connected to xOpera orchestrator. In the future we could have a bunch of tools in this organization like orchestrator, TOSCA parser, API, SaaS component, Template Library and so on.
Steps
For the start we would create a new GitHub organization and then transfer our current three repositories (within the xlab-si organization) that are connected to opera, which are:
Description
xOpera project is constantly evolving and bringing new parts, tools, functionalities. Because of that we also have more repositories that are connected directly with xOpera and they usually start with
xopera-. To manage and to join all these parts I propose creating a new GitHub organization (we can call it xOpera or even something else if we decide to change the name) which would hold all the repositories connected to xOpera orchestrator. In the future we could have a bunch of tools in this organization like orchestrator, TOSCA parser, API, SaaS component, Template Library and so on.Steps
For the start we would create a new GitHub organization and then transfer our current three repositories (within the xlab-si organization) that are connected to opera, which are:
xopera-operaxopera-examplesxopera-apixopera-docsWe can also drop the
xopera-prefix because it will be evident from the organization's name.Current behaviour
xOpera project's repositories are spreaded throughout
xlab-siorganization.Expected results
Gather all xOpera's repositories and connected tools and move them to new separate GitHub organization.