deegree TMC meeting (2014-05-07)
- Welcome and agenda review
- Date for TMC/PSC joint meeting
- Consolidation of deegree infrastructure
- Participation at Bolsena Code Sprint 2014
- Status of automated pull request testing
- deegree3 development pulls
2. Date for TMC/PSC joint meeting
A TMC/PSC Skype meeting has been scheduled for Friday (May 9) at 11 am to find a date for the TMC/PSC joint meeting.
3. Consolidation of deegree infrastructure
The machine that hosts several services of the deegree project (artifact repository, buildserver, homepage) is currently suffering from hard disk problems. In the past, this machine has generously been payed and administered by lat/lon. lat/lon is willing to continue this contribution to the deegree initiative, but would like to hand over server adminstration responsibility to the TMC. This should also include transfer of other deegree services which are still on lat/lon servers (wiki, trac, potentially others).
- A solution is needed rather quickly to avoid loss of data (especially artifacts). In order to avoid an emergency situation, at least the artifacts should be backed up to a differnt machine.
- A quick Google search didn't show a lot of offers for hosted artifact servers
JensFitzke pointed out that this is a highly strategic aspect which should be at least discussed or decided about together with the PSC
- As the machine runs a RAID array, it may be a low-effort solution to just exchange the faulty disk instead of considering a full migration to a new machine right now. lat/lon looks into this.
In the end, the TMC decided that it would prefer to keep the current hardware for now and proposes to move ALL services to a hosted (SaaS) solution.
4. deegree at Bolsena Code Sprint 2014
The yearly Bolsena Code Sprint is close, but a few free places are still available. This could be an excellent chance to fix remaining blockers and get a well-tested 3.4 release out of the door. Maybe every company involved in the deegree bodies (lat/lon, IDgis, Occam Labs, grit) could send one developer to work on this in the spirit of OSGeo. And of course, to enjoy the Italian sun a bit
Note that the FOSGISS sponsored this in the past, so chances are that they will be pay the costs for accomodation (550,- per person) again.
5. Status of automated pull request testing
Automated pull request testing for 3.3 is working now, at least most of the time. Sometimes, build time exceeds 50 minutes which leads Travis to terminate the build. While this is not 100% satisfying (and should be improved, e.g. by implementing caching of dependencies), it can usually be worked around by re-running a timed out build.
6. deegree3 development pulls (for 3.4-pre11)
Pull request #198: Feature/digits mapping. Not accepted (-2). More discussion required.
Pull request #211: Queryable not configurable. Not accepted (-4)
Pull request #249: GDAL integration and dataaccess modules. Not accepted (-1)
Pull request #285: CustomMapping for every mapping. Not accepted (-4)
Pull request #287: LinePlacement: 'center' and 'wordWise' extension. Accepted (+3)
Pull request #289: oracle sdo improvements. Skipped for now
7. deegree3 point release pulls (for 3.3.9)
Pull request #189: fix umn get feature info parser. Accepted (+2.5)
Pull request #199: Feature/digits mapping. Not accepted (-2). More discussion required.
Pull request #209: Queryable not configurable. Not accepted (-3)
Pull request #213: Use of explicit uom within SE Styles. Not accepted (-4)
Pull request #220: LinePlacement: 'center' and 'wordWise' extension implemented. Not accepted (-2)
Pull request #229: CSW: Use DublinCore as default output schema for GetRecords responses. Not accepted (-1)
Pull request #234: Missing support for "xml:" namespace added. Accepted (+4)
Pull request #246: front controller fixes. Accepted (+4)
8. Pull request feedback
During the pull request session, the issue of providing feedback back to pull requesters came up. Ideally, this should be done in a standardized manner. TorstenFriebe agreed to cope with this for now, along with his tasks of compiling release notes and maintaining the trackers.
After the meeting, TorstenFriebe and MarkusSchneider prepared an initial set of response templates: https://github.com/deegree/deegree3/wiki/Pull-request-response-templates
9. 3.4 release date
SebastianGoerke joined the meeting and asked for the release date of deegree 3.4 final. There are several blockers to this (most notable UI regressions) and an official release date is not available. This needs to be discussed at the upcoming TMC/PSC joint meeting.