Re: [udig-dev] initial code check-in

[andrea antonello <andrea.antonello@xxxxxxxxx>]

Ok, since people are coming in late and also ask for time changes, I
now created a doodle to handle this.
I also changed the meeting day to postpone the whole thing.

Proposals are here:
http://doodle.com/xwtt6a92vxzdd95d

If you need different timeslots to be added, please speak now and I
will add them.

Please consider seriously to participate to this meeting, I think it
is an important one for the future of uDig.

All the best,
Andrea


On Sun, Jan 11, 2015 at 4:54 AM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
> I would be happy to meet next week (although that time is 2 hours to early
> for me).
>
> I am considering going to the osgeo sprint (early feb) to work on uDig. I
> had originally intended to work with the GeoServer team but the date is too
> close to foss4g-na.  If I can arrange to go I would be focused on incubation
> with an eye towards steps 2-4 on location tech repo.
>
> Aside: thus far GeoTools 11.2 is going through Eclipse IP is reasonable
> fashion (much to my surprise). I had expected to need to patch an issue or
> two before it would be accepted.
> --
> Jody
> --
> Jody
>
> --
> Jody Garnett
>
> On 7 January 2015 at 11:34, Frank Gasdorf <fgdrf@xxxxxxxxxxxxxxxxxxxxx>
> wrote:
>>
>> Andrea, All,
>>
>> At the moment of writing we have the following situation:
>>
>> master branch is prepared for release with 3rd-party dependencies
>>
>> eclipse Indigo (3.7.2)
>> geotools 11.2
>> geoscript 1.3.1
>>
>> luna-support branch:
>>
>> eclipse luna (4.4.1)
>> geotools 9.0-M0
>> geoscript 1.1-M0
>>
>> next steps from my point of view:
>>
>> final 2.0.0 Release from master branch - the last Indigo based release
>> in parallel update (rebase) luna-support branch to latest state of master.
>> merge changes back to master branch and finally
>> create a - lets say 3.0.0 - release based on Luna (with gt 11.2 and
>> geoscript 1.3.1)
>>
>> While writing these lines I noticed that we lost gdal support because
>> imageio-ext has bindings for 1.9.2 while we currently provide JRE's with
>> gdal 1.7.3. So this may be a task prior 2.0.0 Release.
>>
>> The follow-up question is, do we provide OpenJDK JRE's or do we use Oracle
>> JRE's. In addition, since Java 1.6. is discontinued its worth to think about
>> at JRE 1.7
>>
>> After that I would suggest to move to locationtech github repository for
>> master.
>>
>> Thank you Andrea for providing the proposed IRC meetup. I guess I can make
>> it but would prefer an hour earlier
>>
>> Hope my wrap up makes sense to you.
>>
>> All the best in 2015
>>
>> - Frank
>>
>>
>>
>> 2015-01-07 14:06 GMT+01:00 andrea antonello <andrea.antonello@xxxxxxxxx>:
>>>
>>> Hi Ludwig, and maybe first of all the Project Steering Committee,
>>> I think this is finally important.
>>>
>>> > Our Company probably had mail loss in December, as i did not get any
>>> > updates…
>>> >
>>> > Any updates on uDig going the luna way?
>>>
>>> Is there a build available that I can test for linux or/and windows? I
>>> am not able to create a build right now, but I can sure test it in
>>> complex situations and make sure to give feedback.
>>>
>>> > We are waiting hard for a solution/working luna merge,
>>> >
>>> > which i can start working with as this is why my company paid Tom
>>> > Schindl to
>>> > do the E4 move for us/you.
>>>
>>> may I suggest an IRC meeting in the next week please?
>>>
>>> I would really like to know where we stand as community and what
>>> resources there are for uDig.
>>> It is important that we give a clear message to companies that approach
>>> uDig.
>>>
>>> I already had to watch a large company base a lot of good work and
>>> possible contributions (and bugfixes) on the previous version of uDig.
>>> And those changes will never get into the core.
>>>
>>> I don't want to be pessimistic, but if uDig has no resources to finish
>>> the locationtech migration or support contributions, we should make
>>> this very clear.
>>>
>>> I really want to make a clear point about the uDig status in an IRC
>>> meeting next week.
>>>
>>> My initial proposal is:
>>>
>>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015&month=1&day=14&hour=12&min=0&sec=0&p1=2080
>>>
>>> I suggest anyone interested to participate and to contribute to an
>>> agenda.
>>>
>>> All the best,
>>> Andrea
>>>
>>>
>>>
>>>
>>>
>>> >
>>> >
>>> >
>>> > Bakk. Techn. Ludwig M. Spitzenstätter
>>> >
>>> > Naturwissenschaftliche Sammlungen
>>> >
>>> >
>>> >
>>> > Tiroler Landesmuseen-Betriebsgesellschaft m.b.H.
>>> > Feldstrasse 11a, 6020 Innsbruck
>>> > Tel +43 512 594 89-425   Fax DW -440
>>> >
>>> > l.spitzenstaetter@xxxxxxxxxxxxxxxxxxxxxxx
>>> >
>>> > www.tiroler-landesmuseen.at | www.biooffice.at
>>> >
>>> >
>>> >
>>> > Von: udig-dev-bounces@xxxxxxxxxxxxxxxx
>>> > [mailto:udig-dev-bounces@xxxxxxxxxxxxxxxx] Im Auftrag von Frank Gasdorf
>>> > Gesendet: Dienstag, 25. November 2014 20:11
>>> > An: Jody Garnett
>>> > Cc: uDig project developer discussion
>>> > Betreff: Re: [udig-dev] initial code check-in
>>> >
>>> >
>>> >
>>> > Jody, All,
>>> >
>>> >
>>> >
>>> > the repository has been created (see
>>> > https://locationtech.org/bugs/show_bug.cgi?id=34) and at the moment you
>>> > are
>>> > the only one who can work with since you provided a github id already.
>>> >
>>> >
>>> >
>>> > For all others, please follow bug-description to add your github-id
>>> > (NOTE:
>>> > you have to enter old/new passwords to get it in)
>>> >
>>> >
>>> >
>>> > I added my id recently but haven't got an invitation mail from github.
>>> >
>>> >
>>> >
>>> > Whats the current state of the repository?
>>> >
>>> > * at master we are right on track with geotools 11.2 / geoscript 1.3.1
>>> > /
>>> > imageio-ext 1.1.10 / jaitools 1.3.1
>>> >
>>> > * on luna-branch we have Eclipse E4-Support but still on geotools
>>> > 9.0-M0 /
>>> > geoscript 1.1-M0 / imageio-ext 1.1.5 / jaitools 1.3.0
>>> >
>>> >
>>> >
>>> > I would suggest:
>>> >
>>> > * to contribute master at the moment only --> we still have full
>>> > feature
>>> > support
>>> >
>>> > * create an other branch E4-upgrade from there and merge udig-platform
>>> > luna-support branch into it
>>> >
>>> > * future work is taking place in locationtech/udig repo
>>> >
>>> > * focus on reactivating/refactoring unit tests we can run later on for
>>> > E4
>>> > migration
>>> >
>>> >
>>> >
>>> > Would you prefer to merge it in udig/udig-platform repository and have
>>> > a
>>> > "not really working state" on new master branch?
>>> >
>>> >
>>> >
>>> > What do you think?
>>> >
>>> >
>>> >
>>> > Cheers
>>> >
>>> >
>>> >
>>> > 2014-11-18 1:43 GMT+01:00 Jody Garnett <jody.garnett@xxxxxxxxx>:
>>> >
>>> > We should actually chat about it with Wayne - who is our mentor :)
>>> > Although
>>> > I am sure Andrew is friendly as well. The other thing to chat about, is
>>> > how
>>> > to "stitch together" git history locally - for any developers who are
>>> > interested.
>>> >
>>> >
>>> >
>>> > This was answered today on the geogig email list:
>>> >
>>> >
>>> >
>>> > David Winslow wrote:
>>> >
>>> > Actually git does have a tool for this scenario.  The command is 'git
>>> > rebase
>>> > --onto locationtech/master boundless/master feature_branch" which
>>> > essentially takes all the changes on feature_branch that are not on
>>> > boundless/master and cherry-picks them onto locationtech/master'.  See
>>> > http://git-scm.com/docs/git-rebase and search for the text '--onto' for
>>> > a
>>> > more verbose description.
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > udig-dev mailing list
>>> > udig-dev@xxxxxxxxxxxxxxxx
>>> > To change your delivery options, retrieve your password, or unsubscribe
>>> > from
>>> > this list, visit
>>> > https://locationtech.org/mailman/listinfo/udig-dev
>>> _______________________________________________
>>> udig-dev mailing list
>>> udig-dev@xxxxxxxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://locationtech.org/mailman/listinfo/udig-dev
>>
>>
>>
>> _______________________________________________
>> udig-dev mailing list
>> udig-dev@xxxxxxxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://locationtech.org/mailman/listinfo/udig-dev
>
>
>
> _______________________________________________
> udig-dev mailing list
> udig-dev@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://locationtech.org/mailman/listinfo/udig-dev