Upstream code from third party maintained browser plugins
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.2k
- Forks
- 441
- Avg merge
- 16h 24m
- Merged PRs (30d)
- 3
Description
Hi! I noticed that in the README.md it is stated that the Firefox plugin is deprecated. However, there is a plugin in the Mozilla addon store: https://addons.mozilla.org/en-US/firefox/addon/retire-js/
Is the codebase for this plugin unrelated to (specifically: Firefox plugin code) this repository? It was updated 18 days ago, that is surely not unmaintained. If the codebase is unrelated, I could contact the developer by e-mail to try having the code upstream here. I could not identify their GitHub account if they have one. It would be nice if we could automate some development and push releases automatically from here.
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
Review README.md's Firefox plugin deprecation note and compare it with the code behind the linked Mozilla add-on. Determine whether the plugin can be upstreamed into this repository and define what repository changes and release automation would be needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100