nsidc
Document bug and feature prioritization process
The initial draft for triaging per #901 (see https://earthaccess.readthedocs.io/en/latest/contributing/triaging/) includes helpful information on general Issue triaging, including a flow chart to ensure issues are properly labeled. We did not include priority designation as part of this initial doc, so this is a follow-on ticket to implement.
We currently have a Bug Priority view in our Project (https://github.com/orgs/nsidc/projects/10/views/5) though the High, Medium, and Low priority labels are currently added ad-hoc and somewhat arbitrarily. We ought to document our general guidelines for Issue priority, perhaps focusing specifically on Issues with type:Bug. Can we look to other project governance docs as inspiration for priority designations? Some general ideas to get us started:
Priority: High - Users are unable to search or access data for a significant number of collections and key earthaccess use cases/workflow steps.
Priority: Low - Low impact and time criticality; may be only affecting a small percentage of users, collections, or use cases.
Priority: Medium - Somewhere in the middle. Maybe documentation or tutorials are broken, or less common use cases are impacted.
