Tidy up the Community Builds Table
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 311
- Forks
- 139
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 1
Description
The Community Builds stable has been migrated, but still could use cleanup. See my comment here for the specifics of each entry:
- RedHat builds: fix broken links (@sub-mod)
- AMD builds: fix stale links and split the 1.x / 2.x row(s) into two rows each (@deven-amd, last comment)
- Openlab builds: verify owner and recency, and split 1.x / 2.x rows. Stable last ran for TF 2.1. (@bzhaoopenstack)
- Intel builds: verify owner and build status and split 1.x / 2.x rows. (@gaurides @claynerobison)
@sub-mod and @deven-amd were both looking at their issues, but I haven't heard back from Openlab or Intel yet, so I'll reach out if I need to.
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 pull request comment for the entry-specific details, then review the Community Builds stable table. Verify the RedHat, AMD, Openlab, and Intel entries as listed, fix links or ownership and recency issues, and split 1.x and 2.x rows where requested. Done means every checklist item is resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100