You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 1, 2019. It is now read-only.
@trevnorris recently asked on Twitter if the Foundation would be able to hire a writer to summarize threads that run longer than would be easy to read in a timely manner for full comprehension. I assume this would apply to Core and other supporting WGs.
Here's a rough draft of things that I think would need to be addressed - absolutely want feedback from both those who are participating in these threads and those who would be reading the summaries on what the best way to do this is.
Initial Quick Summary Article questions and criteria for developing a sustainable process:
How do we present these articles? For example, are they in the style of a small blog post, a list-style post of the most important and relevant comments?
How do we become alerted of a thread that needs summary? For example, when someone mentions @nodejs/evangelism with a request in the thread, when someone creates an issue here, or via some other method of communication?
At what point in a thread should a summary be needed? Should the summary begin when a decision is made, when discussion is completely finished, or at some other point - such as on a case-by-case basis?
@trevnorris recently asked on Twitter if the Foundation would be able to hire a writer to summarize threads that run longer than would be easy to read in a timely manner for full comprehension. I assume this would apply to Core and other supporting WGs.
Here's a rough draft of things that I think would need to be addressed - absolutely want feedback from both those who are participating in these threads and those who would be reading the summaries on what the best way to do this is.
Initial Quick Summary Article questions and criteria for developing a sustainable process:
//cc @jasnell @dshaw