Difference between revisions of "Software Task List"

From floodzilla-wiki
Jump to navigation Jump to search
(Created page with "== Software Task List == === Next Tasks in Priority Order === === Grab Bag === This is an unordered, unprioritized, incomplete list of pending tasks.")
 
Line 6: Line 6:
  
 
This is an unordered, unprioritized, incomplete list of pending tasks.
 
This is an unordered, unprioritized, incomplete list of pending tasks.
 +
 +
==== Main Site ====
 +
 +
TASK: Flesh out forecasts page.
 +
* Be able to view individual gages
 +
* Add other gages to list?
 +
* Tabular view of data?
 +
 +
TASK: Forecast notification emails
 +
* Determine if we need to support all the different kinds of email floodzilla.com sends
 +
* Formatting, styling
 +
* Subscribe/unsubscribe/unsubscribe all
 +
 +
TASK: Open source
 +
* Put together public repository
 +
* Methodology: Try to move code over bit by bit, or commit to moving all code at once?
 +
* Review all code for secrets/passwords
 +
 +
TASK: Front page rework
 +
* Spec
 +
 +
TASK: Rework flood notifications to allow summary/batching of emails/SMS
 +
* Current system is noisy when there's a flood
 +
* Suppress messages when a river is hovering around notification stage level
 +
 +
TASK: Get a bug system, or clean up Trello board and use it
 +
 +
TASK: Discharge mode for USGS charts
 +
* Spec? Forecast branch has a developer-designed pass
 +
 +
TASK: build a queue/pipeline system for processing new data (new readings, new forecasts, etc)
 +
* example reading steps: Preprocess (e.g. remove Senix non-reading posts), Filter invalid/offline data, Mark possible crests, Notifications
 +
* example forecast steps: Preprocess, Build downstream predictions, Notifications
 +
 +
TASK: allow more complex chart views (maybe this is Admin-only?)
 +
* battery level
 +
* "missing" readings
 +
* better zoom/navigation
 +
 +
==== Infrastructure ====
 +
 +
TASK: build a test/staging database and environment
 +
 +
==== Admin Tools ====
 +
 +
TASK: Rework how Device creation happens
 +
* don't require user to input ID
 +
* if we get a reading from an unknown device, create the device object
 +
 +
TASK: USGS Admin
 +
* currently, adding new USGS gages requires direct database access
 +
 +
TASK: Per-gage notification lists for flood levels, offline status, etc
 +
* primarily for Gage Stewards
 +
 +
==== Data ====
 +
 +
TASK: recalculate data for 124th West to take into account resurvey.
 +
 +
TASK: recalculate data for Tolt Hill to take into account resurvey.
 +
 +
==== Wiki ====
 +
 +
TASK: Wiki permissions changes: Allow edits only from users with verified email addresses.
 +
 +
TASK: Document wiki administration, installation, etc.
 +
 +
TASK: Ensure all passwords/secrets are in password manager.

Revision as of 17:03, 28 January 2021

Software Task List

Next Tasks in Priority Order

Grab Bag

This is an unordered, unprioritized, incomplete list of pending tasks.

Main Site

TASK: Flesh out forecasts page.

  • Be able to view individual gages
  • Add other gages to list?
  • Tabular view of data?

TASK: Forecast notification emails

  • Determine if we need to support all the different kinds of email floodzilla.com sends
  • Formatting, styling
  • Subscribe/unsubscribe/unsubscribe all

TASK: Open source

  • Put together public repository
* Methodology: Try to move code over bit by bit, or commit to moving all code at once?
  • Review all code for secrets/passwords

TASK: Front page rework

  • Spec

TASK: Rework flood notifications to allow summary/batching of emails/SMS

  • Current system is noisy when there's a flood
  • Suppress messages when a river is hovering around notification stage level

TASK: Get a bug system, or clean up Trello board and use it

TASK: Discharge mode for USGS charts

  • Spec? Forecast branch has a developer-designed pass

TASK: build a queue/pipeline system for processing new data (new readings, new forecasts, etc)

  • example reading steps: Preprocess (e.g. remove Senix non-reading posts), Filter invalid/offline data, Mark possible crests, Notifications
  • example forecast steps: Preprocess, Build downstream predictions, Notifications

TASK: allow more complex chart views (maybe this is Admin-only?)

  • battery level
  • "missing" readings
  • better zoom/navigation

Infrastructure

TASK: build a test/staging database and environment

Admin Tools

TASK: Rework how Device creation happens

  • don't require user to input ID
  • if we get a reading from an unknown device, create the device object

TASK: USGS Admin

  • currently, adding new USGS gages requires direct database access

TASK: Per-gage notification lists for flood levels, offline status, etc

  • primarily for Gage Stewards

Data

TASK: recalculate data for 124th West to take into account resurvey.

TASK: recalculate data for Tolt Hill to take into account resurvey.

Wiki

TASK: Wiki permissions changes: Allow edits only from users with verified email addresses.

TASK: Document wiki administration, installation, etc.

TASK: Ensure all passwords/secrets are in password manager.