Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate go-libp2p-daemon into mono-repo #1989

Open
MarcoPolo opened this issue Jan 10, 2023 · 1 comment
Open

Migrate go-libp2p-daemon into mono-repo #1989

MarcoPolo opened this issue Jan 10, 2023 · 1 comment
Labels
P2 Medium: Good to have, but can wait until someone steps up

Comments

@MarcoPolo
Copy link
Collaborator

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 libp2p/go-libp2p-daemon#273 (comment)

@p-shahi p-shahi added the P2 Medium: Good to have, but can wait until someone steps up label Jan 17, 2023
@lidel
Copy link
Member

lidel commented Jan 18, 2023

We have two "libp2p daemons":

In both cases, they are not actively maintained, nor kept up-to-date, IPFS/libp2p teams are reactive (often whoever cares the most does the heavy lifting of refactoring to work with the latest go-libp2p).

This is not sustainable, delivers bad UX/DX, and is also a lost oportunity – both could act as useful examples of how to use this go-libp2p library.

Whatever we do for the first, we should also do for the second.

@MarcoPolo @marten-seemann thoughts on moving both to this repo, under examples?

  • examples/test-daemon
  • examples/relay-daemon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Medium: Good to have, but can wait until someone steps up
Projects
None yet
Development

No branches or pull requests

3 participants