From a425a60f3adcd3e85da5a263b4250dca08cf1408 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Sat, 23 Mar 2019 16:50:10 -0700 Subject: [PATCH 1/3] Suggest the WICG as a way to propose new features. It can provide initial discussion of a feature and dispatch between the many available repositories on which one could file the issue. Inspired by https://twitter.com/troglotit/status/1109577257738227712. --- whatwg.org/faq | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/whatwg.org/faq b/whatwg.org/faq index 75e125d1c..aa7e8a7c8 100644 --- a/whatwg.org/faq +++ b/whatwg.org/faq @@ -179,11 +179,11 @@ in-progress removal, which may or may not be successful, is the use case. For a good example of how to do this, see this email. -

  • Get more people involved. Open a new issue in - whatwg/html on GitHub that describes the use - cases and their requirements. Ask fellow web developers about their opinions (but remind them of - step 1 above). Adjust the list of use cases and requirements as appropriate. Say which use cases - are important and which are just nice to have. +

  • Get more people involved. Start a thread in the + WICG or open a new issue in whatwg/html on + GitHub that describes the use cases and their requirements. Ask fellow web developers about + their opinions (but remind them of step 1 above). Adjust the list of use cases and requirements as + appropriate. Say which use cases are important and which are just nice to have.

  • Optionally, your work is done at this point. If you have done a good job of the above steps and convinced other people that your use case is an important one to solve, they can do the From 4bfb951795b2149cb82720e63e628c38fcc3e7dc Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Mon, 25 Mar 2019 13:46:00 +0100 Subject: [PATCH 2/3] Suggest whatwg/meta instead of whatwg/html. This point in the process is too early to guess that the solution will end up in HTML. --- whatwg.org/faq | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/whatwg.org/faq b/whatwg.org/faq index aa7e8a7c8..e9f7d265e 100644 --- a/whatwg.org/faq +++ b/whatwg.org/faq @@ -179,11 +179,12 @@ in-progress removal, which may or may not be successful, is the use case. For a good example of how to do this, see this email. -

  • Get more people involved. Start a thread in the - WICG or open a new issue in whatwg/html on - GitHub that describes the use cases and their requirements. Ask fellow web developers about - their opinions (but remind them of step 1 above). Adjust the list of use cases and requirements as - appropriate. Say which use cases are important and which are just nice to have. +

  • Get more people involved. Either open a new issue in whatwg/meta on GitHub or start a thread + in the WICG that describes the use cases and their + requirements. Ask fellow web developers about their opinions (but remind them of step 1 above). + Adjust the list of use cases and requirements as appropriate. Say which use cases are important and + which are just nice to have.

  • Optionally, your work is done at this point. If you have done a good job of the above steps and convinced other people that your use case is an important one to solve, they can do the From 40b622ea88d3d79d0e7457587fd7f191f5a71571 Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Sat, 30 Mar 2019 10:29:17 +0100 Subject: [PATCH 3/3] Suggest people pick the appropriate standard and file issues there. --- whatwg.org/faq | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/whatwg.org/faq b/whatwg.org/faq index e9f7d265e..8f447ea78 100644 --- a/whatwg.org/faq +++ b/whatwg.org/faq @@ -179,12 +179,14 @@ in-progress removal, which may or may not be successful, is the use case. For a good example of how to do this, see this email. -

  • Get more people involved. Either open a new issue in whatwg/meta on GitHub or start a thread - in the WICG that describes the use cases and their - requirements. Ask fellow web developers about their opinions (but remind them of step 1 above). - Adjust the list of use cases and requirements as appropriate. Say which use cases are important and - which are just nice to have. +

  • Get more people involved. Open a new issue in + the appropriate standard's issue tracker on GitHub that + describes the use cases and their requirements. If you're not sure which standard your idea + impacts, use whatwg/meta or start a thread in + the WICG. Ask fellow web developers about their opinions + (but remind them of + step 1 above). Adjust the list of use cases and requirements as appropriate. Say which use cases + are important and which are just nice to have.

  • Optionally, your work is done at this point. If you have done a good job of the above steps and convinced other people that your use case is an important one to solve, they can do the