Migrate go-libp2p-daemon into mono-repo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
This thing is destined to be out of date as long as it lives outside this repo. I think we should be able to get rid of it completely at some point with test-plans, but until we have that replacement we should support it since it is important for js-libp2p tests.
_Originally posted by @MarcoPolo in https://github.com/libp2p/go-libp2p-daemon/issues/273#issuecomment-1377739005_
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.
Research direction
Start by reviewing the go-libp2p-daemon context and how it is used by js-libp2p tests. Clarify the replacement test plans and the migration boundary before changing repository structure. Done means the daemon is supported from this mono-repo until the replacement exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, javascript
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100