Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda for Oct 13 meeting #209

Closed
foolip opened this issue Oct 12, 2022 · 2 comments
Closed

Agenda for Oct 13 meeting #209

foolip opened this issue Oct 12, 2022 · 2 comments
Labels
agenda Agenda item for the next meeting

Comments

@foolip
Copy link
Member

foolip commented Oct 12, 2022

Here's the agenda for our meeting tomorrow:

Previous meeting: #190

@foolip foolip added the agenda Agenda item for the next meeting label Oct 12, 2022
@foolip
Copy link
Member Author

foolip commented Oct 13, 2022

Brief meeting notes

Present: @chrishtr @foolip @gsnedders @jensimmons @jgraham @nairnandu @rachelandrew @robnyman @tantek

MDN short surveys design

#196

@foolip: could this be useful?
@jensimmons: yes, seems like a good approach. like the bucketing too.
@jgraham: I'm more skeptical that we'll get useful insight, but I'm not opposed to trying. Some things like bug fixes are not going to get a lot of votes. Could someone with a web developer hat on try to answer this survey?
@rachelandrew: yes, but there are very different types of web developers. I have a very different idea of what's useful compared to someone who mainly work with frameworks. It's another input, don't think it hurts to have more input. Then we can see where there's overlap in the feedback we see.
@jgraham: are we using a language we expect people to understand?
@rachelandrew: I think so, in responses to State of CSS and similar people are pretty clear in their responses.
@jensimmons: I can imagine some people being frustrated by the grouping. Like pseudo-classes. On the question, "implemented or improved across browsers", it gets complicated to compare those two categories. Can we implement more that the point is interoperability? Something like "improved across browsers (bug fixes and finishing implementation)"?
@chrishtr: agree with that, to focus on interop and their needs.
@jensimmons: Maybe "what would be most helpful for your work?"
@robman: I would guess that to most developers very few things stand out, so it wouldn't be so hard to pick out a top 3. If someone spikes that we didn't expect, that fills in our gaps.
@foolip: I'll update the issue again on Monday, and keep the lists to 20, and circulate again. Should have a preview before we go live.

Score for each Focus Area

#198

@jensimmons: proposal to add this to the score tables, as a 4th column.
@foolip: I think it makes sense to prototype, next steps would be to file an issue on wpt.fyi and ask how much work it would be.
@jgraham: makes sense to show how much progress we've made as a platform
@jensimmons: we could roll this out with with the 2023 dashboard if that works out with timing.

Add subtotals to the 2022 dashboard

#205

@jensimmons: This comes from questions about why we're nowhere near 100 when we've worked hard to pass all the tests. Will need to discuss more for 2023, but here the proposal is to add these subtotals. It would quickly make it clearer.
@tantek: I think the larger issue is communication rather than metrics. I empathize, a lot of value placed on things that are easily measured. Here, the difference between 80s and 90s is whether we're making progress on the investigations. Those are hard problems (a few) that we've decided to include, as a higher bar for progress. I think we need better tools for internal and public communication.
@jensimmons: I appreciate that, but I think that ship sailed with Compat 2021.
@tantek: We saw this as a bug in Compat 2021, and this (investigation efforts) was an attempt to improve on that.
@jgraham: There are specific actions people can take to move the investigation effort scores. It will improve everyone's scores.
@jensimmons: The proposal isn't to change the scores at the top, but to add subtotal.
@foolip: This should be easy to prototype, and I think it would be an improvement.
@tantek: I think we should also include a subtotal for the investigation areas. I'd like to see a more concerted efforts internally at our orgs, for putting time and effort into the investigation scores. We could bump them to the top?
@foolip: I'll file issues for wpt.fyi for these requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda Agenda item for the next meeting
Projects
None yet
Development

No branches or pull requests

1 participant