Open Rabia2219 opened 3 months ago
Rabia2219
commented
3 months ago Should we be offering general onboarding in small groups? Max 3 new people, 2 brigade leads?Admin: Currently tool administration (slack, discourse, etc) happens in an ad hoc way and is not documented (or at least, not anywhere I am aware of). That is 1) not transparent 2) not secure 3) is potentially gate-keeper-y and not equitable 4) can create a burden for the people who are admins.
We should have some kind of onboarding and offboarding process for tool admins, and we should document admin-ship, and how admins are chosen, somewhere.
Tools:
https://docs.google.com/spreadsheets/d/1PvagKDaWoPFeSiC54crVgT4NfUPGirJnLzLVoQ9WsCo/edit#gid=0Make github issues on brigade projects with specific, actionable docs cleanup requestsFigure out how to offer rolling onboarding pairing to project index-- try to get someone "on call" for every weeknight?Backwards-compatibly tag Discourse posts to align with project index taxonomy, suggest new additions to taxonomy based on thatAsk former NAC members for help with Google Drive spelunking and context on what those things even are; transfer ownership of docs to CfA
Move things to DIscourse: https://discourse.codeforamerica.org/c/nac-lounge/25Should brigade-infrastructure and brigade-infrasturcture moderation be two channels that include some of these other tools?How do we recruit volunteers who have never been to a brigade meetup? Should we send them to their brigade? Who will manage them? Does that put project managers in an HR role?Calendar of meetups of projects that need new volunteers? Some kind of integrated "get involved plz here's how" experience??Statusboard-- one view, searchable and filterableMake some Discourse wikis, recruit some wiki-people to do this?READ THIS FIRST:
This board is being sunsetted in favor of https://github.com/codeforamerica/brigade-infrastructure/projects/1
Please go there instead! If you see anything here that needs migrated, please feel free to add it as an issue on that repoCheck out zoom calendar of brigade meetings-- where should this live? Calendar-- how can NAC/brigade members add events to existing calendar on CfA website? How can we make that the source of truth, or iterate on it to create one?
Action: Em will email Veronica/Tom to figure out integrating all calendars, both brigade network calendar and the virtual meetup calendarMeta-documentation for how to use Discourse and what it is for and how it's different from slack
https://discourse.codeforamerica.org/t/slack-vs-discourse-and-when-to-use-each/187Repo: https://github.com/hackforla/github-api-test
Demo: https://hackforla.github.io/github-api-test/
Project Management Board: https://github.com/hackforla/github-api-test/projects/1Repo: https://github.com/ckingbailey/commit-schemaAs a user defining metadata for my project, I'd like to drop downs (or other means) so I understand what options are accepted in the current taxonomy. I'd also like an "other" option if none of the current options fit the bill.Current Status: Alpha Live in use/ Beta under construction - Expanding Beta Index to include more GitHub and repository data.Current Team: Chris Alfano, + consulting with Nikola, Melanie, Ryan Harvey.
Looking for the following help: Data EngineersPrimary Purpose: Provide a comprehensive and updated database of all project in the civic tech eco system that can be shared with many projects or front ends.Repo: https://github.com/codeforamerica/brigade-project-indexCurrent Status: Active Beta/ Coordinating with team members to determine direction around where the design is going.Current Team: Nikola, Melanie, Ryan Harvey, Chris Alfano
Looking for the following help: Not sureprimary purpose: a way for brigades and project owners understand how their project is being indexed and how to improve it.
secondary purpose: to be able to find projects with same topics (covid19).Repo:
https://github.com/codeforamerica/brigade-project-index-statusboard/
Link:
https://statusboard.brigade.cloud/
Project Management / Issues:
https://github.com/codeforamerica/brigade-project-index-statusboard/issuesTerms that need UX conversations about what the people using them mean (e.g. deprecated/inactive)
[see tags being used at CfA](https://statusboard.brigade.cloud/#/topics)
Number of repositories using term in CfA:
Number of repos outside of CfA using (e.g., inactive has [112](https://github.com/search?q=topic%3Ainactive&type=Repositories&ref=advsearch&l=&l=))Taxonomy should have it's own repo
Taxonomy should exist as an independent and standalone piece that can be used by multiple different tools.Update project statusboard to run off new JSON APICreate separate repo for brigade project index statusboard (preferably on codeforamerica github?)Setup CNAME For heroku statusboard project
Overview
We need to prepare the Project Boards for the forced migration that GitHub is doing in August, so that it is already working well for the team by then.
Action Items
Repeat first 3 steps for each card
[PASTE CARD CONTENT HERE]
project board migrationlabel to this issueResources/Instructions
Classic Project board URL(s):
Open:
Closed:
New Project board URL(s): None
Card Content Spreadsheet(s):