Contributing

Contributions are welcome. Follow the code of conduct, then install DASCore for development.

Planning

Development planning and prioritization happens in the DASDAE project.

DASCore or other DASDAE packages

Features belong in DASCore when they are broadly useful, not domain-specific, and need no new dependency; propose specialized features as extension packages. Before adding any dependency, open a discussion describing the feature, dependency cost, and related uses. Controversial additions may require a developer-check-in presentation covering installation size and future uses, followed by majority approval. Other DASDAE packages may choose their own workflow, but following DASCore’s conventions makes cross-project work easier.