Skip to content
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

Embedded WG meeting, June 25 #109

Closed
japaric opened this issue Jun 20, 2018 · 3 comments
Closed

Embedded WG meeting, June 25 #109

japaric opened this issue Jun 20, 2018 · 3 comments

Comments

@japaric
Copy link
Member

japaric commented Jun 20, 2018

6-7 PM CEST on #rust-embedded on irc.mozilla.org

Agenda.

This meeting is open for anyone to attend. If you'd like to bring up any issue / topic related to embedded Rust leave a comment in this issue so we can add it to the agenda.

@rudihorn
Copy link

rudihorn commented Jun 20, 2018

I would like to suggest a topic on somehow improving the way small, but annoying, issues are handled. Currently it seems like PR's and issues are piling up with e.g. the STM32F103xx-hal and some other crates and I feel like there should be more pushing to resolve such issues.

A few examples of issues I am talking about:

  • STM32F103 not on crates.io (preventing any further crates with examples from being pushed)
  • Embedded-HAL having any forms of input pins marked as unproven / general difficulty of being able to use input pins (also in Linux-embedded-hal)
  • Broken docs PR's not being pulled (Disable Jekyll to enable examples in Github pages japaric/stm32f103xx-hal#85)
  • I2C missing / despite some PR's seemingly being available

It would be nice if we could get the very basics working, even if some of it does have to be broken at some stage. I get the feeling some of this may be related to @japaric being very busy, but in this case it would be nice if we could find others to merge pull requests etc. for some of these "core" projects.

@jonas-schievink
Copy link
Contributor

@rudihorn #46 is related, but doesn't mention the crate.

@japaric
Copy link
Member Author

japaric commented Jun 28, 2018

This meeting happened! The logs have been pushed into this repository.

@rudihorn We didn't have time to discuss the issue you brought up but we have scheduled it for the next meeting (which is a video meeting) cf. #110.

@japaric japaric closed this as completed Jun 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants