marmelab / marmelab/EventDrops
Unofficial 1.4 release
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 233
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I noticed that the project seemed to have been inactive for some time, even though there were fixes and pull requests that hadn't been incorporated into a release. Therefore, I took it upon myself to fork the project and release a package:
- [NPM package: @neuroglia/event-drops](https://www.npmjs.com/package/@neuroglia/event-drops)
- [GitHub Fork: neuroglia-io/EventDrops](https://github.com/neuroglia-io/EventDrops)
It ships:
- https://github.com/marmelab/EventDrops/pull/269 by @Busteren
- https://github.com/marmelab/EventDrops/pull/273 by @Busteren
- https://github.com/marmelab/EventDrops/pull/284 by @bastianonm
I really appreciate this project and hope that it continues to thrive. If the original maintainers of the repository happen to resume activity, I would be happy to deprecate my package/archive the forked repository.
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
The issue points to the @neuroglia/event-drops NPM package and the neuroglia-io/EventDrops fork, which already contain the listed pull requests. There is no repository file, test, or remaining change identified here; check the linked fork and package first, and confirm with maintainers whether any work remains in this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- d3, javascript
- Domain
- data-visualization, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100