Requests for Comments¶
EOxServer Requests for Comments (RFCs) are a means for EOxServer developers to share their ideas and feature requests, propose enhancements, and discuss high-level issues concerning the further development of the software.
RFC Procedures¶
See the RFC Policies for details.
Writing RFCs¶
If you want to write a Request for Comments, please read the Guidelines for Requests for Comments first.
RFCs¶
Table: “List of accepted EOxServer RFCs” below lists all accepted EOxServer RFCs and their implementation status [1].
The list below provides links to all EOxServer RFCs available:
- RFC 0: Project Steering Committee Guidelines
- RFC 1: An Extensible Software Architecture for EOxServer
- RFC 2: Extension Mechanism for EOxServer
- RFC 3: OGC Service Extensions
- RFC 4: Data Packaging
- RFC 5: Processing Chains
- RFC 6: Directory Structure
- RFC 7: Release Guidelines
- RFC 8: SVN Commit Management
- RFC 9: SOAP Binding of WCS GetCoverage Response
- RFC 10: SOAP Proxy
- RFC 11: WPS 1.0.0 Interface Prototype
- RFC 12: Backends for the Data Access Layer
- RFC 13: WCS-T 1.1 Interface Prototype
- RFC 14: Asynchronous Task Processing (ATP)
- RFC 15: Access Control Support
- RFC 16: Referenceable Grid Coverages
- RFC 17: Configuration of Supported Output Formats and CRSes
- RFC 18: Operator Interface Architecture
- RFC 19: Migrate project repository from svn to git
[1] | Note that this list might not be fully up to date although we try hard. |