GeoTools / GeoServer Meeting 2015-03-31
=======================================

Attending
---------

Ben Caradoc-Davies
Harrison Grundy
Jody Garnett
Andrea Aime
Jukka Rahkonen


Agenda
------

- Meeting time
- Jira migration
- PSC refresh
- Pull request roundup

Actions
-------

- AA: Communicate to devel list that new issues can be created
- HH: upload what issue we have now, do a second pass with 
component/versions
- BCD: proposal to change PSC / PMC grace period to 6 months and make 
removal automatic
- JG: ask for nightly build test for checkboxes on firefox, etc...

Welcome to Torben as new geoserver committeer!

Actions from last meeting
-------------------------
- Release:
http://blog.geoserver.org/2015/03/23/geoserver-2-7-released/
http://geotoolsnews.blogspot.ca/2015/03/geotools-130-released.html
- AA? Confirm GeoServer 2.7 security regression; if verified delay a 
week [DONE]
- JG: Merge in relax paths pull request [DONE]
- BCD: support boundless setting up GeoServer app-schema online tests 
[PENDING]
- JG: Blog post about vecmath, code sprint [DONE]
- http://blog.geoserver.org/2015/03/23/cite-tests-at-foss4g-na/
- 
http://geotoolsnews.blogspot.ca/2015/03/foss4gna-code-sprint-replacing-vecmath.html
 


Meeting time
------------

Daylight savings time ending in New Zealand. Ben asks for a later meeting.

Idea: Move 1/2 hour later

- Too late for Europe
- No good for Andrea and Jukka
- Even later might be OK (after dinner)
- Can we go to the other side of the clock?
- Nope, current time is least bad :(

Andrea: How about 2 hours later:
- May be possible?
- Kind of up to Jukka?
- Jukka: OK

Motion: Move meeting to 19:30 UTC

Agreed!

Next meeting:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting&year=2015&month=4&day=14&hour=19&min=30&sec=0&ah=1

Jira migration
--------------

All tickets and attachments collected, just a matter of getting versions 
and components, and attributes

Harrison (Guest)

Cloud: https://osgeo-org.atlassian.net/secure/Dashboard.jspa

We can use the new jira instance for new tickets (since old tickets will 
line up). Easier to update existing ticket than to create a new one with 
all the new information.

Q: Off by one error? (Reported by Torben)
A: Yes, created one ticket fewer than neede. Title in the summary is 
filler is also off by one - but since that will be replaced it is not 
important.

Q: Automate creation of versions?
A: Yep, similar to the script for tickets

Tarball of everything and script.

Q: reattach attachments?
A: yes

Q: What is the missing?
A: User that created the ticket ... will store the username as a custom 
field

Q: Will the username be stored or perserved?
A: Stored in a custom field

Q: Scripts open source?
A: BSD 2-clause

Discussion: How to add new users? By hand (PSC members) or open for user 
sign up? Is it possible to write a script to remove input from a spammer?

The other issue is 2000 user limit. Jody: not sure I care :) We can ask 
when we get that far...

Idea: Use jira as a backend for something else. Form to feed issues into 
Jira. This is used on free BSD project - new users like to create new 
tickets more than they want to comment on existing tickets.

Idea: Create components by hand? Not helpful as the internal ids don't 
match...

Q: Is the new instance slow?

Gets faster during interactive use.
Very slow for creating tickets ... not sure why?

HH: Would like to benchmark performance?
- May consider osgeo hosted jira
- Can also atliassian

Q: uDig and GeoAPI?
A: Collected so we have a backup, but GeoServer and GeoTools are priority

Wiki
- https://github.com/geotools/geotools/wiki
- old.geotools.org
- script to convert from textile output --> markdown or rst?

Docs
- do through geotools docs and remove references to wiki
- module matrix
- update config.py GEOT definition
- anything else ...

PSC refresh
-----------

GeoServer:

    * Alessio Fabiani
    * Andrea Aime
    * Ben Caradoc-Davies
    * Chris Holmes (Chair)
    * Christian Mueller
    * Gabriel Roldan
    * Jody Garnett
    * Jukka Rahkonen
    * Justin Deoliveira
    * Phil Scadden
    * Simone Giannecchini

GeoTools:

    * Andrea Aime
    * Ben Caradoc-Davies
    * Christian Mueller
    * Ian Turton
    * Jody Garnett
    * Justin Deoliveira
    * Simone Giannecchini

See: http://docs.geotools.org/latest/developer/roles/committee.html

Quote: "If you are unable to maintain your responsibilities as a PMC 
member, please feel free to step down at any time. Thank you so much for 
your contributions. If we cannot find you (especially when voting on 
proposals) it becomes very difficult to keep the project functioning. 
After two months time we will send out a search party and nominate your 
replacement."

Ben: Would like find more volunteers for reviewing pull requests
Jukka: And tickets.

GeoTools intended to use module maintainers for reviewing pull requests.

Ben: Update the policy to 6 months and automatically update the PSC list.

Andrea: Need a proposal for this (Ben to take the action item)

pull request roundup
--------------------

Disable clicking on labels/whitespace to toggle checkboxes [GEOS-6948]
- https://github.com/geoserver/geoserver/pull/996
- backport to stable? ask for test of nightly build on geoserver-users 
list (chrome, safari - tested, firefox, ie?). Problem is visible on 
firefox...

GSIP-128 JAIEXT integration in GeoServer
- https://github.com/geoserver/geoserver/pull/997
- need multiple people to review
- ben will help test #796?

windows failure?
- can no longer reproduce on the buld box.

geotools matrix branch:
- JG: will catch up with tyler and ask about timeframe
- about the point and line classes? use point2d and line2d classes :)

Build failures on travis:
- openjdk - wcs failure
- oracle jdk - jar signing issue from niels jar signing issue (order of 
jars in test classpath)? waiting on community pull request ...


-- 
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz>
New Zealand

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to