AmeliaBR
commented
4 years ago Trusting GitHub that there are no merge issues. ReSpec should let us know if we've broken too many cross-references!
As for what other people are working on:
I've been completely off, energy-wise, for the past two weeks, and haven't done anything to speak of. I'm also taking the weekend for personal time. My priority for next week will be to get the file formats & server API capabilities sketched out, with matching use cases. I'll probably go through the remaining "status: suggestion" discussion pages at the same time & try to turn them into at least placeholders.
@NickFitz got some basic demos working with the Apple and Bing APIs this week. You could play around with those demos and update your capability summaries.
Other things you could do next:
-
Keep filling out the "required capabilities" for each use case. Add descriptions of use cases which are currently placeholders only.
-
Make sure that we have matching capabilities wherever they make sense. E.g., for some of the end-user use cases, we have API capabilities that could be used by a developer to recreate that capability, but not a discussion of whether the capability is included in the default widget.
-
Create GitHub discussion pages for the capabilities.
-
If you want a change of pace, work on any of the ToDos in the preprocessing script. E.g., generate the "supported use case" lists for each capability based on the "required capabilities" lists in the use cases.
@NickFitz, let us know if any of that overlaps with anything you're likely to work on in the next little while.
nchan0154
Small one this week! This PR includes assigning capabilities and draft text for the content author use cases. Please let me know if this conflicts with anything, Amelia, I'm happy to deal with the merge.
Can I get an update on what people are currently working on so I don't step on any toes? @AmeliaBR @NickFitz and anyone else working on the report text