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?
We worked with Globe Telecom to build an AI model that measures the socioeconomic class of areas across the entire Philippines to assist in their high CAPEX decision making.
We’re excited to announce that we’re partnering up with Mapbox!
Making design decisions in Thinking Machines was as hard as picking up an outfit when you’re late for work. Learn how we solved our design dilemmas with Asimov, TM’s design system.