-
Notifications
You must be signed in to change notification settings - Fork 97
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
Impl days at RustFest Paris #90
Comments
I'll be there on Monday and Tuesday and I'd like to focus on the embedded Rust book and the embedonomicon. Also, happy to answer embedded Rust related questions and provide feedback and review embedded crates / projects during that time. |
Hello, if I make to the Rustfest I'll be there on both impl days. I don't know what I'll do yet, but I'm sure we can find a task for me. |
My current plan (which I made before becoming aware of the impl days) is to leave Monday around noon, but I'm considering to change that. I'll have to make that decision closer to the conference though, as I'm not yet sure if circumstances will allow me to stay longer. Assuming I manage to stay for the impl days, I'll probably work on LPC82x HAL and/or embedded-hal, if left to my own devices. Happy to help out with other work, though. |
Here are some tasks I can mentor, but probably not all of them at the same time.
|
I'll be there on both Impl days. I'll probably work on https:/coredump-ch/lpc11uxx-rs. |
I'll be there on monday only. I've not decided on what I'll work, probably on Discovery. I'll bring one. |
This happened! Thanks to everyone who joined us ❤️. Looking forward to see you all again in the next RustFest! |
This ticket is to see who's attending the impl days after RustFest Paris and to try to organize some
work items (related to the 2018 edition milestone) for them to tackle during the impl days.
For starters, comment here indicating which days you'll attend and what you'd be interested in
working on -- it can be anything: embedded-hal stuff, adding support to a development board, binding
a C library / SDK, writing documentation, polishing a no_std crate, etc.
The text was updated successfully, but these errors were encountered: