How to publish this plugin, "paper work"
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- wordpress
- Domain
- release
Research direction
No files, tests, or code entry points are identified. Read the issue and its existing comments first, then clarify the publication decision and ownership with the maintainers; the work is done when a publication route and responsibilities are agreed.
Written by the indexing model from the issue text.
Description
@oguhpereira @AurelienLourot
I've been thinking about how we could possible publish this plugin. Since this plugin is a branch of Dracula project, I'm leaning towards creating a Dracula user on WP system, and upload it under that user. So, we could call it DraculaWP, or something related, then we could send it to be reviewed by that user. Of course, that would require us to create an email, something like draculaWP@gmail.com. I volunteer to do all that. But want to know from you what would be the best course of action.
See you
- Dominant language
- CSS
- Stars
- 16
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·