Upstreaming some concepts built up in `embedded-time`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Start by reading the contribution guidelines and the related issues #211 and #359, then review the fork and the constructs being considered from embedded-time. The issue does not identify files, tests, or a defined set of changes; completion would require an agreed upstreaming plan and a reviewed feature-gated contribution.
Written by the indexing model from the issue text.
Description
Just now, I forked embedded-hal with the intention of upstreaming some constructs that I've been using in embedded-time. This issue is to put this out there for visibility. If others are working on it, or if I've missed work that makes my fork redundant, this issue should reduce the risk of unfortunate double work.
Some relevant issues
#211
#359
Why I'm doing this
I'm very happy with embedded-time, though it seems to be stale/abandoned (last commit to main: 3 years, little other activity). There are some little (perhaps opinionated?) changes I'd like to see that I'll be making as I upstream into my fork, which I hope to eventually upstream to embedded hal
How upstream?
I will be following the contribution guidelines. I anticipate the initial PR (if all goes well), to put things behind a feature gate so as to be as unintrusive as possible, and as a rule, defer to the WG recommendations.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 282
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-embedded/embedded-hal
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-embedded/embedded-hal#742 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
rust-embedded/embedded-hal#747 · 5 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
rust-embedded/embedded-hal#746 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rust-embedded/embedded-hal#745 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
rust-embedded/embedded-hal#744 · 1 comment ·
All issues in rust-embedded/embedded-hal
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100