On 28/01/2014 18:55, Eduard Koller (MS OPEN TECH) wrote:
I believe it makes sense to add the JS in a new repo, and the Java lib to the 
existing 4.0 one.
Francesco, what do you think?

I agree with you: I don't think that the JS library might ever share something significant with the Java artifacts, so a separate repository (olingojs?) makes sense to me.

About ODataJClient, it is currently 100% compatible V3 and we have recently started supporting the V4 spec, hence I'd say its best suiting repository is olingo4.

Regards.

-----Original Message-----
From: Klevenz, Stephan [mailto:[email protected]]
Sent: Tuesday, January 28, 2014 3:30 AM
To: [email protected]
Subject: Re: Contributing OData V3 Java client libraries to the Olingo project

Hi Eduard,

It could make sense to handle your contribution within a single process.
It could make things simpler.
@Mentors Please involve if you think different.

Currently we have 2 git repositories [1,2] to host code for OData 2.0 and
4.0 separately. Each repository stands for a release line where we have 
currently releases for OData 2.0 and no release for OData 4.0 yet.

If you plan to go with your client code only for OData 4.0 then it can be added 
to [2]. Alternatively you can request a own repository (just ask here on 
mailing list). For the javascript client it is maybe an option to have it in a 
separate repository. WDYT?

Regards,
Stephan


[1] OData 2.0:
https://git-wip-us.apache.org/repos/asf/incubator-olingo-odata2
[2] OData 4.0:
https://git-wip-us.apache.org/repos/asf/incubator-olingo-odata4
[3] Summary of project resources:
http://incubator.apache.org/projects/olingo.html




On 28.01.14 07:01, "Eduard Koller (MS OPEN TECH)" <[email protected]>
wrote:

Thank you for providing details, Stephan.
I will let you know as soon as I have the signed grant and ICLA in place.

I'd like to also contribute a JavaScript library for OData V3 (that can
be then extended to V4).
Should I include the Javascript library together with the Java library
as parts of one single process?

Thank you,
Eduard


-----Original Message-----
From: Klevenz, Stephan [mailto:[email protected]]
Sent: Monday, January 27, 2014 3:38 AM
To: [email protected]
Subject: Re: Contributing OData V3 Java client libraries to the Olingo
project

Eduard,

Your contribution is highly welcome. I am aware of this OData V3 client
code and it is really valuable to have this with Olingo.

>From my knowledge there are some formal aspects required for each
Apache contribution. Maybe mentors can hook in if I miss something.

Before you can contribute you have to sign a software grant an sent it
to Apache. For details see [1] and [2]. After that you can create a
Jira issue [3] and attach the source code as a zip or patch file to it.
For example have a look into our initial source contribution [4].

We also need a list of committers who want to join Apache Olingo. Each
of then has to sign a individual contributor license agreement (ICLA)
[5] and send it to Apache for getting a user account.

Francesco mentioned already that Olingo has started to work on OData
4.0 (EDM, ANTLR based URI parser) and your code will fit here. Apart of
the formal aspects above I suggest to have separated discussion how we
can achieve this technically.

Let us know if you have more questions to this.

Regards,
Stephan


[1] http://www.apache.org/licenses/
[2] http://www.apache.org/licenses/software-grant.txt
[3] https://issues.apache.org/jira/browse/OLINGO
[4] https://issues.apache.org/jira/browse/OLINGO-1
[5] http://www.apache.org/licenses/icla.txt



On 27.01.14 09:45, "Francesco Chicchiriccò" <[email protected]> wrote:

On 27/01/2014 05:09, Eduard Koller (MS OPEN TECH) wrote:
Hello,

I'd like to contribute to the Olingo project a set of Java client
libraries for Odata V3.

Can you please let me know what is the process the Olingo project
uses for such contributions?

The code is currently available at
https://github.com/MSOpenTech/ODataJClient/. If you have specific
questions about iy, I noticed that Francesco Chicchiriccò who wrote a
big part of this code is a member of Olingo and can provide details.
Hi there,
besides V3, we have already started the implementation of V4 at [1],
so I'd say contribution should come from there to olingo4 repository.

Regards.

[1] https://github.com/MSOpenTech/ODataJClient/tree/ODATA_4

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

Reply via email to