Update 2022-06-24-headspace.md #11425
Open
Conversation
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
Added 2022/06/2022-06-06-corus.md
Added 2022/06/2022-06-08-compare-the-market.md
Added 2022/05/2022-05-31-ceva.md
Added 2022/06/2022-06-08-flexiblog-react-gatsby-blog-template.md
Added 2022/06/2022-06-09-sword-factory.md
Added 2022/06/2022-06-08-wiley-2.md
Added 2022/06/2022-06-09-asiainfo.md
Added 2022/06/2022-06-09-ifood.md
Added 2022/06/2022-06-08-wuba.md
Added 2022/06/2022-06-08-university-of-washington.md
Added 2022/06/2022-06-08-testdome.md
Added 2022/06/2022-06-09-website-code.md
Added 2022/06/2022-06-09-printfly.md
Added 2022/06/2022-06-08-unikorn.md
Added 2022/05/2022-05-31-ceva-2.md
Added 2022/06/2022-06-22-explore.md
Added 2022/06/2022-06-22-metrobank.md
Added 2022/06/2022-06-22-tech-mahindra.md
Added 2022/06/2022-06-22-codesign.md
Added 2022/06/2022-06-22-wiley.md
Added 2022/06/2022-06-22-ceva.md
Added 2022/06/2022-06-22-ceva-2.md
Added 2022/06/2022-06-22-wubu58.md
Added 2022/06/2022-06-23-gcash.md
Added 2022/06/2022-06-24-headspace.md
This comment was marked as off-topic.
This comment was marked as off-topic.
Vovanchik25071982
approved these changes
Sep 24, 2022
2022/06/2022-06-24-headspace.md
Outdated
| @@ -74,4 +74,4 @@ Headspace | |||
|
|
|||
| **Please type your full legal name below to sign this request.** | |||
Vovanchik25071982
approved these changes
Dec 3, 2022
2022/06/2022-06-24-headspace.md
Outdated
| @@ -74,4 +74,4 @@ Headspace | |||
|
|
|||
| **Please type your full legal name below to sign this request.** | |||
2022/06/2022-06-24-headspace.md
Outdated
| @@ -74,4 +74,4 @@ Headspace | |||
|
|
|||
| **Please type your full legal name below to sign this request.** | |||
2022/06/2022-06-24-headspace.md
Outdated
| @@ -74,4 +74,4 @@ Headspace | |||
|
|
|||
| **Please type your full legal name below to sign this request.** | |||
|
|
|||
| [private] | |||
dmca-sync-bot
force-pushed
the
master
branch
2 times, most recently
from
66324cf
to
14285da
Compare
|
sadmk |
|
dsaasadasdasd;'fasl;d |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you are looking to file or dispute a takedown notice by posting to this repository, please STOP 🛑 because we do not accept Pull Requests or other contributions to this repository.
Read on to learn about the available paths forward.
Please note that re-posting the exact same content that was the subject of a takedown notice without following the proper process (outlined below) is a violation of GitHub’s DMCA Policy and Terms of Service. If you commit or post content to this repository that violates our Terms of Service, we will delete that content and may suspend access to your account as well.
Submitting a DMCA Notice
If you are a copyright owner wishing to submit a takedown notice, read our DMCA Policy and Guide to Submitting a DMCA Takedown Notice. You can submit the actual notice using our special Copyright Claims Contact Form.
Responding to a DMCA Notice
If you are the owner of a repository that has been taken down, you have two main options:
Do you want to make changes to the repository that would remove the allegedly infringing content? If that is possible in your case, contact us to let us know that you would like to make the changes.
Do you want to formally dispute the action by submitting a counter notice? Maybe the person sending the takedown notice does not hold the copyright or did not realize that you have a license or made some other mistake in their takedown notice. If you believe your content on GitHub was mistakenly disabled by a DMCA takedown request, you have the right to contest the takedown by submitting a counter notice. If you do, we will wait 10-14 days and then re-enable your content unless the copyright owner initiates a legal action before then.
If you do not want to make changes or dispute the notice, but still have general concerns about the copyright laws and how they apply in your case, know that GitHub and developers have the opportunity and a voice to advocate for changes in law and public policy to better support software development. We are constantly looking to advocate for developers, so feel free to reach out and let us know your concerns. We also encourage you to learn more about copyright and speak up by reaching out to the Copyright Office or your local lawmakers to voice your concerns.