Update to erlware/erlware_commons upstream.
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
[Placeholder] We currently use chef/erlware_commons forked from metadave/erlware_commons forked from erlware/erlware_commons
https://github.com/erlware/erlware_commons/compare/master...chef:lbaker/fix_for_ftmap Looks like this has the diff from the erlware/erlware_commons fork.
It would be helpful to get the changes merged to upstream.
Aha! Link: https://chef.aha.io/features/SH-3009
Contributor guide
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.
Research direction
Start by reviewing the chef/erlware_commons fork and the linked comparison from master to chef:lbaker/fix_for_ftmap. Confirm which changes are still needed and how chef-server consumes the fork, then use the upstream repository and the SH-3009 feature link to determine the expected handoff. Done means the required changes are merged upstream and the dependency transition is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100