fwolfst / fwolfst/your-repository
README or packaging manifest does not specify the license
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As a developer and user of the project, I would like to see the license and copyright information in the projects README.
It is common to put the license in full text (and nothing else) into a file `LICENSE` in the root folder of the project (other filenames are common, too; but LICENSE is a relatively safe bet).
Also, github will pick this up and display that information.
Also, be sure to be specific and e.g. mention [`or any later version`](https://spdx.org/licenses/GPL-3.0-or-later.html) if you are using GPL as a license, trust the FSF and want to [easily adopt to newer GPL versions](https://www.gnu.org/licenses/gpl-faq.en.html#VersionThreeOrLater) if they come out one day.
## Package information (e.g. ruby gems)
If the project defines a package, e.g. a ruby gem, the license and copyright information/name should be included in its manifest ( e.g. `.gemspec`).
If you are unsure which license would suit your project, feel free to get in contact.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the project README and root directory for an existing LICENSE file or packaging manifest. Confirm the intended license and copyright information with a maintainer, then document it in the README and add the full license text and any applicable package metadata. Done means the license is visible in the repository and represented in the relevant manifest if one exists.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100