You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge remote-tracking branch 'origin/marco/bring-go-nat-home' into debug-nat-port-mapping
* origin/marco/bring-go-nat-home: (75 commits)
go mod tidy
reference internal package for mockgen
mod tidy test-plans
Make changes to internal nat library
ci: move to actions/upload-artifact@v4 (#3152)
tcpreuse: fix rcmgr accounting when tcp metrics are enabled (#3142)
fix(net/nat): data race problem of `extAddr` (#3140)
test: fix failing test (#3141)
quicreuse: make it possible to use an application-constructed quic.Transport (#3122)
nat: ignore mapping if external port is 0 (#3094)
tcpreuse: error on using tcpreuse with pnet (#3129)
chore: Update contribution guidelines (#3134)
tcp: fix metrics test build directive (#3052)
webrtc: upgrade pion/webrtc to v4 (#3098)
ci: get back on the main release track of release checker (#3117)
webtransport: fix docstring comment for getCurrentBucketStartTime
chore: release v0.38.1 (#3114)
fix(httpauth): Correctly handle concurrent requests on server (#3111)
ci: Install specific protoc version when generating protobufs (#3112)
fix(autorelay): Move relayFinder peer disconnect cleanup to separate goroutine (#3105)
...
Copy file name to clipboardExpand all lines: README.md
+14-1
Original file line number
Diff line number
Diff line change
@@ -67,12 +67,25 @@ Guidelines:
67
67
- ask questions or talk about things in our [discussion forums](https://discuss.libp2p.io), or open an [issue](https://github.com/libp2p/go-libp2p/issues) for bug reports, or #libp2p-implementers on [Filecoin slack](https://filecoin.io/slack).
68
68
- ensure you are able to contribute (no legal issues please -- we use the DCO)
69
69
- get in touch with @libp2p/go-libp2p-maintainers about how best to contribute
70
+
- No drive-by contributions seeking to collect airdrops.
71
+
- Many projects aim to reward contributors to common goods. Great. However,
72
+
this creates an unfortunate incentive for low-effort PRs, submitted solely to
73
+
claim rewards. These PRs consume maintainers’ time and energy to triage, with
74
+
little to no impact on end users. If we suspect this is the intent of a PR,
75
+
we may close it without comment. If you believe this was done in error,
76
+
contact us via email. Reference this README section and explain why your PR
77
+
is not a “drive-by contribution.”
70
78
- have fun!
71
79
72
80
There's a few things you can do right now to help out:
73
-
- Go through the modules below and **check out existing issues**. This would be especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrastructure behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
74
81
-**Perform code reviews**.
75
82
-**Add tests**. There can never be enough tests.
83
+
- Go through the modules below and **check out existing issues**. This would
84
+
be especially useful for modules in active development. Some knowledge of
85
+
IPFS/libp2p may be required, as well as the infrastructure behind it - for
86
+
instance, you may need to read up on p2p and more complex operations like
0 commit comments