GSIP 164

GSIP 164 - Promote geofence modules from Community to Extension

Overview

Proposal to promote the community geofence and geofence-server modules to an extension.

Proposed By

Emanuele Tajariol

Assigned to Release

This proposal is for GeoServer 2.13.

State

• Setup
• Under Discussion
• In Progress
• Completed
• Rejected
• Deferred

Motivation

To expand GeoServer's authorization capabilities using the GeoFence rule engine.

Proposal

To move the community geofence and geofence-server modules to extension status.

The 2 modules are used for different configurations:

• the geofence module needs an external GeoFence webapp running, and performs remote auth requests.
• the geofence-server module runs the GeoFence rule engine internally in GeoServer, and imports the geofence module logic.

According to the mail in the ML, the geofence-server module seems the most used configuration, so, in order to have this module as a supported extension, the geofence module should be moved in supported as well. Since there is a strong dependence between the two modules, they are presented here for promotion in a single proposal.

The geofence module has been a community module since Oct/14. The geofence-server module has been a community module since May/15.

At this point, the modules already satisfy many of the requirements for promotion:

• The modules have at least a "handful" of users: judging by Jira and mailing list activity, the module is used by at least a "handful" of users.
• The modules have a designated and active maintainer: Emanuele Tajariol is also currently the maintainer of the GeoFence project, which contains the core authorization rule engine.
• The modules are considered "stable" by the majority of the PSC.
• The modules maintain 40% test coverage:
  • geofence The package scores a 47% line coverage / 27% branch coverage with Jacoco (32%/6% with integration tests turned off).
  • geofence-server The package scores a 59% line coverage / 45% branch coverage with Jacoco.
• The modules have no IP violations.
• The module has a page in the user manual:
  • geofence: documentation for this module can be found as a wiki page in the geofence project. These pages should be ported into the GeoServer user manual.
  • geofence-server: extensive documentation already exists in the user manual.
• The maintainer (Emanuele Tajariol) has signed the GeoServer Contributor Agreement, also as a maintaner of other GeoServer features (WMTS cascading).

Backwards Compatibility

Feedback

Voting

Project Steering Committee:

• Alessio Fabiani: +1
• Andrea Aime: +1
• Ben Caradoc-Davies:
• Brad Hards: +0
• Christian Mueller:
• Ian Turton:
• Jody Garnett: +1
• Jukka Rahkonen:
• Kevin Smith:
• Simone Giannecchini: +1

Links

• Email Discussion
  • Discussion of geofence module Promotion.
• Pull Request - Coming
• Jira issue
  • [GEOS-8350] Promote geofence/geofence-server community modules to extension (GSIP-164)