[Developer Needs Dashboard] "top developer needs" are all in-progress ideas

MicrosoftEdge / MSEdgeExplainers

Home for explainer documents originated by the Microsoft Edge team

Creative Commons Attribution 4.0 International

1.28k stars 199 forks source link

[Developer Needs Dashboard] "top developer needs" are all in-progress ideas #787

Open matthewp opened 2 months ago

matthewp commented 2 months ago

The titling and description the Microsoft Edge - 2024 web platform top developer needs website denote that it intends to be representative of the needs that web developers have. However, all of the features listed are both in-progress and fairly far along the standardization process. Features that are either not actively being working on, or are in some way stagnate are not represented at all. The implication is that all things that are needed are being actively worked on. I don't think this is close to the truth.

I don't intend to be pedantic. It's unclear to me if this is a naming mistake (call it "top in-progress features"?) or not recognizing those things that are not as far along in the standardization process.

EisenbergEffect commented 2 months ago

I agree with @matthewp on this. The dashboard is showing several things that are already done, things that are in progress, and things that are abandoned, all in a flat list. I think some re-design is in order so that we can capture at least three categories:

Done/Success - Needs that were requested and standards that have shipping in browsers to meet those needs.
In Progress - Needs that were requested, and are actively being worked on, but not yet shipped.
Backlog - Requests that haven't yet been addressed.

Maybe even think of organizing this as a kanban board.

(More fine-grained columns could be added to represent things that still have spec work, things that are shipped in some browsers, etc. But I think at least starting with the three categories I've listed above would really help.)

dandclark commented 2 months ago

Thanks @matthewp and @EisenbergEffect. It’s the intent of the dashboard to track browser support for features that have a fairly stable spec and stable WPT coverage. You’re right that this goal isn’t clearly expressed. We’ll look at modifying the language of the dashboard to make this goal more explicit. Longer-term, I like the idea of adding sub-categories to reflect more fine-grained spec statuses.