Anyone may submit an idea for a policy or program following the staging process outlined below. Proposals should start in the proposals/stage-0/ directory. To submit a proposal, create a new directory in proposals/stage-0/ with a descriptive name, and create a README.md with the information outlined in the Staging proposal template.
For Stage 0 proposals a README.md is sufficient, for later stages please include the appropriate supporting documents as well.
The proposal will be evaluated at committee meetings and stage changes will occur at those times.
Proposals in this stage are summarized in a markdown file. They have a short name and an identified 'champion' - at least one person who will be pushing the proposal through to its conclusion. They have a rough description of the program idea or policy, what resources would be needed to execute it, what committee or role is responsible for overseeing it, ideas for metrics, execution, and so forth. They have clear language about which group or groups the program/policy will serve. The purpose of this stage is to capture the spirit of an idea the community may want to explore further, and to begin thinking about implementation ideas or process questions that need to be answered.
Proposals in this stage are written up in the style of the formal policy or program language. They include examples of the program idea or policy in action, with clear steps and guidelines. They include the steps that will need to be taken to initially implement the idea or policy. The purpose of this stage is to refine the policy, make sure all stakeholders (including the governing board) have had a chance to review and request changes, and determine whether further iteration is needed.
Proposals in this stage are nearly complete. They may be in a pilot or trial-run mode for a limited audience, or pending legal review. They may be awaiting budget approval. The purpose of this stage is to complete any operational checks, such as acquiring budget, access, or governing board approval if needed, before launching the program.
The proposal is now an adopted policy or program of the CHIPS Alliance TAC, and is owned by the committee or role identified. It is expected that the policy or program will be re-evaluated on some regular basis and deprecated if need be.
The following template can be used when creating a proposal's initial README.md file.
# Proposal name
### Abstract
*A rough description of the proposal*
### Champion
*Who will ensure the proposal moves through to a final decision?*
### Required resources
*What will be needed in order to execute? (Time, money, etc)*
### Who will execute the proposal?
*Who will be responsible for setting up and running the proposed process?*
### How is success measured?
*How and when will you know this process is working?*
### Why is this proposal important?
*What existing or anticipated issue does it address?*
### Unresolved questions
*Are there any current objections or concerns?*
### What is necessary to complete this proposal?
*Everything still required to reach Stage 3 / implementation.*