He has committed to GeoTools before, I did some research to check:
https://github.com/geotools/geotools/commits?author=ischneider

And yes, it was done by IanS as a Boundless employee. :)

On Thu, Oct 8, 2015 at 6:34 PM, Jody Garnett <[email protected]> wrote:

> If the work was done by IanS a boundless employee then we are all good. If
> not we check if he has a personal contribution agreement on file, or hunt
> him down and ask.
> On Thu, Oct 8, 2015 at 6:25 PM Travis Brundage <[email protected]>
> wrote:
>
>> Hey all,
>>
>> I'm looking to get some work done in a separate GeoTools branch back into
>> the community. This work was actually done a while back by Ian Schneider,
>> and since then has been rebased onto 12.x to be used elsewhere. I have the
>> branch here: https://github.com/travislbrundage/geotools/tree/xdate
>>
>> So for now what I was planning to do was cherry pick those top 3 commits
>> which contain the work and place them on master (ensuring it builds) to
>> finally give back as a pull request to the main repo.
>>
>> The only part that's really interesting here for me and which I am unsure
>> about is because this code is not actually written by me. Will I have to do
>> anything differently in this case? There are no new files involved, only
>> modified ones.
>>
>> Cheers,
>> Travis
>>
>> --
>> Travis Brundage
>> Software Engineer | Boundless
>> [email protected]
>> 250.888.2820
>> @boundlessgeo
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> GeoTools-Devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
> --
> --
> Jody Garnett
>



-- 
Travis Brundage
Software Engineer | Boundless
[email protected]
250.888.2820
@boundlessgeo
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to