Adding Licences the official documentation site
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.2k
- Forks
- 1.4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
On going through the documentation, I realised that there wasn't any section for the licenses
Describe the solution you'd like
By including clear and accessible information about the xarray's license, users can make informed decisions about how they can use . This can help to ensure that the project remains open and accessible to the wider community esspecially contributors and users.
@TomNicholas I will like to work on adding the licensses to the documentation
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
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 inspecting the official xarray documentation site and its documentation source structure to find where project-wide information belongs. Add a clear, accessible section describing xarray's license, then verify that it appears correctly in the built documentation.
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
- 38/100