Hello Olingo Dev Team, I am writing on behalf of the JayData team at jaystack.com. We have been heavily investing in OData in the past years - almost exclusively on the JavaScript side. In the past we created JayData - one of the notable JS tools for V1-V3 OData with is idiomatic approach.. Unfortunately we could not catch up with V4 because of resources issues. These issues has been battled - and we managed to pull in a sizable investment money (in the range of $2m) to help our dreams come true. Which is providing a full suite of ODataV4 client and server tools for JavaScript.
For this purpose we would like to continue using olingo-odata-js, as a protocol level driver - as we did it in the past. Unfortunately this piece, the odata-v4-js library seems kind of abandoned. No changes for more then a half year and the npm package is definitely broken on npm 3.x. (especially the RAT package is not working - which is a particularly unfortunate thing, as RAT does not add to the olingo functionality just renders it broken). Also there are a number of issues in the current implementation which we consider bugs. Our humble question is: is there a way for us to actively contribute to odata-v4-js, potentially maintaining this on a daily basis with a dedicated dev team of 2-3 developers? How governance works? What should be our next steps? Thanks for any help on this yours sincerely Peter Aron Zentai OBO the JayData team Sent from Windows Mail
