Open Source Checklist
This serves as a rough guideline for software projects that we will release as open-source. We don’t need to fulfill every single requirement for the Initial Release, but we should constantly update the fields as our project grows.
- Did we provide a README.md with basic information and setup on the project?
- Did we provide an API documentation for the project?
- Do we have a contributing guide in CONTRIBUTING.md?
- Do we have a CHANGELOG.md to document our releases?
- Do we have an OSI-approved LICENSE?
- Does our code follow the community style guide for our language of choice?
- Did we set-up automated testing for our business-logic code?
- Did we set-up continuous-integration/continuous-deployment (CI/CD) for the project?
- Do we follow semantic versioning guidelines?
- (Optional) Do we enforce style checks in our codebase?
- (Optional) Did we make our project accessible via package managers? (pip, npm, etc.)
- Do we have a Code of Conduct linked to our README?
- Do we have a project roadmap?
- (Optional) Did we provide Issue and Pull Request templates?
- (Optional) Did we set-up a chat client (e.g. Gitter) for our project?
Rapid solutions are needed to fight deforestation, but we know data is not enough. Here are our learnings from getting down and dirty with groups restoring ecosystems at the frontlines.
Learn how we configure Google’s Cloud Build to achieve continuous deployment of our Dagster pipelines.
Thinking Machines worked with Philippine Airlines to develop a Customer Data Analytics Platform that processes 20TB of data every day across 12 sources. The platform enables 90% faster insighting - reducing the time spent to generate key marketing reports from 3 weeks to 2 days.