Skip to content

Commit 162e6ce

Browse files
committed
Flesh out the README
1 parent faa00dc commit 162e6ce

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

+12
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,18 @@
22

33
This project tracks organize developer signals (interest, needs, wants, frustrations) around web platform features. The work is done within the [W3C WebDX Community Group](https://www.w3.org/community/webdx/).
44

5+
Signals is defined broadly to allow for any available data about web developers to be considered, and typically fall into one of these categories:
6+
7+
- Survey results, for example from [State of CSS](https://stateofcss.com/) or [MDN short surveys](https://github.com/web-platform-tests/interop/issues/245)
8+
- Developer interviews, such as those done for the [MDN Browser Compatibility Report 2020](https://mdn.dev/archives/insights/reports/mdn-browser-compatibility-report-2020.html)
9+
- Browser bugs, including upvote/star counts
10+
- Reactions on GitHub issues relating to web platform features
11+
- Blogs, podcasts, or social media
12+
13+
To the extent possible, signals will be organized around [`web-features`](https://github.com/web-platform-dx/web-features).
14+
15+
This project is only about organizing signals, not about conducting or coordinating research. For that, see the [WebDX research workstream](https://github.com/web-platform-dx/developer-research).
16+
517
## Background
618

719
A discussion on [organizing developer signals around features](https://github.com/web-platform-dx/developer-research/issues/31) led to the creation of this project, see that discussion for more background.

0 commit comments

Comments
 (0)