SpikeInterface / SpikeInterface/spikeinterface
Move `sortingcomponents` out of `spikeinterface`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
sortingcomponents and spikeinterface have different targets (developers VS users) and development pace (fast VS slow).
I suggest factoring out sortingcomponents into its own package.
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 mapping where sortingcomponents and spikeinterface are defined, packaged, and imported, then review their dependency and release boundaries. Identify the packaging and compatibility decisions needed to make sortingcomponents a standalone package. Done means the separation is implemented without breaking the existing project’s stated user-facing functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100