jakartaee / jakartaee/collateral
[JakartaONE Committee] Push CALL2ACTION to make public the value of this REPO
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
using JakartaONE media channels & forums, & JUGs & individuals media channels-- how this event is run needs to be normalized and made explicit that the git issues and PRs are used & welcomed anyone interested to not only through tasks but also own those tasks.
Showing care means tracing the time invested on any activity that leads open source to be not only fun & valuable but also that flattens known experts with new comers without the "you bother me" mentality. There is much to be protected when creating events, for one-- those who Lead today MUST become the trainers on next iterations to enable the trainees to own & adjust what have been previously done. Only like that, normalizing the process is sustainable beyond a just a few. In Jakarta EE, we must aim to scale & bring others beside us, today and always!
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 defining the JakartaONE media, forum, JUG, and individual outreach process requested, then identify where that process belongs in this repository. Done would require an agreed, explicit, and sustainable contribution process documented here.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100