stackabletech / stackabletech/demos
[Tracker] Findings of demos
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 13
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
Feel free to ignore this, this serves mostly as a list for me to track and improve demos
Not adopted in demos
- https://github.com/stackabletech/spark-k8s-operator/issues/162
- https://github.com/stackabletech/druid-operator/issues/359
- https://github.com/stackabletech/spark-k8s-operator/issues/141
Adopted in demos
- https://github.com/stackabletech/druid-operator/issues/306
- https://github.com/stackabletech/spark-k8s-operator/issues/161
- https://github.com/stackabletech/nifi-operator/issues/354
- https://github.com/stackabletech/druid-operator/issues/309
Not from demo, but something @sbernauer want's to track anyway
- https://github.com/stackabletech/trino-operator/issues/299
- https://github.com/stackabletech/secret-operator/issues/229
- https://github.com/stackabletech/druid-operator/issues/372
Not from Stackable
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 linked issues and the demos repository to determine which findings still need action. The issue does not name files, tests, or a concrete change; it would be done only when the demo findings and their adoption status are clearly updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, kubernetes, spark
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100