ExperimentsInHonesty
commented
11 months ago 2023-11-01 Meeting Agenda (Ethan and Bonnie)
- [x] FYI
- I do not have full privileges on issues in BOP. For instance, I cannot add labels or edit comments. This won't matter unless there is some reason to keep BOP.
- Please update roster
- [x] Team member privileges. Bonnie:
- [x] explain how it works with knowledgebase as an example
- [x] why can't Ethan add teams?
- [x] How give developers ability to edit comments and add labels
- [x] Proposal: Migrate BOP project to regular project.
- In knowledgebase repo you can't create a classic project, so seems GitHub wants projects to be migrated.
- Project boards work the same
- Non-classic projects have some cool features
- Can have multiple repos
- Additional useful views
- [x] Proposal: Transfer issues from BOP to Knoweledgebase through UI one a time. It could also be done in bulk programatically from the terminal, but UI is probably faster.
- [ ] Review TODOs for creating bugs
ethanstrominger
1610saas
Overview
This issue tracks the agenda for our weekly meetings
Issue Template
Links to other agenda issues for your team
(so that you can easily post on their agendas items that come up at yours)
Previous Meetings (link to each comment with the date)
2023-10-27 meeting notes
- The purpose of the BoP project is to create an app to catalog knowledge assets about development practices for Code for America brigades. - The purpose of the Knowledgebase app which is in progress is intended to supported BoP functionality. Additionally, the app supports the generation of web pages from markdown about development practices. The markdown is stored in the HackForLA Website repo and when generated, added to the "Toolkit" of the HackForLA website. The web page and source markdown are also content asset which would be of interest to HackForLA and potentially other Code for America brigades. - Since Knowledgebase is intended to support BOP, the two projects are being combined. - MVP for Phase 1 will only support the cataloging of content described in the first bullet. Generation of HackForLA content will be a later phase. - Knowledgebase stores content assets and related data in a Postgres or (for development only) MySQL database. The data is maintained through the default admin screens in Django. - The Knowledgebase screens were reviewed to see how closely they align with BOP. The following needs to be added to the Knowledgebase model: - gdoc (badly named) table which was intended to hold all types of content assets will be split into two tables: asset groups and assets. Most fields will go into asset group. An asset group will have one or more assets associated with it. Asset table will include title, asset type, and URL at a minimum. - google id is only relevant if the content is used as source for the HackForLA website. To support parallel development of web page generation this field will need to be included but can be hidden when deployed to production. - a field is needed to indicate this is for / from the HackForLA website, which will be hidden for production. - Data will be initially populated from existing google sheets - Subsequent updates and additions will be done through the Django admin page. No APIs need to built for this. - Viewing and querying can also be done through Django admin, depending on the complexity of the functional and usability requirements. - Django admin security (which comes with role and group based security) will be configured based on security requirements. - APIs will be created to support a dashboard that summarizes the asset data. - Data maintained by People Depot will be synchronized with Knowledgebase