Migration of Additional Geode Code

[Dan Smith <ds...@pivotal.io>]

I created an umbrella issue to track all of the remaining geode code that
pivotal intends to open source:

https://issues.apache.org/jira/browse/GEODE-8

Unfortunately this code is going to become available as larger chunks
rather than individual commits because these features were already being
developed internally when geode entered incubation. A few of these features
are still in development and I'm hoping they can get turned into geode
feature branches and see some development here.

What are the communities thoughts on the process for reviewing/accepting
this code? Create a feature branch and post the changes for review like any
other commit (once we iron out that process)?

In the spirit of full disclosure, the GemFire development team has been
cranking away since the initial geode drop and is currently working on a
codebase that is downstream of offheap (
https://issues.apache.org/jira/browse/GEODE-7). Getting that codebase
merged is probably going to be key getting those committers fully switched
over to working directly on geode.

-Dan

Re: Migration of Additional Geode Code

[Pid <pi...@pidster.com>]

On 08/05/2015 17:23, Roman Shaposhnik wrote:
> On Fri, May 8, 2015 at 12:59 AM, Pid <pi...@pidster.com> wrote:
>> On 07/05/2015 22:55, Dan Smith wrote:
>>> I created an umbrella issue to track all of the remaining geode code that
>>> pivotal intends to open source:
>>>
>>> https://issues.apache.org/jira/browse/GEODE-8
>>>
>>> Unfortunately this code is going to become available as larger chunks
>>> rather than individual commits because these features were already being
>>> developed internally when geode entered incubation. A few of these features
>>> are still in development and I'm hoping they can get turned into geode
>>> feature branches and see some development here.
>>
>> +1
>>
>>
>>> What are the communities thoughts on the process for reviewing/accepting
>>> this code? Create a feature branch and post the changes for review like any
>>> other commit (once we iron out that process)?
>>
>> That would be a good way to transition development to Geode, but it
>> would also be nice to exercise whatever process we are going to have for
>> significant contributions.
> 
> I think this one is somewhat special though. In a way, we're grandfathering
> code in that was developed during the past month or so while we were waiting
> to migrate to ASF infra. In a way, the best option would've been to ingest
> that code into our repo to begin with, but since SGA covered a particular
> tarball we now have to catch up.

I don't have a strong preference; at this point anything happening is an
opportunity to figure stuff out - but I would like more people to join
this thread.

Roman & I will get bored of talking to each other fairly quickly.  ;)


p

> Thanks,
> Roman.
> 


-- 

[key:62590808]

Re: Migration of Additional Geode Code

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Fri, May 8, 2015 at 12:59 AM, Pid <pi...@pidster.com> wrote:
> On 07/05/2015 22:55, Dan Smith wrote:
>> I created an umbrella issue to track all of the remaining geode code that
>> pivotal intends to open source:
>>
>> https://issues.apache.org/jira/browse/GEODE-8
>>
>> Unfortunately this code is going to become available as larger chunks
>> rather than individual commits because these features were already being
>> developed internally when geode entered incubation. A few of these features
>> are still in development and I'm hoping they can get turned into geode
>> feature branches and see some development here.
>
> +1
>
>
>> What are the communities thoughts on the process for reviewing/accepting
>> this code? Create a feature branch and post the changes for review like any
>> other commit (once we iron out that process)?
>
> That would be a good way to transition development to Geode, but it
> would also be nice to exercise whatever process we are going to have for
> significant contributions.

I think this one is somewhat special though. In a way, we're grandfathering
code in that was developed during the past month or so while we were waiting
to migrate to ASF infra. In a way, the best option would've been to ingest
that code into our repo to begin with, but since SGA covered a particular
tarball we now have to catch up.

Thanks,
Roman.

Re: Migration of Additional Geode Code

[Pid <pi...@pidster.com>]

On 07/05/2015 22:55, Dan Smith wrote:
> I created an umbrella issue to track all of the remaining geode code that
> pivotal intends to open source:
> 
> https://issues.apache.org/jira/browse/GEODE-8
> 
> Unfortunately this code is going to become available as larger chunks
> rather than individual commits because these features were already being
> developed internally when geode entered incubation. A few of these features
> are still in development and I'm hoping they can get turned into geode
> feature branches and see some development here.

+1


> What are the communities thoughts on the process for reviewing/accepting
> this code? Create a feature branch and post the changes for review like any
> other commit (once we iron out that process)?

That would be a good way to transition development to Geode, but it
would also be nice to exercise whatever process we are going to have for
significant contributions.


p


> In the spirit of full disclosure, the GemFire development team has been
> cranking away since the initial geode drop and is currently working on a
> codebase that is downstream of offheap (
> https://issues.apache.org/jira/browse/GEODE-7). Getting that codebase
> merged is probably going to be key getting those committers fully switched
> over to working directly on geode.
> 
> -Dan
> 


-- 

[key:62590808]