NetAppDocs / NetAppDocs/storagegrid
License vs. Terms of Use
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 3
Description
Page URL
https://docs.netapp.com/us-en/storagegrid/s3/consistency.html
Page title
How StorageGRID S3 REST API balances availability and consistency
Summary
- At the bottom, there's a link to Terms of Use
- That links to netapp.com
- There, it says:
Unless otherwise specified in these Terms, all information and screens appearing on this Site, including documents, services, site design, text, graphics, logos, images and icons, as well as the arrangement thereof, are the sole property of NetApp. All rights not expressly granted herein are reserved.
Since these NetAppDocs repositories have no license in them, what rights are expressly or implicitly granted?
This repo claims the documentation is open-source.
Questions/issues:
- which open-source license are NetApp docs (including this repo) made available under, so that users may know what rights are "expressly granted" and avoid violating the NetApp Terms of Use?
- shouldn't there be a license file in each repo? For "open-source" documentation, it is common to use one of the CC licenses.
Public issues must not contain sensitive information
- This issue contains no sensitive information.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository and the linked NetApp Terms of Use and documentation page. Determine which licensing information the repository provides and what change is requested for users to understand their rights. Done means the applicable license position is resolved and documented, including whether each repository needs a license file.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100