erddap
erddap copied to clipboard
Priority Projects
This is subject to change. Priorities will shift and new projects will be added over time. This is roughly in priority order, but not a strict ordering. Also some projects will take a very long time and so will likely be done slowly over time.
- Improve the ERDDAP developer experience
- Update documentation to be in line with modern open source project expectations.
- Improve testing
- Enable more of the tests (there's currently still many disabled for a variety of reasons)
- Reduce the data needed for tests and/or create a set of tests that needs minimal data
- Set up automation to run tests for every pull request to verify changes.
- Automate build (WAR) creation and make it available
- Detect Issues
- Improve logging, either making processed logs available publicly, or an integration like Sentry to aid in detecting problems.
- Metrics in Prometheus. Add additional metrics (like those on the status page/daily email).
- Improve the admin experience
- Make ERDDAP easier to run and configure, including but not limited to official support for containers/Kubernetes
- Identify pain points in admin workflows and improve them
- Official Docker support
- https://github.com/ERDDAP/erddap/issues/96
- Support the interests of those supplying data
- #134
- Improve the user experience
- #92
- Technical Debt
- #159
- Migrate away from hardcoded paths to using Java Resources
- Provide better support for adding dataset types (possibly without needing to modify main code base)
- Separate helper utilities to their own build targets
- Better handle standalone tools embedded in the codebase (NetCheck, GenerateDatasets, ArchiveADataset, TranslateMessages)
- Use a templating language or framework for defining the HTML
- Reduce log spam during testing