Creating a Roadmap
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the repository's existing project goals and any current planning material; the issue specifically suggests a single Org Mode file. Define version milestones, tasks, and priorities, then post the roadmap where contributors can find it. Done means the project has an agreed, accessible plan that reduces overlapping work.
Written by the indexing model from the issue text.
Description
If you have a roadmap @zonuexe could you please post it or consider writing one? It can be very simple, like a single Org Mode file that says stuff like:
- Version 1.0.0
** Support doing FOO
** Allow customizing BAR
* Version 2.0.0
** Let user fallback on using BAZ in FOO is not available
You could even assign priorities using C-c C-, in Org Mode. This way contributors will not accidentaly waste effort working on the same tasks simulatenously.
- Dominant language
- Emacs Lisp
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 emacs-php/php-runtime.el
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
emacs-php/php-runtime.el#4 · 4 comments ·
-
Unit TestingMay be free again @ejmr claimed this 2930 days ago, and no pull request is open. Open
emacs-php/php-runtime.el#2 · 1 reaction · 1 assignee ·
All issues in emacs-php/php-runtime.el
Similar issues
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
bug developer portal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
discord/discord-api-docs#8645 ·
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100