-
Notifications
You must be signed in to change notification settings - Fork 6
Project Management
John Levin edited this page Aug 16, 2022
·
5 revisions
Record of Project Management Meeting Agendas/Actions
General attendees:
- John Levin
- Hunter Owens
- Elizabeth Sall
- Benjamin Bressette
- Jameelah Young
- Blake Fleischer
- Joey Reid
Key:
🟢 - actions
✅ - complete actions
- Confirm use of Apache2 license - All
- Any objection to Contributor Covenantas the code of conduct? - All
- Add license to Repository definition
- Create LICENSE.md file
- Add license language to spec files
- create CODE_OF_CONDUCT.md file
- Create contributors.md file (do we want to have this?)
- Move draft CONTRIBUTING.md into repository, replace current PR
- Finalize CONTRIBUTING.md
- Write How to Create Good Issues and Pull Requests
- Add link to LICENSE.md
- Add link to CODE_OF_CONDUCT.md
- Add internal links
- Edit README.md: Add reference/link to CONTRIBUTING.md
- Finalize registration form (add links to CODE_OF_CONDUCT and CONTRIBUTING) - John
- Monitor email contributor registration requests, approve contributors - John
- Add approved contributors to GitHub - Jameelah
- Prepare bi-weekly summary of repository changes, issues, PRs - Jameelah?
- Hold bi-weekly contributor meeting - John
- Send bi-weekly project update to contributors - John
- Convene governance group - John
- Review draft emails to potential contributors and stakeholders - All
- Send email to potential contributors - John
- Send email to all stakeholders - John
- 🟢 Ben will schedule bi-weekly meetings
- 🟢 All put agenda/actions on wiki on github
- ✅ E will put on github (here it is!)
- Discussed what we wanted to have in Github and order of operations:
- Spec from G-18 draft first, proposed changes later.
🟢 Jameelah will get spec up there by end of week and have Cal-ITP team review
- Discussed change management processes.
- Suggested that we start by proposing a process and can evolve from it.
- Initial thoughts after get to 1.0:
- Adopt semantic versioning (wherein a change to 2.0 would imply backwards incompatibility)
- Commit to not getting to 2.0 for 1+ years (some chunk of time) to allow people to adopt it
- Adopt some sort of regular (i.e. quarterly) major change process (backwards compatible)
✅ John will schedule some time with E to go over plan