Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move `sortingcomponents` out of `spikeinterface`

Open
#4,669 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

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.

Description

discussion

sortingcomponents and spikeinterface have different targets (developers VS users) and development pace (fast VS slow).

I suggest factoring out sortingcomponents into its own package.

Dominant language
Python
Stars
855
Forks
280
Avg merge
3d 32m
Merged PRs (30d)
39

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SpikeInterface/spikeinterface

All issues in SpikeInterface/spikeinterface

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.