Reorganise JCache info
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by comparing the distributed-caching-jcache.html, distributed-session-caching.html, and sessionCache-1.0.html topics to determine where the configuration content belongs. Then review configuring-infinispan-support.html, especially its introduction, for the missing Infinispan purpose and platform context. Done means the topics have the requested structure and the introductory context is clear.
Written by the indexing model from the issue text.
Description
https://openliberty.io/docs/latest/distributed-caching-jcache.html
This container topic is largely about configuration, which should instead be in the feature config reference topic: https://openliberty.io/docs/latest/reference/feature/sessionCache-1.0.html
It is not helpful for this to be the container topic. The Distributed caching topic should be the container topic: https://openliberty.io/docs/latest/distributed-session-caching.html It introduces the concept and gives context to anything else.
The topic about Infinispan starts with a generic shortdesc but it should mention Infinispan and why you might be using that as that's the point of the topic. Nothing in the whole intro section explains why you might choose Infinispan yet the topic assumes you're on OpenShift (which is not necessarily going to be the case). Is Infinispan the only option on OpenShift? Can it be used only on OpenShift? I'm not sure any of this context is given in the topic.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 58
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from OpenLiberty/docs
-
source mismatchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/docs#8579 ·
Maintainers usually reply within 1 day
-
Jandex extended pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenLiberty/docs#8451 · 1 comment ·
Maintainers usually reply within 1 day
-
CVE update for 26.0.0.10Possibly taken @ramkumar-k-9286 claimed this 18 days ago. Open26.0.0.10
OpenLiberty/docs#8563 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
26.0.0.11
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenLiberty/docs#8548 ·
Maintainers usually reply within 1 day
-
26.0.0.12
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenLiberty/docs#8529 · 1 comment ·
Maintainers usually reply within 1 day
All issues in OpenLiberty/docs
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 3 days
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
vendor-pitch
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
eugenioenko/ttt#1000 ·
Maintainers usually reply within 1 day