-
Notifications
You must be signed in to change notification settings - Fork 1
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
Name change: Amplica Labs -> Project Liberty Labs #347
Conversation
9084a93
to
eeea8c0
Compare
@@ -186,7 +186,7 @@ | |||
same "printed page" as the copyright notice for easier | |||
identification within third-party archives. | |||
|
|||
Copyright Amplica Labs | |||
Copyright Project Liberty LLC |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In SAT, you put Copyright 2024 Project Liberty LLC
. Do we want to keep it consistent with or without the date?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The date is optional per copyright patterns. We likely shouldn't have it anywhere, but I was just replacing when going through these.
So this is the "more" correct version, but both are fine.
services/account/LICENSE
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was this deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I imagine we only need a LICENSE file at the root of the repo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup. Only need the one License file now that it is unified
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some package locks have only 6 lines changing and some have a ton. Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question! I allowed dependency trees to be updated. I removed the lock file and reran npm i
to make sure it cleared out any old stuff.
"devDependencies": { | ||
"tsx": "^4.15.7" | ||
} | ||
"name": "setup", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
confirming format
has been run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is actually from npm formatting it I believe. That said, I ran make format
and it had formatting changes elsewhere, so I'll push that up as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few questions, but LGTM
Updating:
No Amplica references should remain.
Closes: #345