Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build status dashboard of brigade meta data for Brigade Congress #20

Closed
nikolajbaer opened this issue Aug 19, 2019 · 3 comments
Closed
Assignees

Comments

@nikolajbaer
Copy link
Collaborator

To motivate and communicate the Brigade Project Index initiative and challenge, we discussed creating a dashboard / interactive visualization for Brigade Congress.

The visualization would show all brigades across the network, their projects and the meta-data/indexed "status" of these projects. It would update as often as possible/reasonable.

Additionally it should be paired with instructions on how to better index projects in your brigade.

Bonus features might be:

  1. Filtering / Visualization of tags and taxonomies
  2. Suggest one!

References:
https://civictech.guide
(something similar to their homepage map visual maybe)?

@nikolajbaer nikolajbaer self-assigned this Aug 19, 2019
@themightychris
Copy link
Collaborator

@nikolajbaer I can commit to ingesting and normalizing all the projects discoverable through the CfAPI into a repository per #19

It will be a repo/branch containing a tree of files, where every blob is the repo is a TOML file profiling one project. I'm thinking the paths will probably be ${brigade}/${project} but that will probably evolve and isn't super important.

Using that as our source of truth, I could publish from there into a giant JSON file or an SQL script. Do you have any idea yet what would be a good way to hand that off to you for use in a dashboard? If you're building in Node, I could provide library code / examples for reading the DB in its native git format

@nikolajbaer
Copy link
Collaborator Author

If you ping me when you have your first run of that repo going, I can definitely work from that.

My goal is to keep this pretty minimal (html page with some d3 ideally). Figuring out when and how often to update might be our biggest concern, but we probably can put something together that runs periodically and gathers what is needed (e.g. a lambda script or whatnot).

@themightychris
Copy link
Collaborator

@nikolajbaer sounds good. If you beat me to getting started, maybe mock a json file and then I'll target fully populating it with an ongoing process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants