Screenshot of the TC39 website
As the website is currently an MVP and extremely simple, we have plans to increase it. These plans include a group of documentation about how we work. We are going to experiment with other features as the require arises.
Both most requested items with regard to sources were Learning Resources and a Web site. These two are linked, but need very different types of work. Since this particular clearly highlighted the need for a website, all of us began work on this right away.
Aggregated tags in response to the question “ What would you like to see as a source of the language specification process? ”
We identified different types of customers: Learners who are discovering the standards for the first time, Observers of the specification that are watching proposal advancement, and Research Users who need a central place where all of the significant documents are available. The website was designed around these customers. In order to not overwhelm people with details, the MVP is specifically centered on the most pertinent information, namely plans in Stage 3 of our procedure. Links are contextualized in order to assist individuals understand what documents they are looking at.
Stage 3 Suggestion List
The web site is very simple, but gives us the starting point from which to move forward. We have been continuing to work on documenting our own process. We hope to make more of these types of documents publicly available soon and also to incorporate them into the website with time.
Aggregated tags in response to problem “ Is there something we can learn better, or that you find particularly annoying right now? ”
Included in the survey, we collected emails to get in touch later, as we were uncertain how many responses we would get. The particular goal was to better understand particular concerns. However , we had an overwhelming quantity of feedback that pointed us within the direction we needed to go. Right after reviewing this, we decided towards keeping this personal information and to demand feedback publicly on a case-by-case schedule. Thank you to everyone who took part.
We are looking forward to your own feedback and comments. This task was community-driven— thank you to everybody who made it possible!