Groundwork Technical Committee

[willbreitkreutz]

@USACE/groundwork-contributors

Hi all,

To get us out of the ad-hoc cycle, I'd like to set up weekly releases for Groundwork. My plan is to set up a recurring 30 minute call where we can talk about any outstanding PRs that are reviewed and ready for merge, decide which ones we merge, and then do the release once a week. Here's a rough process I'm thinking about:

• PRs should be tagged "docs-only" when they only affect the documentation, in those cases we can merge as we go, since those won't affect any users.
• PRs should be tagged with the semver level that they would incur;
  • patch-bump = bug fixes
  • minor-bump = additions to the library / component api of existing component
  • major-bump = breaking changes to any part of the library
• PRs should be reviewed prior to the release meeting
• PRs should be concise and include changes related to a single topic
• PRs with changes to the library / api should have related documentation updates

I'd like to use these meetings as a steering committee of sorts for groundwork, helping guide where it goes over time. The calls we were having prior to the dev workshop were helpful, and I'd like to continue some of that discussion.

I don't want to add too much process, so this is it for now, but we can flex as the library hopefully gains traction.

I am going to be sending out a webmeeting invitation to those I know who are interested, if you don't get the outlook invite, let me know and I'll get you added.

[willbreitkreutz]

Notes from team discussion:

• Hotfix version - need process for real-time updates to the lib off-cycle in case something is broken.
• Need contribution guide including all PR rules etc...
• Contribution effort / resources is the crux moving forward, need a plan to deal with maintenance.