is it worth keeping the Marathon (Mesos) support?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names Marathon and Apache Mesos support but does not identify files, tests, or entry points. First locate the Marathon/Mesos integration and review its current usage and maintenance needs; done requires an agreed decision on whether support should remain or be removed.
Written by the indexing model from the issue text.
Description
Apache Mesos has been retired with little sign of a continuing community
- Dominant language
- Scala
- Stars
- 34
- Forks
- 20
- Avg merge
- 19h 10m
- Merged PRs (30d)
- 31
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 apache/pekko-management
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/pekko-management#1031 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
apache/pekko-management#702 · 6 comments · 14 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
apache/pekko-management#669 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
apache/pekko-management#650 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
apache/pekko-management#459 ·
Maintainers usually reply within 1 day
All issues in apache/pekko-management
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
propensive/soundness#2438 ·
Maintainers usually reply within 1 day
-
No test covers transaction re-request after a delivery timeoutPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ergoplatform/ergo#2916 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Area: PDF support
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
orbeon/orbeon-forms#8055 ·
Maintainers usually reply within 2 days