Move embedded-hal-mock to rust-embedded?

[dbrgn]

Hello folks. Due to family and work obligations, I have not had the time to maintain embedded-hal-mock properly in the last year. Case in point: https://github.com/dbrgn/embedded-hal-mock/pull/131#issuecomment-3434119027 This is a situation that I'm not happy with, and it also hinders the development of the testing ecosystem in the embedded space: People rely on the library, but it doesn't get pushed forward as fast as it should. When I search on GitHub for TOML files containing "embedded-hal-mock", I find 484 results. And on crates.io there are 246 reverse dependencies.

Would rust embedded be willing to adopt the project and maintain it?

[adamgreig]

Tagging @rust-embedded/hal / @rust-embedded/embedded-hal who would decide on this.

[eldruin]

Thank you so much for your work on this so far! embedded-hal-mock is central to platform-independent driver development so it definitely sounds appropriate to me, yes. I would keep it in its own repository in order to keep the history, just under the r-e org.

[dbrgn]

Thanks for the kind words, @eldruin! I would be happy to simply transfer the repository to the rust-embedded organization. I'm also willing to remain co-maintainer, right now I don't have any time to do anything meaning but maybe in the future when I can come back to driver development.

[BartMassey]

I think REWG should maintain this, and @dbrgn I would love to keep you as a co-maintainer. That said, a plan for who and how to resolve the current backlog would be really helpful. I don't understand this crate well enough to be much help myself…

[dbrgn]

@BartMassey I'm happy to stay as co-maintainer and would contribute again once my time budget changes. Additionally, @ryankurte and @newAM have also helped with maintenance and contributions, they might also still be interested in helping out.

In any case, the library is fairly simple, should not take anyone too long to get started. The basic idea is that you can queue expectations, which are then checked once a call to one of the HAL's methods is done.

The biggest helping factor is knowledge on how the underlying protocols and the HAL work.

[ryankurte]

hey, appreciate all your work on e-h-m and definitely think it'd be a good addition to the REWG! i am slowly recovering from a bad case of higher education so aiming to be around the REWG again more to help up with maintenance too.

[BartMassey]

REWG discussed today: all comments were favorable. Needs a vote from the HAL Team: somebody set one up?

[eldruin]

Sure, thank you. This needs a team vote by the @rust-embedded/hal team:

• [ ] @Dirbaio
• [x] @eldruin
• [x] @MabezDev
• [x] @ryankurte
• [x] @therealprof

[BartMassey]

Excellent: this passes looks like. So now someone just needs to move the repo.

[dbrgn]

I think somebody needs to (temporarily) give me permission to create repositories on rust-embedded in order to do the transfer.

[BartMassey]

We'll move it at the meeting Tuesday. Thanks much!

[eldruin]

@dbrgn you can transfer it to me, for example, and I will transfer it to the org.

[BartMassey]

@dbrgn Adam says he's temporarily given you the permissions needed for the transfer. Give it a try when ready.