Hello Rich
Thanks you for reaching us. I will be present at Glasgow and would be
happy to participate. I can be a point of contact.
For the tasks, I suggest a collaboration with Maven. We contributed to
improvements of Java module support in Maven 4 because SIS pushes the
use of this feature probably further than most projects. Therefore, SIS
is a good test for Maven 4 support of Java modules. There is still holes
in Maven support, and we could try to fill them in a joint Maven-SIS work.
Another task which is always very welcome is documentation. We have a
developer guide separated from Javadoc, but it has not been updated for
a long time. Editions by someone not very familiar with SIS may actually
be better, because fresh eyes would probably see ways to restructure the
document for making it more accessible to newcomers.
Finally, one characteristics of Apache SIS is that we work closely with
the Open Geospatial Consortium (OGC). Some contributors may not have a
big interest in SIS itself but may be more interested in OGC's work,
because it has a much bigger impact. We were working recently on OGC
JSON encoding of Coordinate Reference Systems (CRS). We would welcome
help for completing the draft specification for OGC with SIS as
proof-of-concept implementation.
Martin
Le 05/05/2026 à 21:32, [email protected] a écrit :
Hi SIS community,
We're organizing a hackathon at Community Over Code Glasgow 2026 (October
11–14) and SIS has sessions on the schedule. We'd love for your community to
participate.
The idea is simple: dedicated time and space at the conference for contributors
(new and existing) to work together on real tasks — fixing bugs, writing docs,
tackling issues that need focused attention, or onboarding new contributors.
To participate, we'd need a few things from your project:
• A point of contact — someone we can coordinate with on logistics and
who'll be present at the event.
• A list of tasks — bugs, docs, features, good-first-issues, or whatever
your project wants to focus on. This helps people show up ready to contribute
rather than spending the first hour figuring out what to work on.
• Promotion — a message to your dev@ and users@ lists letting people know
this is happening and encouraging them to attend.
This is the first year we're bringing the hackathon back, so we're treating it
as a pilot — we want to gauge interest before committing to scale. Even if only
a few contributors from your project can participate, that's a great start.
If you're interested, please reply here or reach out to me directly. Even a quick "yes, we're
in" or "maybe, let's talk" is helpful as we figure out how many projects to plan for.
Also, please join us in the #hackathon channel on the ApacheCon Slack — that's
where we'll be coordinating as things come
together:http://s.apache.org/apachecon-slack
Thanks,
Rich, on behalf of the Community Over Code planners
