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.

Sign up for GitHub

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

Jump to bottom

KB: Dev team agenda #11

Open
ExperimentsInHonesty opened this issue Oct 31, 2023 · 6 comments
Open

KB: Dev team agenda #11

ExperimentsInHonesty opened this issue Oct 31, 2023 · 6 comments
Assignees
@pwalia1 @ethanstrominger @ExperimentsInHonesty @Estherchuks
Labels
category: management complexity: small feature: agenda milestone: missing role: back end dev role: dev lead role: security admin size: 0.25pt Can be done in 1.5 hours or less

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Oct 31, 2023 •
edited
Loading

Overview

This issue tracks the agenda for our weekly meetings

Issue Template

## [Date ]  Meeting Agenda

### Prework to prep for meeting
- [ ] #

### Recurring items
 - [ ] Review any questions outstanding from #16 
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/knowledgebase/projects/1#column-19676619)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team member
       - [ ] [Ethan Strominger](https://github.com/hackforla/knowledgebase/issues/assigned/ethanstrominger)
       - [ ] [Toe Arkar](https://github.com/hackforla/knowledgebase/issues/assigned/Toe12)
       - [ ] [Priya](https://github.com/hackforla/knowledgebase/issues/assigned/pwalia1)
       - [ ] [Erin](https://github.com/hackforla/knowledgebase/issues/assigned/erin)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ]  #

### New Items
- [ ] 
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items

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
@ExperimentsInHonesty ExperimentsInHonesty added size: 1pt Can be done in 4-6 hours size: 8pt Can be done in 31-48 hours question Further information is requested labels Oct 31, 2023
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Oct 31, 2023 •
edited
Loading

2023-11-01 Meeting Agenda (Ethan and Bonnie)

  • 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
  • Team member privileges. Bonnie:
    • explain how it works with knowledgebase as an example
    • why can't Ethan add teams?
    • How give developers ability to edit comments and add labels
  • 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
  • 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

@ExperimentsInHonesty ExperimentsInHonesty added size: 0.25pt Can be done in 1.5 hours or less and removed size: 1pt Can be done in 4-6 hours size: 8pt Can be done in 31-48 hours question Further information is requested labels Oct 31, 2023
Closed
@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Oct 31, 2023 •
edited by ethanstrominger
Loading

2023-11-03 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

  • Review figma and compare to data model
  • Knowledge transfer
    • Review Wiki structure
    • Review how table definition spreadsheet is organized
    • Review UI
    • Review Github project board
    • At next meeting (so devs can try or review first)
      • troubleshoot deployment issues
      • review code in peopledepot/django-root (ignore util and iso-tutorial node)
  • [ ]
  • Review issues (or TODO) for assignments
  • Identify potential feature labels #13
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

  • Discussed / reviewed
    • code for data models to understand Django
    • requirements of API (read only)
    • started reviewing figma and mapping to Django data model, but need Bonnie

Task Items

Closed
8 tasks
@ethanstrominger ethanstrominger pinned this issue Nov 1, 2023
@ethanstrominger
Copy link
Member

2023-11-03 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

  • Review figma and compare to data model
  • Discuss front end developer engagement (when?)
  • Knowledge transfer
    • Review Wiki structure
    • Review how table definition spreadsheet is organized
    • Review UI
    • Review Github project board
    • At next meeting (so devs can try or review first)
      • troubleshoot deployment issues
      • review code in peopledepot/django-root (ignore util and iso-tutorial node)
  • Review issues (or TODO) for assignments
  • Identify potential feature labels #13
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

@ethanstrominger
Copy link
Member

2023-11-10 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

  • Review figma and compare to data model
  • Discuss front end developer engagement (when?)
  • Add tasks to this issue Create list of tasks that we can turn into Initial stories #12
  • Knowledge transfer
    • Review Wiki structure
    • Review how table definition spreadsheet is organized
    • Review UI
    • Review Github project board
    • At next meeting (so devs can try or review first)
      • troubleshoot deployment issues
      • review code in peopledepot/django-root (ignore util and iso-tutorial node)
  • [ ]
  • Review issues (or TODO) for assignments
  • Identify potential feature labels #13
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

@ethanstrominger ethanstrominger mentioned this issue Nov 6, 2023
Closed
20 tasks
@1610saas
Copy link
Member

1610saas commented Nov 16, 2023 •
edited by ExperimentsInHonesty
Loading

2023-11-17 Meeting Agenda

Prework to prep for meeting

  • Add any questions the Dev team has to #266

Recurring items

New Items

  • Review figma and compare to data model
  • Discuss front end developer engagement (when?)
  • Add tasks to this issue Create list of tasks that we can turn into Initial stories #12
  • Knowledge transfer
    • Review Wiki structure
    • Review how table definition spreadsheet is organized
    • Review UI
    • Review Github project board
    • At next meeting (so devs can try or review first)
      • troubleshoot deployment issues
      • review code in peopledepot/django-root (ignore util and iso-tutorial node)
  • [ ]
  • Review issues (or TODO) for assignments
  • Identify potential feature labels #13
  • Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

@ethanstrominger
Copy link
Member

ethanstrominger commented Nov 20, 2023 •
edited
Loading

2023-12-1 Meeting Agenda

Prework to prep for meeting

  • Add any questions the Dev team has to #266

Recurring items

New Items

FYIs

Notes from Meeting

Task Items

@JesseTheCleric JesseTheCleric moved this to In progress (actively working) in P: KB: Project Board Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pwalia1 pwalia1

@ethanstrominger ethanstrominger

@ExperimentsInHonesty ExperimentsInHonesty

@Estherchuks Estherchuks

Labels
category: management complexity: small feature: agenda milestone: missing role: back end dev role: dev lead role: security admin size: 0.25pt Can be done in 1.5 hours or less
Projects
P: KB: Project Board
Status: In progress (actively working)
Milestone
No milestone
Development

No branches or pull requests
6 participants
@pwalia1 @Toe12 @ethanstrominger @ExperimentsInHonesty @1610saas @Estherchuks