Hi Jeroen,
sorry but now I am even more confused than before. If Cycleone doesn't need any dependencies, then what are we talking about? I thought the main goal of using conan was about dependencies?
But just in case did misunderstand you, and you indeed need dependencies:
I still don't see the reason why you need a GitHub organization. Because from what I saw, conon is just a tool that will run. And the way you set it up with Travis and a single repository is just one way to set it up. You could very well put this into a single repository, maybe use different branches, or an all-in-one registry. And you could also use JIPP to build this, instead of Travis, …
And the whole description of "vendor neutral" that you just have, doesn't sound vendor neutral at all to me. If I would be a committer on the cyclonedds project, then I wouldn't have automatically permissions by this bintray repository, as you mentioned, that it is managed by adlink, and not by the Eclipse Foundation.
I think a good approach may be to start off small, and start building on JIPP. To me it looks like you can build all the dependencies you need e.g. with a Jenkins pipeline. That way it would even be self-contained. It could be replicated, doesn't require the management of additional outside services and could all be done in a single repository. Or two or three if you want to split it up. And it you then run into a real blocker, let's discuss what really required.
Cheers
Jens
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________
Red Hat GmbH,
www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill