merging into mxnet repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- machine-learning
Research direction
Start by reviewing the mxnet.cpp project and the MXNet project to determine what “merge” would involve. Clarify the repository, build, and integrated-test boundaries before proposing a plan. Done means the projects have an agreed integration path and future MXNet checkins can be tested against mxnet.cpp.
Written by the indexing model from the issue text.
Description
I propose to merge mxnet.cpp into mxnet project.
- It will attract more attention to mxnet.cpp.
- It will enable integrated test with mxnet, so that future checkins to mxnet will not break mxnet.cpp
- Dominant language
- C++
- Stars
- 113
- Forks
- 78
- 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 dmlc/MXNet.cpp
-
batch scoring in cpp Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
GPU NDarray memory Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·