Provide SnakeYaml in Velocity Polymer?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
SnakeYaml is currently heavily used by the plugin ecosystem and bundled with nearly all platforms, including Velocity.
My opinion is that it would be wise to wait and see if the plugin landscape changes such that SnakeYaml is no longer as critical. I'm not going to advocate for its inclusion if the library dies out, but if its usage persists (or grows) nearing the time of Velocity Polymer, I would suggest it be kept in Velocity.
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
The issue names no files, tests, or entry points. Start by reviewing the current dependency and bundling configuration, then assess whether SnakeYaml remains sufficiently important to include in Velocity Polymer. Done requires a settled project decision and a documented inclusion or exclusion plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100