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

Standardized Readme #72

Closed
wants to merge 3 commits into from
Closed

Conversation

RichardLitt
Copy link
Member

@RichardLitt RichardLitt commented Jun 21, 2016

@RichardLitt RichardLitt added the need/review Needs a review label Jun 21, 2016

# Contribute
libp2p is the product of a long and arduous quest of understanding -- a deep dive into the internet's network stack, and plentiful peer-to-peer protocols from the past. Building large scale peer-to-peer systems has been complex and difficult in the last 15 years, and libp2p is a way to fix that. It is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradeability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did you put this all into one line?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was already in one line?

@RichardLitt
Copy link
Member Author

@whyrusleeping Word on this?

@whyrusleeping whyrusleeping added the help wanted Seeking public contribution on this issue label Aug 19, 2016

`go-libp2p` repo will be a place holder for the list of Go modules that compose Go libp2p, as well as its entry point.

## Examples

Examples can be found on the [libp2p-examples repo](https://github.com/whyrusleeping/libp2p-examples/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #133 as well

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be merged automatically, with #133. Any comments on this PR? @hsanjuan how does it look, otherwise?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'm already a fan of your standarized readmes :)

@whyrusleeping whyrusleeping added the status/ready Ready to be worked label Nov 28, 2016
===================
# go-libp2p

![](https://raw.githubusercontent.com/diasdavid/specs/libp2p-spec/protocol/network/figs/logo.png)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logo should be moved into this repo here

# Usage
- [**The IPFS Network Spec**](https://github.com/ipfs/specs/tree/master/libp2p), which grew into libp2p
- [**go-libp2p implementation**](https://github.com/ipfs/go-libp2p)
- [**js-libp2p implementation**](https://github.com/diasdavid/js-libp2p)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs to point to libp2p/specs and libp2p/js-libp2p respectively

@RichardLitt
Copy link
Member Author

@lgierth fixed.

## Contribute

libp2p implementation in Go is a work in progress. As such, there's a few things you can do right now to help out:
- Go through the modules below and [**check out existing issues**](https://github.com/libp2p/go-libp2p/issues). This would be especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrasture behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should either remove the go-libp2p reference or also mention js-libp2p

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should only mention go!

@RichardLitt
Copy link
Member Author

@lgierth This should be good to go, no?

@RichardLitt RichardLitt assigned ghost and unassigned whyrusleeping Jan 19, 2017
@RichardLitt RichardLitt assigned whyrusleeping and unassigned ghost Jan 19, 2017
@RichardLitt
Copy link
Member Author

@whyrusleeping Apparently you're the merge master for this one.

@daviddias
Copy link
Member

I believe this one can be closed. The README got a summer cleaning today :)

@Kubuxu Kubuxu closed this Aug 23, 2017
@daviddias daviddias removed the status/ready Ready to be worked label Aug 23, 2017
marten-seemann pushed a commit that referenced this pull request Apr 21, 2022
marten-seemann added a commit that referenced this pull request Apr 22, 2022
…-net

stop using the deprecated go-multiaddr-net package
marten-seemann added a commit that referenced this pull request Apr 26, 2022
stop using the deprecated go-multiaddr-net
marten-seemann pushed a commit that referenced this pull request Aug 9, 2022
marten-seemann pushed a commit that referenced this pull request Aug 15, 2022
Record which direction the resource was blocked
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking public contribution on this issue need/review Needs a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants