2023-10-25 - Product Committee

5 min

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)

1. GovStack will reference a specific branch/space which can be updated by the Sandbox so that the 23Q3 publication will reference up-to-date information, even if it has changed since the original publication

@Wes Brown

10 min

Current Template: https://app.gitbook.com/o/pxmRWOPoaU8fUAbbcrus/s/YLLEfCKTnmzAMDSDzJJH/use-cases/less-than-use-case-template-greater-than

Nico: Consider adding a section of Implementation Examples

@Wes Brown

10 min

GovStack 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:

1. Document the updated scope of the meeting - Wes

2. Invite the product and team owners to the PC - Wes

   1. Also notify generally so that others can show up if they are interested

Proposed Agenda:

• Selected Team Updates (2-3 teams per meeting)

  • Status update, active tasks, questions/comments

• General Project Discussions

  • Discussions about priorities, processes, and concerns

  •  

• Discuss the eMarketplace building block and how to include it in the Market Linkage use case

• Discuss working on a procurement platform reference use case

GIZ, Estonia, Dial, ITU