2023-10-25 - Product Committee
Date
Oct 25, 2023
Participants
@Wes Brown
@Steve Conrad
@Rachel Lawson (Unlicensed)
@Sarah Farooqi
@Sainabou Jallow
@Nico Lueck
Meeting Recording
Recording URL:
Discussion topics
Item | Presenter | Time | Notes |
---|---|---|---|
Review Action Items |
| 5 min |
|
Referencing Changing Content in a GovStack Publication |
|
| How should we reference documentation and other resources for things like the Sandbox, which is a more traditional software project? Content is GitBook and GitHub, both are versioned. Question about how it should be named - Suggestion to use semver (or similar) for internal versioning. Overall GovStack publication should reference a specific version of each component or reference a specific major/minor release (whatever is current). This seems applicable to other resources as well (testing harness, compliance, etc)
|
Use Case Template | @Wes Brown | 10 min | Current Template: GitBook Nico: Consider adding a section of Implementation Examples |
Changes to Product Committee | @Wes Brown | 10 min | GovStack Offerings and Products and Team Proposalarchived (temp page) Use this meeting to organize work around the products similar to how the TC organizes the work around the BBs Next Steps:
Proposed Agenda:
|
Next Meeting |
|
|
|
Meeting Note Rotation |
|
| GIZ, Estonia, Dial, ITU |