-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
123 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,123 @@ | ||
**Are you the copyright holder or authorized to act on the copyright owner's behalf?** | ||
|
||
Yes, I am authorized to act on the copyright owner's behalf. | ||
|
||
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** | ||
|
||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
|
||
As a department, we own not just the skeleton files but the solutions themselves. The skeleton files, solutions, specifications, graders, and introductory material have all been authored by the department and are our sole property. | ||
We have ownership of the skeleton code, solutions, and specifications that provides the basis of the work in all of these repositories. This constitutes our IP and is protected. | ||
Previous request: | ||
"I am the instructor for a UC Berkeley course that has sole ownership of the projects posted in these repositories. Students are made aware of the permissions for code reuse and publication and this goes against the agreement." | ||
|
||
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.** | ||
|
||
I am the creator and owner of one or more copyrighted works appearing on your web site, which can be found on cs61bl.com/su20, cs61bl.com/su19, cs61bl.com/su18, cs61bl.com/su17, cs61bl.com/su16. Further, this material can be found in the following repositories belonging to the institution hosted on GitHub: | ||
https://github.com/cs61bl/ai-skeleton-su20 | ||
https://github.com/cs61bl/skeleton-su20 | ||
https://github.com/cs61bl/library-su20 | ||
[private] | ||
[private] | ||
https://github.com/cs61bl/skeleton-su19 | ||
https://github.com/cs61bl/ai-skeleton-su19 | ||
[private] | ||
[private] | ||
https://github.com/cs61bl/skeleton-su18 | ||
https://github.com/cs61bl/library-su18 | ||
[private] | ||
[private] | ||
[private] | ||
[private] | ||
[private] | ||
[private] | ||
[private] | ||
[private] | ||
https://github.com/Berkeley-CS61B/ai-skeleton-sp19 | ||
https://github.com/Berkeley-CS61B/skeleton-sp19 | ||
https://github.com/Berkeley-CS61B/library-sp19 | ||
https://github.com/Berkeley-CS61B/library-sp18 | ||
https://github.com/Berkeley-CS61B/skeleton-sp18 | ||
And the final very large one: [private] | ||
|
||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** | ||
|
||
https://github.com/HenryYihengXu/Gitlet-cs61b-proj3 | ||
https://github.com/dhrushilbadani/Gitlet | ||
https://github.com/ferreiro/gitlet | ||
https://github.com/zhangjiedev/gitlet | ||
https://github.com/yerbolaussat/project_gitlet | ||
https://github.com/rkargon/gitlet | ||
https://github.com/cleomart/Gitlet | ||
https://github.com/lounotlew/Gitlet | ||
https://github.com/okdolly/CS61BLsummer2017 | ||
https://github.com/Raynxxx/Gitlet | ||
https://github.com/AdhityaRamadhanus/dit | ||
https://github.com/DrehanM/Gitlet | ||
https://github.com/dshen109/gitlet | ||
https://github.com/lifesaver0129/CS61BL-Data-Structure | ||
https://github.com/117010153/cs61b | ||
https://github.com/mikuchobits/cs61bl/ | ||
https://github.com/max2468tw/cs61bl | ||
https://github.com/cheolhojang/61BL-2017 | ||
https://github.com/qfang0770/cs61bl | ||
https://github.com/max2468tw/cs61bl/ | ||
https://github.com/MadcowD/CS61B | ||
https://github.com/Berkeley-Reject/berkeley-cs61b | ||
https://github.com/leihao1/CS61B2019 | ||
https://github.com/mooooon333/CS61B | ||
https://github.com/yngz/cs61b | ||
https://github.com/minori5214/cs61b | ||
https://github.com/wvqnllb/Learn-to-be-a-Developer | ||
https://github.com/chen1649chenli/NBody | ||
https://github.com/NervousOrange/Berkeley-CS61B | ||
https://github.com/jiahui-z/Berkeley-CS61B-19Spring | ||
https://github.com/hexinatgithub/cs61b | ||
https://github.com/danieljaeim/Signpost | ||
https://github.com/Fifthist/Starling | ||
https://github.com/miajj/Gravity-Simulation | ||
https://github.com/leihao1/cs61b | ||
https://github.com/xiyaow/CS61B | ||
https://github.com/scleeza/Algorithms | ||
https://github.com/pengw00/cs61-homework | ||
https://github.com/junhaowww/cs61b-sp18 | ||
|
||
**Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.** | ||
|
||
Yes | ||
|
||
**Is the work licensed under an open source license? If so, which open source license? Are the allegedly infringing files being used under the open source license, or are they in violation of the license?** | ||
|
||
No. | ||
|
||
**What would be the best solution for the alleged infringement? Are there specific changes the other person can make other than removal? Can the repository be made private?** | ||
|
||
They must make the repos private or remove them entirely. | ||
|
||
**Do you have the alleged infringer’s contact information? If so, please provide it.** | ||
|
||
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** | ||
|
||
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** | ||
|
||
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** | ||
|
||
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.** | ||
|
||
**So that we can get back to you, please provide either your telephone number or physical address.** | ||
|
||
Physical Address: | ||
[private] | ||
Telephone: | ||
[private] | ||
Email: | ||
[private] | ||
|
||
**Please type your full legal name below to sign this request.** | ||
|
||
[private] |