RocketChat / RocketChat/Docker.Official.Image
Improve release process
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 337
- Forks
- 228
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 5
Description
@tianon @pierreozoux
I'm not sure who to ping here. Pretty much from the start this has been a community maintained repo. Because of that its been a bit hands off and just let things run.
We'd like to get a bit more hands on and assure this image gets the same sort of quality as the one in our own repo.
So we'd really like to understand how exactly the pieces here fit together and how we can improve. I don't know if here is the best way or if via email.
If email is better please shoot me an email aaron.ogle [@] our company domain :)
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 files, tests, or concrete acceptance criteria are named. Review how this community-maintained Docker image is currently released, then clarify the desired quality comparison with the company's own image, ownership, and what an improved release process would consider done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100