Skip to content

Commit 402d56f

Browse files
authored
Merge pull request #4 from GenericMappingTools/nov2018update
Add new progress report
2 parents ff75fe2 + 3ccbccd commit 402d56f

File tree

3 files changed

+104
-36
lines changed

3 files changed

+104
-36
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ The GMT Team shall update the Steering Committee with timely reports. It has pro
2020
reasonable to provide these reports twice a year as a quarter is a bit too short to add
2121
much new material.
2222

23-
* [October 2018](reports/2018-10.md)
23+
* [November 2018](reports/2018-11.md)
2424
* [March 2018](reports/2018-03.md)
2525
* [September 2017](reports/2017-09.md)
2626
* [March 2017](reports/2017-03.md)

reports/2018-10.md

-35
This file was deleted.

reports/2018-11.md

+103
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
# Progress Report 2018-11-6
2+
3+
Since our [last report in March, 2018](2018-03.md) we have continued work on several
4+
parallel tracks:
5+
6+
* We have released our final GMT 4 version in July 2018, the GMT 4.5.18 release.
7+
* We have maintained the GMT 5.4 branch which is the current stable release branch,
8+
releasing 5.4.4 (the latest official release) on July 1, 2018.
9+
* We have ported all of our subversion repository and issue tracking to GitHub.
10+
* We have secured some funding from EarthScope for the new modern mode.
11+
* We are working on stabilizing GMT 6.0.0 beta and modern mode implementation.
12+
* We have secured funding for the upcoming Portugal and California developer summits in 2019.
13+
14+
## Farewell to GMT 4.5.x
15+
16+
We have issued our final GMT 4 release this July 1. This is version 4.5.18 and this
17+
terminates our involvement with bug fixes and point releases for this series. GMT 5
18+
was released 5 years ago and any issues discovered in 4.5.18 need to be reproduced
19+
in GMT 5 where we will make corrections.
20+
21+
## Maintenance of 5.4
22+
23+
Because all our development is now taking place in GMT 6, the 5.4 branch is only
24+
updated when a bug is found. We anticipate to make a 5.4.5 release shortly, which
25+
has been held up by the GitHub transition. The 5.4.5 release will simplify
26+
installation and building of the MB-system with GMT5 and 6.
27+
28+
## GMTSAR 2018 workshop
29+
30+
Wessel, Luis and Uieda attended the annual GMTSAR workshop at Scripps in August.
31+
Due to a late conflict, Wessel missed most of the workshop but arrived on the
32+
last day. GMT developers then stayed the weekend at Scripps and collaborated
33+
on GMT transition activities (below).
34+
35+
## GitHub Transition activities
36+
37+
During the GMTSAR 2018 workshop at Scripps, three of the GMT Developers (Wessel,
38+
Luis, Uieda) spent a weekend where we ported the entire GMT 5/6 subversion
39+
repository to GitHub. Using git will be the fourth version control system that
40+
GMT has used over the decades (SCCS, CVS, subversion, now git). The new
41+
repository (https://github.com/GenericMappingTools/gmt) is online at GitHub and
42+
is independent of the University of Hawaii. We expect that this transition will make it
43+
easier for community members to make contributions to the GMT code and documentation.
44+
For now, only the source code and the issue tracking has been migrated, but we are
45+
working on rebuilding the entire documentation process as well. We have started
46+
planning the first of two GMT developer summits to prepare our plans for how a GMT
47+
transition can be accomplished. All six GMT developers are confirmed to attend the
48+
summit which will be held in Faro, Portugal from January 20-27, 2019. Being off-season
49+
and with 3 developers in Europe, this was the cheapest and soonest meeting we could
50+
have.
51+
52+
## GMT 6
53+
54+
With the move to GitHub we have laid the foundation for future development.
55+
We have added Continuous Integration (CI) which means each time a pull request
56+
is made the whole suite is compiled and tests are run to make sure the changes
57+
in the pull request do not break anything in the repository. GitHub also provides
58+
an Issues list similar to our old Issues on the Wiki at SOEST. We still need to
59+
port older bug reports to GitHub as well as establish a forum similar to the one
60+
at SOEST. Finally, we need to automate the building of the documentation so that
61+
we can move off the GMT server at SOEST. By not relying on SOEST computers and
62+
hosting we are making it easier for a community of developers and users to assist
63+
with the maintenance of GMT.
64+
GMT 6 is slowly getting more stable, and with the separate funding from EarthScope
65+
we are implementing and testing the modern mode plus the new modules for movie
66+
making (movie.c) and Google Earth quadtree imaging (grd2kml.c). We hope GMT 6 beta
67+
will be ready early in 2019.
68+
69+
## Summits in 2019
70+
71+
We have secured NSF funding for our two proposed summits. At this point we have
72+
made reservations for the GMT Developer Summit in Faro, Portugal for Jan 20-27,
73+
taking advantage of very cheap rates for accommodation and travel. During this
74+
summit we will work up plans for the transition and these will be circulated do
75+
the GMT Steering Committee as well as NSF. We will incorporate their feedback
76+
and prepare a White Paper on the GMT transition for further discussion at the
77+
California Summit in the summer of 2019.
78+
79+
## Python package
80+
81+
Development of the Python wrapper has continued with added support for netCDF grids
82+
through the [xarray library](http://xarray.pydata.org/), a new sphinx extension for
83+
inserting GMT/Python plots into documentation, new module wrappers developed by new
84+
contributors to the project, functions to download sample datasets, and better reporting
85+
of C API errors.
86+
87+
The current implementation is running into a few limitations around building new module
88+
wrappers and tutorial documentation. A re-implementation of some of the underlying code
89+
is under way, which should make it easier to keep the documentation in sync with
90+
examples and the GMT documentation.
91+
92+
## Outreach
93+
94+
Some of the GMT developers (Wessel, Luis, Uieda) met with a group of Scripps graduate
95+
students and postdocs during the GMTSAR workshop to gather feedback and talk about GMT
96+
development. In particular, they discussed opportunities for getting involved in the
97+
project and how this process can be made more accessible. The overall reception was
98+
positive and resulted in the some feedback filed as issues in the new Github repository.
99+
We hope to keep this communication channel open to recruit new contributors in the near
100+
future.
101+
102+
Uieda gave an update on the GMT/Python status at the 2018 Scipy Conference in July (a
103+
recording of the talk is available on Youtube: https://youtu.be/6wMtfZXfTRM).

0 commit comments

Comments
 (0)