Umask for documentarians on docs.nyc1.psf.io
Nobody has claimed this yet.
- Dominant language
- Hurl
- Stars
- 124
- Forks
- 67
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 5
Description
Currently we're all having a umask of 007, so if we create a directory the docsbuild-scripts won't be able to touch it.
@ewdurbin would it be a good idea to set it to 002 (so if we create a directory it would go as 775) and setting S_ISGID (2000) bit on /srv/docs.python.org (and all directory of the herarchy) so anything created under it is still owned by the docs group?
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 inspecting the docs.nyc1.psf.io configuration and the /srv/docs.python.org directory hierarchy mentioned in the issue. Verify the current umask and group ownership behavior, then confirm that newly created directories use umask 002 and inherit the docs group through the setgid bit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100