Merge pull request #2062 from w3c/ege-proposals-reorg

Proposals Folder Explanation
w3c · Dec 18, 2024 · eaa2435 · eaa2435
2 parents 1aee54f + 7124a13
commit eaa2435
Show file tree

Hide file tree

Showing 6 changed files with 34 additions and 1 deletion.
diff --git a/proposals/README.md b/proposals/README.md
@@ -0,0 +1,20 @@
+# Proposals to the WoT TD Specification
+
+This folder contains proposals that do not fit a single issue or pull request when the discussions take place.
+Based on the content of these proposals, big features can be evaluated in a defined folder and not mix with the editor's drafts.
+
+The status of a proposal is indicated next to it with the following meanings:
+
+- In Progress: The proposal is being actively discussed
+- Rejected: The proposal is not accepted by the TF
+- Paused: The proposal is not rejected but there is no active work happening on it
+- Accepted: The proposal is in use by the TF
+- Retired: The proposal was accepted and used but it is not relevant anymore and thus is retired.
+
+| Proposal Name and Link                               | Status   |
+| ---------------------------------------------------- | -------- |
+| [Simplified TD](./simplified-td/index.html)          | Rejected |
+| [Hypermedia 1](./hypermedia-control/README.md)       | Paused   |
+| [Hypermedia 2](./hypermedia-control-2/README.md)     | Paused   |
+| [Hypermedia 3](./hypermedia-control-3/README.md)     | Paused   |
+| [Project Management](./project-management/README.md) | Accepted |
diff --git a/proposals/hypermedia-control-2/README.md b/proposals/hypermedia-control-2/README.md
@@ -1,5 +1,8 @@
 # Hypermedia Control on the Web of Things
 
+> [!NOTE]  
+> Proposal Status: Paused
+
 This proposal introduces a generic hypermedia control framework for the Web of Things (WoT) that is similar to that of @vcharpenay but uses static TDs and focuses on action affordances.
 The ideas were introduced also [at this comment](https://github.com/w3c/wot-thing-description/issues/302#issuecomment-627500213)
 

diff --git a/proposals/hypermedia-control/README.md b/proposals/hypermedia-control/README.md
@@ -1,5 +1,8 @@
 # Hypermedia Control on the Web of Things
 
+> [!NOTE]  
+> Proposal Status: Paused
+
 This proposal introduces a generic hypermedia control framework for the Web of Things (WoT).
 
 TL;DR:

diff --git a/proposals/hypermerdia-control-3/README.md b/proposals/hypermerdia-control-3/README.md
@@ -1,5 +1,8 @@
 # Yet another Action Model
 
+> [!NOTE]  
+> Proposal Status: Paused
+
 This proposal wants to overcame problems around the other proposals of a new hypermedia action model. In particular, it
 should address the following concerns:
 

diff --git a/.../project-management/project-management.md → proposals/project-management/README.md b/.../project-management/project-management.md → proposals/project-management/README.md
@@ -1,5 +1,8 @@
 # WoT Project Management Process
 
+> [!NOTE]  
+> Proposal Status: Accepted
+
 The main question to answer is "How do we organize the work?".
 We want to have one place to look for the list of "work" to do in a short period.
 To do that, a prioritization should happen and should be aligned with use cases and requirements.
@@ -50,7 +53,7 @@ The lifecycle is also reflected in a table below. The example below can be consi
   - Ideally, we should discuss our requirements and what people want to see. Mandating a mechanism that the moderators like but is disliked by everyone else should be avoided.
   - The goal is to make it more systematic than "copy-pasting the agenda, look into issues and PRs"
   - The process for generating features from use cases should be taken into account
-  - We can use a tool like GitHub Projects. A premature example is available at https://github.com/orgs/w3c/projects/31
+  - We can use a tool like GitHub Projects. A premature example is available at <https://github.com/orgs/w3c/projects/31> (this project is now deleted and an up to date one is available at <https://github.com/orgs/w3c/projects/80>)
 - Mahda Noura: Only assigning an issue is not enough, because the number can increase and we can lose oversight/prioritization.
 - Cristiano Aguzzi: Assigning should happen when you know that person can do it in 1-2 weeks.
 - Jan Romann: Splitting issues definitely helps. We should limit the workload of an issue in the beginning or use checkboxes per small item and open a "spinoff" issue.

diff --git a/proposals/simplified-td/index.html b/proposals/simplified-td/index.html
@@ -63,6 +63,7 @@
     </style>
   </head>
   <body>
+    <p class="note">Proposal Status: Rejected</p>
     <section id="abstract">
       <p>
         This document summarizes the discussions on simplifying the JSON-LD&nbsp;1.0-based