You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My theory is that the developer guide can be a single point of reference for best practices, policies, etc for the stac-utils Github organization. Right now it includes some recommended issue and pull request templates, some words on semantic versioning and dependency management, and some de-facto policies around owners, maintainers, etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've created a stac-utils developer guide: http://stac-utils.github.io/developer-guide/. Source code is here: https://github.com/stac-utils/developer-guide.
My theory is that the developer guide can be a single point of reference for best practices, policies, etc for the stac-utils Github organization. Right now it includes some recommended issue and pull request templates, some words on semantic versioning and dependency management, and some de-facto policies around owners, maintainers, etc.
Contributions and suggestions always welcome!
Beta Was this translation helpful? Give feedback.
All reactions