You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Klevenz, Stephan" <st...@sap.com> on 2013/07/23 12:46:42 UTC
initial code contribution
@mentors
How does the initial code contribution works? I was thinking to create a Jira issue and attach the source code to it for documentation. This seems to be wrong because of attachments are not possible.
@all
Secondly some of us still struggle with ICLAs and do not have Apache users yet. Can someone else pick the code from (https://github.com/SAP/cloud-odata-java) and do the initial commit?
Regards,
Stephan
Re: initial code contribution
Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi,
initial code contribution is done:
https://git-wip-us.apache.org/repos/asf?p=incubator-olingo-odata2.git;a=tre
e;h=ff2b0a0eee6d196fb217ed14d740ca3aac8b6d33;hb=ff2b0a0eee6d196fb217ed14d74
0ca3aac8b6d33
-- Stephan
On 26.07.13 12:02, "Florian Müller" <fm...@apache.org> wrote:
> Hi,
>
> Looks good to me and ready for the initial check in.
> I'll help with the check in.
>
>
> - Florian
>
>
>> On Jul 25, 2013, at 5:52 PM, Dave Fisher wrote:
>>
>>> Hi,
>>>
>>> With my mentor hat on.
>>>
>>> The project should check in the code as it is granted.
>>>
>>> Then someone in the project who works for SAP should make the header
>>> changes.
>>
>> I see that the changes are all made and that the OLINGO-1 has the
>> provenance. Great!
>>
>>>
>>> The most important part of the first release for this podling is
>>> make sure that the headers are correct. The ASF has a tool that helps
>>> called Apache RAT. It can be found here: http://creadur.apache.org/
>>
>> This will be a useful monitoring tool.
>>
>> Regards,
>> Dave
>>
>>
>>>
>>> Regards,
>>> Dave
>>>
>>> On Jul 23, 2013, at 9:14 AM, Florian Müller wrote:
>>>
>>>> Hi Stephan,
>>>>
>>>> Before we check the code into the Apache Git, we should make a few
>>>> general changes to it.
>>>> We should have at least the Apache header in each source file. It
>>>> would
>>>> also be good to change package names to something like
>>>> "org.apache.olingo...".
>>>>
>>>>
>>>> Florian
>>>>
>>>>
>>>>> I found the attach button, so code is available as ZIP here:
>>>>>
>>>>> https://issues.apache.org/jira/browse/OLINGO-1
>>>>>
>>>>> I have taken the latest version from GitHUB. The ZIP doesn't
>>>>> contain the
>>>>> history and it is not refactored yet. We can do this as community
>>>>> task.
>>>>>
>>>>> - Stephan
>>>>>
>>>>>
>>>>> On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> First question for me, what should be included in the "Initial
>>>>>> commit"?
>>>>>> In my opinion we should check in the current code base without
>>>>>> the
>>>>>> complete 'git' history.
>>>>>> What do you think?
>>>>>>
>>>>>> @Stephan:
>>>>>> You can attach files to your issue
>>>>>> (https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions
>>>>>> -> Attach
>>>>>> Files"), but only to a maximum of 10MB. Enough for the code, but
>>>>>> not for
>>>>>> the 'git' history.
>>>>>>
>>>>>> Kind regards,
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>> On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com>
>>>>>> wrote:
>>>>>>
>>>>>>> @mentors
>>>>>>> How does the initial code contribution works? I was thinking to
>>>>>>> create a
>>>>>>> Jira issue and attach the source code to it for documentation.
>>>>>>> This seems
>>>>>>> to be wrong because of attachments are not possible.
>>>>>>>
>>>>>>> @all
>>>>>>> Secondly some of us still struggle with ICLAs and do not have
>>>>>>> Apache
>>>>>>> users yet. Can someone else pick the code from
>>>>>>> (https://github.com/SAP/cloud-odata-java) and do the initial
>>>>>>> commit?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Stephan
>>>>>>>
>>>>>
>>>>>
>>>
>
Re: initial code contribution
Posted by Florian Müller <fm...@apache.org>.
Hi,
Looks good to me and ready for the initial check in.
I'll help with the check in.
- Florian
> On Jul 25, 2013, at 5:52 PM, Dave Fisher wrote:
>
>> Hi,
>>
>> With my mentor hat on.
>>
>> The project should check in the code as it is granted.
>>
>> Then someone in the project who works for SAP should make the header
>> changes.
>
> I see that the changes are all made and that the OLINGO-1 has the
> provenance. Great!
>
>>
>> The most important part of the first release for this podling is
>> make sure that the headers are correct. The ASF has a tool that helps
>> called Apache RAT. It can be found here: http://creadur.apache.org/
>
> This will be a useful monitoring tool.
>
> Regards,
> Dave
>
>
>>
>> Regards,
>> Dave
>>
>> On Jul 23, 2013, at 9:14 AM, Florian Müller wrote:
>>
>>> Hi Stephan,
>>>
>>> Before we check the code into the Apache Git, we should make a few
>>> general changes to it.
>>> We should have at least the Apache header in each source file. It
>>> would
>>> also be good to change package names to something like
>>> "org.apache.olingo...".
>>>
>>>
>>> Florian
>>>
>>>
>>>> I found the attach button, so code is available as ZIP here:
>>>>
>>>> https://issues.apache.org/jira/browse/OLINGO-1
>>>>
>>>> I have taken the latest version from GitHUB. The ZIP doesn't
>>>> contain the
>>>> history and it is not refactored yet. We can do this as community
>>>> task.
>>>>
>>>> - Stephan
>>>>
>>>>
>>>> On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> First question for me, what should be included in the "Initial
>>>>> commit"?
>>>>> In my opinion we should check in the current code base without
>>>>> the
>>>>> complete 'git' history.
>>>>> What do you think?
>>>>>
>>>>> @Stephan:
>>>>> You can attach files to your issue
>>>>> (https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions
>>>>> -> Attach
>>>>> Files"), but only to a maximum of 10MB. Enough for the code, but
>>>>> not for
>>>>> the 'git' history.
>>>>>
>>>>> Kind regards,
>>>>> Michael
>>>>>
>>>>>
>>>>> On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com>
>>>>> wrote:
>>>>>
>>>>>> @mentors
>>>>>> How does the initial code contribution works? I was thinking to
>>>>>> create a
>>>>>> Jira issue and attach the source code to it for documentation.
>>>>>> This seems
>>>>>> to be wrong because of attachments are not possible.
>>>>>>
>>>>>> @all
>>>>>> Secondly some of us still struggle with ICLAs and do not have
>>>>>> Apache
>>>>>> users yet. Can someone else pick the code from
>>>>>> (https://github.com/SAP/cloud-odata-java) and do the initial
>>>>>> commit?
>>>>>>
>>>>>> Regards,
>>>>>> Stephan
>>>>>>
>>>>
>>>>
>>
Re: initial code contribution
Posted by Dave Fisher <da...@comcast.net>.
On Jul 25, 2013, at 5:52 PM, Dave Fisher wrote:
> Hi,
>
> With my mentor hat on.
>
> The project should check in the code as it is granted.
>
> Then someone in the project who works for SAP should make the header changes.
I see that the changes are all made and that the OLINGO-1 has the provenance. Great!
>
> The most important part of the first release for this podling is make sure that the headers are correct. The ASF has a tool that helps called Apache RAT. It can be found here: http://creadur.apache.org/
This will be a useful monitoring tool.
Regards,
Dave
>
> Regards,
> Dave
>
> On Jul 23, 2013, at 9:14 AM, Florian Müller wrote:
>
>> Hi Stephan,
>>
>> Before we check the code into the Apache Git, we should make a few
>> general changes to it.
>> We should have at least the Apache header in each source file. It would
>> also be good to change package names to something like
>> "org.apache.olingo...".
>>
>>
>> Florian
>>
>>
>>> I found the attach button, so code is available as ZIP here:
>>>
>>> https://issues.apache.org/jira/browse/OLINGO-1
>>>
>>> I have taken the latest version from GitHUB. The ZIP doesn't contain the
>>> history and it is not refactored yet. We can do this as community task.
>>>
>>> - Stephan
>>>
>>>
>>> On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>> First question for me, what should be included in the "Initial commit"?
>>>> In my opinion we should check in the current code base without the
>>>> complete 'git' history.
>>>> What do you think?
>>>>
>>>> @Stephan:
>>>> You can attach files to your issue
>>>> (https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions -> Attach
>>>> Files"), but only to a maximum of 10MB. Enough for the code, but not for
>>>> the 'git' history.
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>
>>>> On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com> wrote:
>>>>
>>>>> @mentors
>>>>> How does the initial code contribution works? I was thinking to create a
>>>>> Jira issue and attach the source code to it for documentation. This seems
>>>>> to be wrong because of attachments are not possible.
>>>>>
>>>>> @all
>>>>> Secondly some of us still struggle with ICLAs and do not have Apache
>>>>> users yet. Can someone else pick the code from
>>>>> (https://github.com/SAP/cloud-odata-java) and do the initial commit?
>>>>>
>>>>> Regards,
>>>>> Stephan
>>>>>
>>>
>>>
>
Re: initial code contribution
Posted by "Klevenz, Stephan" <st...@sap.com>.
The rat check is now part of build execution and can be activated by this
profile:
mvn clean install -Pbuild.quality
Furthermore I added following excludes where it is not possible or not
necessary to add a license:
<exclude>**/MANIFEST.MF</exclude> // no comment possible
<exclude>.gitignore</exclude> // not possible
<exclude>.git/**</exclude> // not necessary
<exclude>bin/**</exclude> // generated
<exclude>**/*.project</exclude> // generated
<exclude>**/*.classpath</exclude> // generated
<exclude>**/*.json</exclude> // no comment possible (test data)
<exclude>**/*.batch</exclude> // no comment possible (OData
batch, test data)
The rat check seems to be ok now and there are no issues reported.
I am going to setup another build job for quality check that runs at least
once a day.
-- Stephan
On 01.08.13 09:13, "Alan Cabrera" <li...@toolazydogs.com> wrote:
>
>On Jul 26, 2013, at 1:52 AM, Dave Fisher <da...@comcast.net> wrote:
>
>> The most important part of the first release for this podling is make
>>sure that the headers are correct. The ASF has a tool that helps called
>>Apache RAT. It can be found here: http://creadur.apache.org/
>
>Since the project is on Maven one can run:
>
>mvn rat:check
>
>to make sure the project's files are conforming to ASF requirements.
>
>
>Regards,
>Alan
>
Re: initial code contribution
Posted by Alan Cabrera <li...@toolazydogs.com>.
On Jul 26, 2013, at 1:52 AM, Dave Fisher <da...@comcast.net> wrote:
> The most important part of the first release for this podling is make sure that the headers are correct. The ASF has a tool that helps called Apache RAT. It can be found here: http://creadur.apache.org/
Since the project is on Maven one can run:
mvn rat:check
to make sure the project's files are conforming to ASF requirements.
Regards,
Alan
Re: initial code contribution
Posted by Dave Fisher <da...@comcast.net>.
Hi,
With my mentor hat on.
The project should check in the code as it is granted.
Then someone in the project who works for SAP should make the header changes.
The most important part of the first release for this podling is make sure that the headers are correct. The ASF has a tool that helps called Apache RAT. It can be found here: http://creadur.apache.org/
Regards,
Dave
On Jul 23, 2013, at 9:14 AM, Florian Müller wrote:
> Hi Stephan,
>
> Before we check the code into the Apache Git, we should make a few
> general changes to it.
> We should have at least the Apache header in each source file. It would
> also be good to change package names to something like
> "org.apache.olingo...".
>
>
> Florian
>
>
>> I found the attach button, so code is available as ZIP here:
>>
>> https://issues.apache.org/jira/browse/OLINGO-1
>>
>> I have taken the latest version from GitHUB. The ZIP doesn't contain the
>> history and it is not refactored yet. We can do this as community task.
>>
>> - Stephan
>>
>>
>> On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>>
>>> Hi,
>>>
>>>
>>> First question for me, what should be included in the "Initial commit"?
>>> In my opinion we should check in the current code base without the
>>> complete 'git' history.
>>> What do you think?
>>>
>>> @Stephan:
>>> You can attach files to your issue
>>> (https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions -> Attach
>>> Files"), but only to a maximum of 10MB. Enough for the code, but not for
>>> the 'git' history.
>>>
>>> Kind regards,
>>> Michael
>>>
>>>
>>> On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com> wrote:
>>>
>>>> @mentors
>>>> How does the initial code contribution works? I was thinking to create a
>>>> Jira issue and attach the source code to it for documentation. This seems
>>>> to be wrong because of attachments are not possible.
>>>>
>>>> @all
>>>> Secondly some of us still struggle with ICLAs and do not have Apache
>>>> users yet. Can someone else pick the code from
>>>> (https://github.com/SAP/cloud-odata-java) and do the initial commit?
>>>>
>>>> Regards,
>>>> Stephan
>>>>
>>
>>
Re: initial code contribution
Posted by "Klevenz, Stephan" <st...@sap.com>.
I have attached another zip with refactored code:
+ org.apache.olingo
+ Apache license header to all files
- Stephan
On 24.07.13 09:41, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi Stephan,
>It's fine with me.
>
>Kind Regards
>Chandan VA
>
>
>-----Original Message-----
>From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
>Sent: Wednesday, July 24, 2013 1:02 PM
>To: dev@olingo.incubator.apache.org
>Subject: Re: initial code contribution
>
>Hi,
>
>I suggest to do as Florian has proposed. I will do another ZIP with
>packaging org.apache.olingo + Apache header. All the rest can be community
>work.
>
>WDYT?
>
>Stephan
>
>On 24.07.13 07:43, "V.A, Chandan" <ch...@sap.com> wrote:
>
>>Hi all,
>>We need to refactor not just the package name but also the artifact id in
>>case of JPA processor library.
>>
>>@Stephan,
>>You had initially proposed changes to artifact id in case of JPA
>>processor library to align with OData Lib. Do we need to do that now in
>>GITHUB first or do it after initial commit.
>>
>>
>>Thanks,
>>Kind Regards
>>Chandan VA
>>
>>-----Original Message-----
>>From: Bolz, Michael [mailto:michael.bolz@sap.com]
>>Sent: Tuesday, July 23, 2013 11:39 PM
>>To: dev@olingo.incubator.apache.org
>>Subject: Re: initial code contribution
>>
>>Hi Florian,
>>
>>Wouldn't it be better to do it after the initial commit?
>>So we have this part of history which could help to link to the (a little
>>messy) history on GitHub.
>>
>>Or we do the changes on GitHub on then do the initial commit. I think
>>this
>>could be a good solution.
>>
>>By the way I have attached a small script for package renaming to the
>>JIRA
>>issue.
>>
>>Kind regards,
>>Michael
>>
>>
>>
>>On 23.07.13 18:14, "Florian Müller" <fm...@apache.org> wrote:
>>
>>>Hi Stephan,
>>>
>>>Before we check the code into the Apache Git, we should make a few
>>>general changes to it.
>>>We should have at least the Apache header in each source file. It would
>>>also be good to change package names to something like
>>>"org.apache.olingo...".
>>>
>>>
>>>Florian
>>>
>>>
>>>>
>>
>
RE: initial code contribution
Posted by "V.A, Chandan" <ch...@sap.com>.
Hi Stephan,
It's fine with me.
Kind Regards
Chandan VA
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Wednesday, July 24, 2013 1:02 PM
To: dev@olingo.incubator.apache.org
Subject: Re: initial code contribution
Hi,
I suggest to do as Florian has proposed. I will do another ZIP with
packaging org.apache.olingo + Apache header. All the rest can be community
work.
WDYT?
Stephan
On 24.07.13 07:43, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi all,
>We need to refactor not just the package name but also the artifact id in
>case of JPA processor library.
>
>@Stephan,
>You had initially proposed changes to artifact id in case of JPA
>processor library to align with OData Lib. Do we need to do that now in
>GITHUB first or do it after initial commit.
>
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Bolz, Michael [mailto:michael.bolz@sap.com]
>Sent: Tuesday, July 23, 2013 11:39 PM
>To: dev@olingo.incubator.apache.org
>Subject: Re: initial code contribution
>
>Hi Florian,
>
>Wouldn't it be better to do it after the initial commit?
>So we have this part of history which could help to link to the (a little
>messy) history on GitHub.
>
>Or we do the changes on GitHub on then do the initial commit. I think this
>could be a good solution.
>
>By the way I have attached a small script for package renaming to the JIRA
>issue.
>
>Kind regards,
>Michael
>
>
>
>On 23.07.13 18:14, "Florian Müller" <fm...@apache.org> wrote:
>
>>Hi Stephan,
>>
>>Before we check the code into the Apache Git, we should make a few
>>general changes to it.
>>We should have at least the Apache header in each source file. It would
>>also be good to change package names to something like
>>"org.apache.olingo...".
>>
>>
>>Florian
>>
>>
>>>
>
Re: initial code contribution
Posted by "Klevenz, Stephan" <st...@sap.com>.
Hi,
I suggest to do as Florian has proposed. I will do another ZIP with
packaging org.apache.olingo + Apache header. All the rest can be community
work.
WDYT?
Stephan
On 24.07.13 07:43, "V.A, Chandan" <ch...@sap.com> wrote:
>Hi all,
>We need to refactor not just the package name but also the artifact id in
>case of JPA processor library.
>
>@Stephan,
>You had initially proposed changes to artifact id in case of JPA
>processor library to align with OData Lib. Do we need to do that now in
>GITHUB first or do it after initial commit.
>
>
>Thanks,
>Kind Regards
>Chandan VA
>
>-----Original Message-----
>From: Bolz, Michael [mailto:michael.bolz@sap.com]
>Sent: Tuesday, July 23, 2013 11:39 PM
>To: dev@olingo.incubator.apache.org
>Subject: Re: initial code contribution
>
>Hi Florian,
>
>Wouldn't it be better to do it after the initial commit?
>So we have this part of history which could help to link to the (a little
>messy) history on GitHub.
>
>Or we do the changes on GitHub on then do the initial commit. I think this
>could be a good solution.
>
>By the way I have attached a small script for package renaming to the JIRA
>issue.
>
>Kind regards,
>Michael
>
>
>
>On 23.07.13 18:14, "Florian Müller" <fm...@apache.org> wrote:
>
>>Hi Stephan,
>>
>>Before we check the code into the Apache Git, we should make a few
>>general changes to it.
>>We should have at least the Apache header in each source file. It would
>>also be good to change package names to something like
>>"org.apache.olingo...".
>>
>>
>>Florian
>>
>>
>>>
>
RE: initial code contribution
Posted by "V.A, Chandan" <ch...@sap.com>.
Hi all,
We need to refactor not just the package name but also the artifact id in case of JPA processor library.
@Stephan,
You had initially proposed changes to artifact id in case of JPA processor library to align with OData Lib. Do we need to do that now in GITHUB first or do it after initial commit.
Thanks,
Kind Regards
Chandan VA
-----Original Message-----
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Tuesday, July 23, 2013 11:39 PM
To: dev@olingo.incubator.apache.org
Subject: Re: initial code contribution
Hi Florian,
Wouldn't it be better to do it after the initial commit?
So we have this part of history which could help to link to the (a little
messy) history on GitHub.
Or we do the changes on GitHub on then do the initial commit. I think this
could be a good solution.
By the way I have attached a small script for package renaming to the JIRA
issue.
Kind regards,
Michael
On 23.07.13 18:14, "Florian Müller" <fm...@apache.org> wrote:
>Hi Stephan,
>
>Before we check the code into the Apache Git, we should make a few
>general changes to it.
>We should have at least the Apache header in each source file. It would
>also be good to change package names to something like
>"org.apache.olingo...".
>
>
>Florian
>
>
>>
Re: initial code contribution
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Florian,
Wouldn't it be better to do it after the initial commit?
So we have this part of history which could help to link to the (a little
messy) history on GitHub.
Or we do the changes on GitHub on then do the initial commit. I think this
could be a good solution.
By the way I have attached a small script for package renaming to the JIRA
issue.
Kind regards,
Michael
On 23.07.13 18:14, "Florian Müller" <fm...@apache.org> wrote:
>Hi Stephan,
>
>Before we check the code into the Apache Git, we should make a few
>general changes to it.
>We should have at least the Apache header in each source file. It would
>also be good to change package names to something like
>"org.apache.olingo...".
>
>
>Florian
>
>
>>
Re: initial code contribution
Posted by Florian Müller <fm...@apache.org>.
Hi Stephan,
Before we check the code into the Apache Git, we should make a few
general changes to it.
We should have at least the Apache header in each source file. It would
also be good to change package names to something like
"org.apache.olingo...".
Florian
> I found the attach button, so code is available as ZIP here:
>
> https://issues.apache.org/jira/browse/OLINGO-1
>
> I have taken the latest version from GitHUB. The ZIP doesn't contain the
> history and it is not refactored yet. We can do this as community task.
>
> - Stephan
>
>
> On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>
>> Hi,
>>
>>
>> First question for me, what should be included in the "Initial commit"?
>> In my opinion we should check in the current code base without the
>> complete 'git' history.
>> What do you think?
>>
>> @Stephan:
>> You can attach files to your issue
>> (https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions -> Attach
>> Files"), but only to a maximum of 10MB. Enough for the code, but not for
>> the 'git' history.
>>
>> Kind regards,
>> Michael
>>
>>
>> On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com> wrote:
>>
>>> @mentors
>>> How does the initial code contribution works? I was thinking to create a
>>> Jira issue and attach the source code to it for documentation. This seems
>>> to be wrong because of attachments are not possible.
>>>
>>> @all
>>> Secondly some of us still struggle with ICLAs and do not have Apache
>>> users yet. Can someone else pick the code from
>>> (https://github.com/SAP/cloud-odata-java) and do the initial commit?
>>>
>>> Regards,
>>> Stephan
>>>
>
>
Re: initial code contribution
Posted by "Klevenz, Stephan" <st...@sap.com>.
I found the attach button, so code is available as ZIP here:
https://issues.apache.org/jira/browse/OLINGO-1
I have taken the latest version from GitHUB. The ZIP doesn't contain the
history and it is not refactored yet. We can do this as community task.
- Stephan
On 23.07.13 13:00, "Bolz, Michael" <mi...@sap.com> wrote:
>Hi,
>
>
>First question for me, what should be included in the "Initial commit"?
>In my opinion we should check in the current code base without the
>complete 'git' history.
>What do you think?
>
>@Stephan:
>You can attach files to your issue
>(https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions -> Attach
>Files"), but only to a maximum of 10MB. Enough for the code, but not for
>the 'git' history.
>
>Kind regards,
>Michael
>
>
>On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com> wrote:
>
>>@mentors
>>How does the initial code contribution works? I was thinking to create a
>>Jira issue and attach the source code to it for documentation. This seems
>>to be wrong because of attachments are not possible.
>>
>>@all
>>Secondly some of us still struggle with ICLAs and do not have Apache
>>users yet. Can someone else pick the code from
>>(https://github.com/SAP/cloud-odata-java) and do the initial commit?
>>
>>Regards,
>>Stephan
>>
>
Re: initial code contribution
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi,
First question for me, what should be included in the "Initial commit"?
In my opinion we should check in the current code base without the
complete 'git' history.
What do you think?
@Stephan:
You can attach files to your issue
(https://issues.apache.org/jira/browse/OLINGO-1 -> "More Actions -> Attach
Files"), but only to a maximum of 10MB. Enough for the code, but not for
the 'git' history.
Kind regards,
Michael
On 23.07.13 12:46, "Klevenz, Stephan" <st...@sap.com> wrote:
>@mentors
>How does the initial code contribution works? I was thinking to create a
>Jira issue and attach the source code to it for documentation. This seems
>to be wrong because of attachments are not possible.
>
>@all
>Secondly some of us still struggle with ICLAs and do not have Apache
>users yet. Can someone else pick the code from
>(https://github.com/SAP/cloud-odata-java) and do the initial commit?
>
>Regards,
>Stephan
>