maliput / maliput/maliput_documentation
Document S3 bucket
Open
Nobody has claimed this yet.
- Dominant language
- CMake
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We should document:
- Where it is located.
- Who maintains it.
- Credentials (not to make them public, but how they are stored)
- Commands to access it.
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 locating the repository's documentation structure and any references to the S3 bucket. Document its location, maintainer, credential-storage procedure, and access commands without exposing credentials. Done means all four topics are recorded clearly and safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100