typelevel / typelevel/typelevel.github.com
Document process for access control to Typelevel repositories
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 115
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 7
Description
Ref https://gitter.im/typelevel/general?at=57222f544cd0ac7a27ed46a2
Summary:
"For bintray, ie sbt-catalysts, currently on @milessabin @larsrh and myself have access there. Technically, this enough, but I feel at least one extra is needed to do releases.
Any thoughts..? ref https://bintray.com/typelevelThis is a job for a typelevel/general issue ... we need a list of people who currently have permissions (both Sonatype and Bintray) and the skeleton of a process for how someone gets on or off that list.
I have extended this to include Typelevel based github repositories too, as they are very much related.
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 with the linked Gitter discussion and the Bintray Typelevel page, then inspect the Typelevel GitHub repositories and the existing Sonatype and Bintray access arrangements. Document who currently has permissions and define a process for adding or removing people; done means the list and process are recorded for all three areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100