Separate repos for plugins, themes, and languages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
Given that our download page uses the Github API anyway and we already have a components.js to keep track of things, what do you think about having plugins etc in separate repos? That way their authors can update them without needing to send PRs to us and we don't need to keep track of authors, we can just use the repo owner.
It seems this is the way big projects with a plugin architecture are going, e.g. Atom. Thoughts?
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 by reading components.js and the download page’s existing GitHub API integration. Determine whether the proposed separate repositories can support plugins, themes, and languages without tracking authors; done would require an agreed architecture and implementation scope, which the issue does not currently define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100