311 Data Weekly Engineering Meeting

ryanfchase commented 3 weeks ago

Overview

Meeting agendas for the weekly 311 Data Engineering member meetings, useful links and other resources

Agenda Quick Links

2024-05-08

Resources/Instructions

Template for weekly meeting's comment.

## YYYY-MM-DD - 311 Data Weekly Engineering Meeting
_[Back to Top](#)_

### Next Week's Announcement Volunteer
- (replace with @ github handle)

### Quick Links
- [Open PRs](https://github.com/hackforla/311-data/pulls)
- [Open Github Issues](https://github.com/hackforla/311-data/issues?q=is%3Aopen+is%3Aissue+label%3A%22Role%3A+Frontend%22+no%3Aassignee+-label%3ADependency+-label%3Adraft+-label%3AEpic)

### Topic requests/questions:

### Action Items:

### Resources / Links:

### Attendees

- [ ] Ryan C
- [ ] Johnny
- [ ] Shannan
- [ ] Billy Phan
- [ ] Drake

ryanfchase commented 3 weeks ago

2024-05-08 - 311 Data Weekly Engineering Meeting

Back to Top

Weekly Announcement Volunteer

@Skydodle

Quick Links

Topic requests/questions:

[x] Weekly Engineering agenda
[x] Dev team announcements person
[x] Create open role on Engineering CoP
[x] Bug-hunt ticket
[x] Contact Form
[x] Discuss new ticket goals

Action Items

[ ] brainstorm documentation issues (3 or 4 updates / new pages)

Resources / Links:

More info on today's Topic Requests

``` 1. Weekly Engineering agenda - we can briefly list all open tickets here, list PRs here, list goals here 2. Dev team announcements person: - designated member to announce PRs, open tickets, etc (weekly rotation) - assign this person at the weekly meeting 3. Our plan to get new members: - create an Open Role on Engineering CoP - to justify this, we should make sure we have available tickets, and good onboarding + documentation 4. Bug-hunt & Code Quality tickets - a live forever ticket that gets reassigned every week, challenge to break the code - person assigned can do a bug writeup - can be a good first issue - Can document proposed solutions to these bugs and prioritize them for later 5. Contact Form - Create a Github access token for 311 Data dev 6. New Ticket Goals - try and maintain a number of Good First Issues (e.g. 3-5) - The number of available tickets should roughly match number of active devs ```

Attendees

[ ] Ryan C
[ ] Johnny
[ ] Shannan
[ ] Billy Phan
[ ] Drake

ryanfchase commented 2 weeks ago

2024-05-18 - 311 Data Weekly Engineering Meeting

Back to Top

Next Week's Announcement Volunteer

@ryanfchase

Quick Links

Topic requests/questions:

[x] live forever bug reporting ticket

Action Items:

Resources / Links:

Attendees

[ ] Ryan C
[x] Johnny
[ ] Shannan
[ ] Billy Phan
[ ] Drake

ryanfchase commented 1 week ago

2024-05-22 - 311 Data Weekly Engineering Meeting

Back to Top

Next Week's Announcement Volunteer

Quick Links

Topic requests/questions:

Action Items:

review Engineering Documentation
- CONTRIBUTING.md
- README.md

Resources / Links:

Attendees

[ ] Ryan C
[ ] Johnny
[ ] Shannan
[ ] Billy Phan
[ ] Drake

ryanfchase commented 1 week ago

Posting our meeting notes from Wednesday...

Notes on Readme

311-Data v2 --> 311-Data v1.2
update the screenshot of the app
remove Matplotlib, Polars, Numpy
remove Google Colab
remove Observable (tbd)

Notes on contributing.md

if you run into issues, post onto #311-data-engineering, (not open new issue -- we dont have infrastructure for this)
feature branching format: [ issueId-Title, issueId-MinimalDescription ]

TODO

prune branches on 311-Data
see if we want to implement any linting rules, PR rules for github actions
Getting started, it would be nice if there was a directory tree with main components, and some descriptions of what they do

hackforla / 311-data