...
3.1 Initial contact with EOSC-hub (Prospective service provider)
The prospective service provider Service Provider completes the Join as a provider form on the EOSC-hub website, providing high-level information about the service and motivation for joining. The submitted information becomes a ticket in Jira to track the request.
...
3.4.5 Marketplace integration (EOSC-hub Task 5.2)
A Marketplace representative is designated to guide new service representative. A form is provided to fill in the information about the service relevant from the Marketplace point of view. The guide and service representative work closely and at the same time the given form improves that in the end it can be self explanatory.
Provider gets to know other MP Services to analyse possible relations and dependencies.
Provider chooses a level of integration with the Marketplace and decides if the service wants to take part in the common service orders management process available (see Operational integration).The prospective Service Provider completes the Marketplace Service Description Template providing information relevant to the Marketplace. Other existing services on the marketplace are introduced that may be relevant and of interest for potential future integration.
3.4.5 Operational integration (EOSC-hub Task 4.1)
A nominated contact from the Service Provider is invited to engage with the Service Provider Forum by joining its mailing list and attending quarterly meetings. The Service Provider Forum is designed to facilitate communication between Service Providers and the EOSC-hub project, in addition to requirements gathering.
...