-
Notifications
You must be signed in to change notification settings - Fork 99
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
Resources Team: Decide on 2019 objectives #277
Comments
I'm interested in tackling the testing topic - as I've had some thoughts around this. I also think having discoverability of embedded-hal impls is fairly important as well. |
We discussed in yesterday's meeting (#290) that teams should start deciding on If appropriate, you can reserve a time slot during the weekly meetings to have Finally, if any of your goals for this year requires changes in any of the cc @rust-embedded/resources |
Summary of WG meeting at Oxidize: things we'd like to work on this year:
|
2019 finished. Maybe we can create a follow up issue for 2020. Nominating for next week's meeting. |
Closing as we're now well into 2020; if anything outstanding from this list is still relevant please add it to the not-yet-awesome embedded rust list, or create a new issue to track it. |
As part of our 2019 planning, we want to figure out what each team wants to work on this year, including new ideas, items from the 2019 wishlist (#256), and any leftover items from this year.
Let's use this issue to come up with a list of possible items and then prioritise them.
The text was updated successfully, but these errors were encountered: