generated from ipfs/ipfs-repository-template
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Establish a mechanism for tracking if copied-in-code has been updated at the original source #270
Labels
topic/build-and-release-fitness
Items related to our CI process, dependency management, etc.
Comments
BigLep
added
the
topic/build-and-release-fitness
Items related to our CI process, dependency management, etc.
label
Apr 6, 2023
This was referenced Apr 6, 2023
guseggert
pushed a commit
that referenced
this issue
Apr 12, 2023
* Added FAQ and README updates * Add note about #270
This is no longer relevant since for #202 we ended up archiving the repos. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Done Criteria
A mechanism has been setup and documented for us to know if any of the repos that were copied into this Boxo have received "important improvements" in their original location.
Why Important
Some of the repos we copied as part of #202 (e.g., ipfs/go-car) have active maintainers (see #218 ). Fixes will likely get made there that we'll miss. Similarly, repos that are not maintained may get picked up by others and we'd like to know if improvements get made so we can evaluate whether to incorporate them.
User/Customer
Kubo maintainers to make sure they aren't missing out on other changes that should be pulled into Kubo.
Notes
The text was updated successfully, but these errors were encountered: