stackabletech / stackabletech/documentation
Documentation: Which combination of components of Stackable Data Platform run successfully together?
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 13
- Forks
- 14
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 10
Description
As a user of Stackable Data Platform I want to know which combination of components / component versions run together and which do not because I want to use a consistent set of components to run my data platform.
Acceptance criteria:
- matrix of components and versions running successfully together in combination
- matrix of components and versions not running together in combination
- the matrix is part of the Stackable documentation
- the matrix can be referenced by URL from support subscription contracts, probably versioning / archiving required maybe related to a release?
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 reviewing the documentation repository's organization and any existing release, versioning, or archiving conventions. Define how supported and unsupported component/version combinations will be represented and referenced by stable URLs. Done means both requested matrices are published in the Stackable documentation and can be retained or archived for contract references.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100