Closed jwflory closed 1 year ago
Linking some files here that need to be updated to this end:
https://github.com/DPGAlliance/DPG-Standard/blob/main/CHANGELOG.md https://github.com/DPGAlliance/DPG-Standard/blob/main/governance.md
Let's discuss in the DPG reviewer check-in and scope this out > update this thread? Adding to the agenda.
Linking this for discussion https://github.com/DPGAlliance/DPG-Standard/issues/124
Program management on the standard, https://github.com/orgs/DPGAlliance/projects/3/views/2
Hi, closing this issue since we have deployed the Projects board and labels for the Standard updates.
Summary
Identify a cadence or release schedule for new updates and changes made to the DPG Standard.
Background
In the April Standard Council meeting, @prajectory mentioned the ongoing work to codify the governance around the Standard and the process used to make changes and revisions. One possible way to streamline this is by identifying a cadence in which we periodically review feedback and proposals made to the DPG Standard, and if needed, release a new update. Ideally, as a Standard, formal updates are few and infrequent, but a regular cadence allows us to work through a backlog of feedback.
For context, there are many other FOSS projects where this might be modeled. The CHAOSS Project, which produces metrics about open source community health, releases twice a year through a formal review process. Fedora Linux, a DPG, makes two major releases of their operating system appx. every six months. Perhaps twice yearly or quarterly could be a good cadence depending on the backlog and capacity of the team.
Details
A few thoughts on how this work might be completed:
Outcome