-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Replace all nonreal values in BCD with version numbers/ranges #206
Replace all nonreal values in BCD with version numbers/ranges #206
Comments
Despite this still being in proposal status, I have been working on this project and making optimal progress on it. I'd say that this project is nearing completion already! |
Great work, Vinyl! 🎉 Currently seeing 215 features that can't be calculated:
|
These PRs will get us a lot closer to this goal: |
We're down to 126 now! 🎉 Details
|
mdn/browser-compat-data#23430 will also be a big step in the progession of this goal! |
We're down to 93 now! 🎉 Details
|
We're down to 11 features! 🎉
|
While web extensions aren't within the scope of this project (and aren't considered for Baseline calculation), I had submitted pull requests to replace Edit: since work is being performed for web extensions as well, and web extensions should be relatively easy in comparison to all the other data, I'm including it in the scope of this project! |
Since this project has been actively worked on and discussed in meetings, I figure that it's past the proposal stage -- as such, I've re-tagged this project accordingly! |
In order to finish this project, we need to
|
Problem statement
The WebDX group has stated that having
true
andnull
as a value in BCD is problematic for Baseline calculation.true
values have also been a source of confusion for many developers, with many asking what “Yes” meant in the compatibility tables.This project is the final chapter of the real values super-goal of BCD.
Proposed solutions
true
To reduce confusion right away, we should replace all true values with the most accurate data we are able to.
The easiest solution is to replace all of the true values with ranged values that match up the date of the browser releases with the date of the commit the feature was first tracked in BCD.
The harder solution is to track down exact version numbers for all of the features.
null
For
null
values, we must track down the version numbers.Task list
Note: the majority of true values are from web extensions, a part of BCD that is not typically maintained other than by the web extensions MDN team.
Priority assessment
More information
Open Web Docs (OWD) is a non-profit collective funded by corporate and individual donations.
In order for this project to happen, please consider donating to OWD at https://opencollective.com/open-web-docs.
For more information on sponsorship and membership tiers, see https://openwebdocs.org/membership/
More information is available at https://openwebdocs.org/.
For questions, please reach out to [email protected].
The text was updated successfully, but these errors were encountered: