Permission for a forked wiki
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Hey devs! I kind of wanted to help maintain a project where the repo was moved off of the Wiki page and developed in a separate matter where PRs can be used, etc. Right now the wiki is pretty out of date, and I would like to help with it. Problem is, I don't think the wiki has a license and so whether I am safe here is still ???.
If I could get authorization or assigned a license or something, that'd help.
This is still just something I wanna maybe do as a hobby not really a guaranteed thing.
CC: @mar-v-in @ale5000-git
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
No file, test, or code entry point is named; start by reviewing the current wiki and confirming its licensing status. Done would require a maintainer decision on authorization or an assigned license before the wiki can be forked and maintained through PRs.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100