The Proposal System is a structured documentation mechanism for submitting formal suggestions to the 996.ICU project. It consists of a standardized template file and a collection of submitted proposal documents stored in the proposal/ directory. The system provides a consistent format for recording community suggestions, technical improvements, and strategic decisions.
For detailed information on the proposal template structure and submission guidelines, see Page 7.1.
The Proposal System serves as the formal channel for submitting structured suggestions to the repository. It fulfills several functions:
Sources: proposal/proposal_template.md12-28
Diagram: Proposal System Directory Structure
Sources: proposal/proposal_template.md1 proposal/proposal_for_expanding_the_anti996license_for_more_fields.md1 proposal/proposal_to_request_github_official_including_996icu_license.md1 proposal/proposal_blockchain_evidence_online.md1 proposal/proposal_roadmap.md1 proposal/proposal_for_other_types_of_work.md1
All proposals follow the standardized template defined in proposal/proposal_template.md1-53 The template consists of a metadata header table followed by eight required content sections.
Each proposal begins with a markdown table containing metadata fields as defined in proposal/proposal_template.md3-10:
| Field | Description | Example Values |
|---|---|---|
| Title | Proposal name | "Proposal Template for 996.icu Projects" |
| Author | Creator username or name | "xiao" |
| Status | Current proposal state | "Draft", "Accepted", "Rejected" |
| Type | Proposal category | "Template", "Proposal", "Technical", "Roadmap" |
| Created | Creation date | "31-Mar-2019" |
| Post-History | Update record | "None" or list of updates |
Following the header, each proposal document contains these sections as specified in proposal/proposal_template.md12-48:
| Section | Purpose |
|---|---|
| Why this Proposal? | States the rationale and motivation for creating the proposal |
| Community Value | Describes the benefit to the 996.ICU community |
| Problems | Lists specific issues being addressed |
| Solutions | Proposes concrete solutions to the identified problems |
| Resource & Requirements | Enumerates resources needed for implementation |
| Actions & Implementation Plan | Outlines step-by-step implementation actions |
| References | Provides links to supporting documentation |
| Copyright | Contains copyright notice (all proposals placed in public domain) |
Diagram: Proposal Document Structure in proposal_template.md
Sources: proposal/proposal_template.md3-10 proposal/proposal_template.md12-15 proposal/proposal_template.md17-21 proposal/proposal_template.md23-28 proposal/proposal_template.md30-33 proposal/proposal_template.md35-37 proposal/proposal_template.md39-41 proposal/proposal_template.md43-47 proposal/proposal_template.md49-52
The Proposal System consists of files stored in the proposal/ directory. As of the current repository state, the directory contains one template file and five submitted proposal documents.
Proposal Directory Contents
| File | Type | Lines | Status | Created |
|---|---|---|---|---|
proposal_template.md | Template | 53 | N/A | 31-Mar-2019 |
proposal_for_expanding_the_anti996license_for_more_fields.md | Proposal | 76 | Draft | 07-Apr-2019 |
proposal_to_request_github_official_including_996icu_license.md | Proposal | 118 | Draft | 1-April-2019 |
proposal_blockchain_evidence_online.md | Technical | 77 | Draft | 19-April-2019 |
proposal_roadmap.md | Roadmap | 54 | Draft | 15-April-2019 |
proposal_for_other_types_of_work.md | Proposal | 49 | Draft | 31-04-2019 |
All proposal files follow the naming convention proposal_<descriptive_name>.md and use the structure defined in proposal_template.md.
Sources: proposal/proposal_template.md1-53 proposal/proposal_for_expanding_the_anti996license_for_more_fields.md1-76 proposal/proposal_to_request_github_official_including_996icu_license.md1-118 proposal/proposal_blockchain_evidence_online.md1-77 proposal/proposal_roadmap.md1-54 proposal/proposal_for_other_types_of_work.md1-49
The proposal workflow follows a standard GitHub pull request process. Proposals are submitted as new markdown files in the proposal/ directory.
Diagram: Proposal Submission and Review Process
The Status field in the proposal header tracks the current state. As seen in the existing proposals, all current proposals maintain "Draft" status proposal/proposal_template.md7 proposal/proposal_for_expanding_the_anti996license_for_more_fields.md8 proposal/proposal_to_request_github_official_including_996icu_license.md9
Sources: proposal/proposal_template.md7 proposal/proposal_template.md39-41 proposal/proposal_for_expanding_the_anti996license_for_more_fields.md8 proposal/proposal_to_request_github_official_including_996icu_license.md9
The repository contains five submitted proposals as of the current state. All proposals follow the template structure and maintain "Draft" status.
Diagram: Proposal Types and Topics
| Proposal File | Author | Created | Target System | Focus |
|---|---|---|---|---|
proposal_for_expanding_the_anti996license_for_more_fields.md | ChuangSheep | 07-Apr-2019 | License | Extend license to video/text content |
proposal_to_request_github_official_including_996icu_license.md | ff4415 | 1-April-2019 | License | Get license added to choosealicense.com |
proposal_blockchain_evidence_online.md | Eric Chow | 19-April-2019 | Evidence | Use EOS blockchain for evidence storage |
proposal_roadmap.md | Tooodis | 15-April-2019 | Strategy | Overall movement roadmap and tactics |
proposal_for_other_types_of_work.md | xloypaypa | 31-04-2019 | Scope | Expand support to other professions |
Sources: proposal/proposal_for_expanding_the_anti996license_for_more_fields.md7-11 proposal/proposal_to_request_github_official_including_996icu_license.md7-16 proposal/proposal_blockchain_evidence_online.md6-10 proposal/proposal_roadmap.md6-10 proposal/proposal_for_other_types_of_work.md6-10
To submit a new proposal to the repository, contributors create a new markdown file following the template structure.
proposal_<descriptive_name>.mdproposal/ directoryDiagram: Required Fields and Sections
The template defines the following sections:
Sources: proposal/proposal_template.md1-53
The Proposal System interacts with other components of the 996.ICU repository:
Diagram: Proposal System Interactions
Sources: proposal/proposal_for_expanding_the_anti996license_for_more_fields.md14-31 proposal/proposal_to_request_github_official_including_996icu_license.md18-28 proposal/proposal_roadmap.md12-34
The Proposal System serves as the formal mechanism for suggesting improvements to the 996.ICU project. It provides a structured template and process for community members to contribute ideas, address issues, and enhance the project's effectiveness in combating the 996 work culture. Through this system, the project can evolve in a deliberate, community-driven manner while maintaining a clear record of decisions and discussions.
Sources: proposal/proposal_template.md12-21
Refresh this wiki