[PR] Feedback from key users
@MeganCadena is already working on this.
Since Oct 27, 2025.
Assessment
This issue has not been assessed yet.
Description
This issue has no description.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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
- 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.
More from PubInv/librecorder
-
[General] Review of paper 3May be free again @aroyphillips claimed this 298 days ago, and no pull request is open. Open
PubInv/librecorder#42 · 1 assignee ·
-
Make "dark_light" classifer product report in proper formatMay be free again @aroyphillips claimed this 319 days ago, and no pull request is open. Open
PubInv/librecorder#41 · 1 assignee ·
-
Report should be standardized and versioned and classifiers should produce it...May be free again @aroyphillips claimed this 319 days ago, and no pull request is open. Open
PubInv/librecorder#40 · 1 comment · 1 assignee ·
-
Make GUI use "sample Type" and "Classifier" registry....May be free again @Nipul12 claimed this 319 days ago, and no pull request is open. Open
PubInv/librecorder#39 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PubInv/librecorder#38 ·
All issues in PubInv/librecorder
Similar issues
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 72/100
EclipseFdn/open-vsx.org#14043 ·
Maintainers usually reply within 1 day
-
netbox status: needs triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
netbox-community/netbox#23376 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day
-
Triage 🩺
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
[BUG] Container scenario crashes without expected_recovery_time, kube DNS example uses retry_waitOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
krkn-chaos/krkn#1627 · 1 comment ·
Maintainers usually reply within 1 day