Open fitzgen opened 5 years ago
@fitzgen is there a good example of such an issue already that we could use as a template for filing these tracking issues? Might make it a bit easier to get people to take on parts of this :sparkles:
It seems like that the existing issues that fit in this category are quite simple: https://github.com/rustwasm/gloo/issues/6#issue-414841275 Perhaps we should just create them, and more information can be added later.
We don't have a template yet, but creating one would be awesome!
I think most of this would be "mid-level" APIs at least initially, and the big questions to resolve with these crates are:
callback
-based) API look like?Future
- and/or Stream
-based API on top of that?I'm going to knock this work out now.
List generated by scraping platform.html5.org.
Some of these items are not really APIs, for example the CSS roadmap, and others are very niche and probably not often used. Would it be better to create tracking issues for all items, or do it on an ad-hoc basis?
@derekdreery oh that's really good; nice work! What we did for async-std was create dedicated tracking issues; for example streams.
I think creating a tracking issue per-heading would probably work well; then gathering each tracking issue under a shared milestone to track overall progress.
Something we also found worked well was regularly announce these issues on "This week in rust: call for participation". With a little bit of outreach it's probably possible to knock a lot of these out in no-time.
@derekdreery Thanks! I think it would be best to create issues on an ad-hoc basis, so we can ignore things which don't make sense for gloo.
Would be A++++ if someone went through https://platform.html5.org/ and made sure we had an associated tracking issue for each item there (where it makes sense). Lots of potential utility crates!