[patcg.github.io] Pull Request: Adding a clear incubation process and flow

AramZS has just submitted a new pull request for https://github.com/patcg/patcg.github.io:

== Adding a clear incubation process and flow ==
This PR intends to alter the charter to include a means to handle incubation for specific in-scope work. 

Notable alterations are: 

- The addition of a Document Incubation `h3` section to cover the means and purpose of the incubation process. 
- Added note that Adoption process may or may not take up documents from incubation and in either case still requires a clear group consensus to enter the adoption process. 
- Promoted "Feature Work" section to an `h2` heading and made modifications to make it clear that the process of migration and discontinuation applies to both Adopted and Incubated documents. 
- Made it clear that all incubated documents are covered by the CLA. 
- Incubation work does not require the expectation of interoperability, as it is too early in the process to assume a work under incubation would be ready for such an expectation. 

Goals of the alteration:

- To acknowledge that PATCG's constituency is different enough from WICG that there is value in having an incubation process within this CG. 
- To give us tools to facilitate the work on proposals that we believe--if they reach a viable state for this group to reach consensus on and this group has decided to adopt them--may be strongly within the interests of this CG. 
- To better organize work into this space and provide a clear set of tools for work within this space to be properly identified and discussed. 
- To create opportunities for such work to use our facilitation and IPR tools in the form of having a repo within this org and the ability to create ad-hoc meetings for PATCG's membership. 

There are a number of things we want to make sure that this does not imply:

- This does not intend to imply that all relevant proposals **must** be within this group or that their incubation process **must** come through this group's incubation process. 
- This does not intend to imply that private ad technology proposals can't be incubated by WICG
- This does not intend to imply that private ad technology proposals must immediately move from another space or from WICG to our process
- This does not intend to imply that every possible private ad tech proposal is best housed within our incubation process. 
- Most of all it should be clear that entering the incubation process requires consensus under our existing rules. I do not intend to imply that this process should be a free-for-all. 

If you feel this alteration implies any of these things, please point out how it does so we can make alterations for clarity. 

This is a draft and I anticipate and hope for feedback and refinement from the group. 

Final merging is contingent on consensus from the group. 

See https://github.com/patcg/patcg.github.io/pull/7


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 14 March 2022 17:54:40 UTC