summaryrefslogtreecommitdiff
path: root/docs/proposals/README.md
diff options
context:
space:
mode:
authorAnders Leino <aleino@nvidia.com>2025-02-11 02:42:08 +0200
committerGitHub <noreply@github.com>2025-02-10 16:42:08 -0800
commit3c2d46aa1c8575dc046d7457793e77c7a4789093 (patch)
treeb333f6f799b975ca4e18fadd3cec0a144d8ec082 /docs/proposals/README.md
parent133bd259c00984c6a01869f71951a7feb919463a (diff)
Remove the docs/proposals directory (#6313)
* Remove the docs/proposals directory This directory will get added to the spec repository in the following PR: https://github.com/shader-slang/spec/pull/6 This closes #6155. * Remove entry from .github/CODEOWNERS file * Redirect some proposal references --------- Co-authored-by: Yong He <yonghe@outlook.com>
Diffstat (limited to 'docs/proposals/README.md')
-rw-r--r--docs/proposals/README.md18
1 files changed, 0 insertions, 18 deletions
diff --git a/docs/proposals/README.md b/docs/proposals/README.md
deleted file mode 100644
index 4dbf0760c..000000000
--- a/docs/proposals/README.md
+++ /dev/null
@@ -1,18 +0,0 @@
-Proposals
-=========
-
-This directory contains proposals / "RFCs" for Slang language/compiler/system features.
-In general, proposals are used for features that are large or complicated enough that the design and/or plan benefits from being discussed in detail before we commit to making code changes.
-
-## How to make a proposal ##
-
-1. Copy the template doc, `000-template.md` to a new document. Fill in the details of your proposal, and give the document a descriptive name following the same formatting. Leave the number as `000`.
-2. Submit a PR with your proposal doc in the `slang/docs/proposals/ directory` to solicit input from the maintainers of Slang.
-3. Integrate feedback and iterate until you have affirmative approval from maintainers.
-4. Include maintainer approval information and update the proposal status in your proposal header prior to merge.
-
-The maintainer accepting the merge should assign the proposal a number.
-
-Implementation of features large enough to require a proposal doc should not begin until the doc has been accepted and merged.
-
-