From 8b5abe43391c1ec62c4ab41cc7c8d363144fd133 Mon Sep 17 00:00:00 2001 From: "pa.pecherskij" Date: Mon, 17 Nov 2025 23:03:04 +0300 Subject: [PATCH 1/3] feat: details about workgroup pillar design document and procedure by which it should be merged --- src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md index 10b4c2819f..1a54c816b7 100644 --- a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md +++ b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md @@ -107,6 +107,10 @@ Conflicts on pull requests that are internal to the workgroup are subjected to t ### Design Documents Workgroups are encouraged to make design documents for their game area. View the [Game Area Design Document Template](../../general-development/game-area-design-doc.md) and the Department Design Document Template on each drafted department for a good document basis. +Game Area / Department Design document (which will describe pillars of design for workgroup dedicated area) should be merged, before workgroup will be considered fully-formed and functional. +Merging such document will mark the fact that maintainers team agreed to give more freedom of action to workgroup upon designated area, and thus it should be accepted by majority of maintainers votes. +Document should be accompanied by separate Discourse thread, in which any other maintainer should be able to request merge delay (for a preiod not more then a week), in case he want to review document and possibly leave change requests, but cannot do it right now. +Document merge should be done upon gettint no requested changes / no merge delay requests for 1 week or more. When a workgroup creates a design document, it is said to be owned by that workgroup. From 0e4319a6f82733098716a8d33e19898505bef2d9 Mon Sep 17 00:00:00 2001 From: Fildrance Date: Tue, 18 Nov 2025 21:04:30 +0300 Subject: [PATCH 2/3] Update src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md Co-authored-by: SlamBamActionman <83650252+SlamBamActionman@users.noreply.github.com> --- .../maintainer/maintainer-workgroup-policy.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md index 1a54c816b7..939ebe887f 100644 --- a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md +++ b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md @@ -107,10 +107,10 @@ Conflicts on pull requests that are internal to the workgroup are subjected to t ### Design Documents Workgroups are encouraged to make design documents for their game area. View the [Game Area Design Document Template](../../general-development/game-area-design-doc.md) and the Department Design Document Template on each drafted department for a good document basis. -Game Area / Department Design document (which will describe pillars of design for workgroup dedicated area) should be merged, before workgroup will be considered fully-formed and functional. -Merging such document will mark the fact that maintainers team agreed to give more freedom of action to workgroup upon designated area, and thus it should be accepted by majority of maintainers votes. -Document should be accompanied by separate Discourse thread, in which any other maintainer should be able to request merge delay (for a preiod not more then a week), in case he want to review document and possibly leave change requests, but cannot do it right now. -Document merge should be done upon gettint no requested changes / no merge delay requests for 1 week or more. +Relevant Game Area / Department design documents (which will describe pillars of design for the workgroup's dedicated area) should be merged before a workgroup will be considered fully-formed and functional. +Merging such a document will signify that the maintainer team has agreed to give more freedom of action to the workgroup in the designated area, and therefore any merge must be approved by a majority of maintainer votes. +The document must be accompanied by a separate Discourse thread, in which any other maintainer is able to request a merge delay (for a period not more then a week), in case they want to review the document but can not do it right away. +The document should be merged upon getting no requested changes / no merge delay requests for 1 week or more, and any existing requested changes have been addressed. When a workgroup creates a design document, it is said to be owned by that workgroup. From 22c3f99171c1dbc743e2f9d49e67a045a6a84e89 Mon Sep 17 00:00:00 2001 From: "pa.pecherskij" Date: Thu, 20 Nov 2025 17:39:45 +0300 Subject: [PATCH 3/3] grammar fixups --- src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md index 939ebe887f..d00dbc818c 100644 --- a/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md +++ b/src/en/wizden-staff/maintainer/maintainer-workgroup-policy.md @@ -109,7 +109,7 @@ Workgroups are encouraged to make design documents for their game area. View the [Game Area Design Document Template](../../general-development/game-area-design-doc.md) and the Department Design Document Template on each drafted department for a good document basis. Relevant Game Area / Department design documents (which will describe pillars of design for the workgroup's dedicated area) should be merged before a workgroup will be considered fully-formed and functional. Merging such a document will signify that the maintainer team has agreed to give more freedom of action to the workgroup in the designated area, and therefore any merge must be approved by a majority of maintainer votes. -The document must be accompanied by a separate Discourse thread, in which any other maintainer is able to request a merge delay (for a period not more then a week), in case they want to review the document but can not do it right away. +The document must be accompanied by a separate Discourse thread, in which any other maintainer is able to request a merge delay (for a period not more than a week), in case they want to review the document but cannot do it right away. The document should be merged upon getting no requested changes / no merge delay requests for 1 week or more, and any existing requested changes have been addressed. When a workgroup creates a design document, it is said to be owned by that workgroup.