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
It's not a good look to spam the go-libipfs repo with highly experimental code and issues. It would be one thing if we had clear documentation on how we handle experimental functionality and a tight triage process and views sorting out the experimental / aspirational work from the nuts and bolts of bugs to existing functionality. We'll get there, but we're not there currently.
Done Criteria
RAPIDE experimental work (PRs and issues) are out of go-libipfs until either:
Why Important
It's not a good look to spam the go-libipfs repo with highly experimental code and issues. It would be one thing if we had clear documentation on how we handle experimental functionality and a tight triage process and views sorting out the experimental / aspirational work from the nuts and bolts of bugs to existing functionality. We'll get there, but we're not there currently.
Notes
This will get moved within the IPFS org (e.g., http://github.com/ipfs/go-libipfs-rapide ) since that makes it easier to move issues.
The text was updated successfully, but these errors were encountered: