The following are all Node.js tools used to help facility the OS development processes and pipelines for the NuPIC project and satellite repos. They are configured to be deployed in a stateless fashion on a simple platform (currently Heroku).
Kitchen sink, stateless, Node.JS application used to support NuPIC development flow. Been around for several years, not the best code quality. Needs a redesign, but mostly generic. Could be used for other projects with a little work.
Here's an old video of how it worked 2 years ago.
- Facilitates NuPIC development flow
- PR validation
- Integrates repos with dependencies
- Mailing list statistics
- Lots of ad-hoc tools, some of which are not used anymore
Provides a generic "widget" framework for piecing together a status board. Current implementation contains the statuses of dependent services (Github, Travis-CI), last doc builds, custom repo statuses, links to other tools, running Travis-CI builds, and recently updated issues across all monitored repositories. Ugly, but functional.
A component of Sprinter Dash, the Road Map presents a consolidated view across many repositories, using Github Issues to present Milestones, super tasks, and subtasks.
Because Github doesn't have the concept of sub-tasks, this UI uses markdown conventions to associate issues and present them grouped together.
Caching for this project needs to be improved, because the Github API calls used to populate the views are extensive. Initial load times are very high.
Sprinter is a low-level library and CLI for querying the Github Issues API across multiple repositories (plus some other parts of the API like collaborators and labels). It is used in all three of the projects described above.
A small Travis-CI client for listing running builds across a Github organization or user account.
@cbaranski Can you review this for me? This is for an upcoming TODO group meeting about open source tooling. We will all showcase the tools we've created, and this is a high-level description of ours.