The New Core Dev WorkFlow
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 333
- Forks
- 127
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
Description:
Currently, we are revamping the Workflow for Core team.
There is much confusion and most contributors have been historically assigning action keywords wrongly (or not assigning at all, probably because of not knowing about them). Keywords are very important because they ultimately help push tickets to an end. Not setting keywords leave most almost finished patches lost in oblivion.
Audience:
The main audience is any current or future contributor that wants to learn how to do things well and confidently when they are introduced into the Core contributor's world, from a workflow perspective
Learning Objectives:
- Learn the purpose of the most important and popular keywords
- Learn how to correctly assign keywords according to the work done
- Learn how to search based on the different keywords and understand how anyone could be useful to Core, both technical and non-technical contributors
Content Type:
I'm planning to do two formats:
- An onboarding course, explaining the main keywords, the most used ones, text based.
- A more in-detail course, probably in video
- Maybe in the future depending on the interest, a second "Advanced" including all the less used keywords, but for now, only these 2.
I will be creating this content
Related Resources
- Current version Trac Workflow Keywords (still pending to be updated with the new version). I'm willing to create this course in advance as a companion for the revamp so people can start working with the right foot after publishing.
- Gutenberg workflow overview by annezazu, this was the first resource that got my attention. Gutenberg has been doing a great job and I found that Core had to catch up some months ago, this is why we started the revamping process.
Contributor guide
No contributing guide indexed for this repository
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
Start with the issue description and review the linked Trac Workflow Keywords page and Gutenberg workflow overview. The proposed work covers a text onboarding course and a more detailed video course; it is done when contributors can understand, assign, and search the relevant workflow keywords.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- content, developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100