Reference implementation library collaboration

[Arthur De Magalhaes]

Hey everyone,

If a few vendors / community members want to collaborate on a core library for a specific implementation, does it make sense to create a "reference_library" folder in the spec's GitHub repo?  

So it wouldn't be a full reference implementation, but a core library that vendors can use to get them 90% of the way there, and then they just have to plug-in vendor specific code around the edges.  

For example, in OpenAPI it would make sense to have a library that supports `reader` (annotations -> model, with filtering), `parser` (spec -> model) and `serialization` (model -> spec) .  

Keeping that vendor-neutral is the goal, so that's why I thought a good candidate would be inside a sibling folder to the spec.

Thoughts?

- Arthur

[Ondro Mihályi]

Hi,

We discussed this earlier and agreed that's sensible but an impl should be in a different repository.

It doesn't even have to be in an eclipse repository so that you don't have to undergo Eclipse IP validation and processes. You can create a new org on GitHub and add all collaborators to the org. It's up to you. But it's important that there's no impl coupled with the spec in the spec repository.

--Ondro

[Arthur De Magalhaes]

Sounds good.  Thanks for the info Ondro!

- Arthur