Rename this repo #17
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry.go#17
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
lbry.go
is a confusing name for what this does.Also, should this be public?
please let me know if we do this as Chainquery depends on its packages.
@tiger5226 what's in here that Chainquery relies on? Should it be split out?
It's possible I'm not understanding everything this repo does. In my head, this is the "YouTube sync repo"
We use a lot of stuff. So does internal-apis. It is the repo grin has designated as the Go repo for all things LBRY. So if anything is shared between go apps it goes here. Specifically from the gopkg.lock file
So obviously this repo should be named
lbry-libraries.go
.how about bookshelf.go? Stays with the LBRY theme and signifies lots of choices. No strong preference, just thought it was a playful name. @lyoshenka remarked "The swiss army knife" previously, although I think he removed that for the same reasons you want to rename the repo.
I strongly believe any lbry.go repo should be reserved for the daemon rewrite as that is what any one would think this repo was.
Additionally, lbryschema.go, and reflector.go use this as well I believe.
@kauffj and @lyoshenka is this something you want to tackle? It won't be easy, but sooner rather than later. Perhaps a better readme?
This is for @lyoshenka only. I noticed he already started splitting some parts of this repo out.
ill rename this eventually
closing for now