Evaluate what we have available on dotcms-utilities and standardize
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
No response
Task
We have very useful tools available but they haven't been properly communicated to our devs.
We need to evaluate them and come up with a standard and then communicate how to use them to our devs.
https://github.com/dotCMS/dotcms-utilities
Proposed Objective
Please Select
Proposed Priority
Priority 3 - Average
Acceptance Criteria
Conventions for our branch naming and commits easier to achieve/adopt by developers
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Parent: #31604
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
Review the dotcms-utilities repository first, then compare its available tools with the requested branch-naming and commit conventions. Done means a decided standard and developer-facing guidance explaining how to use it; the issue provides no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100