Repository navigation
Offer to help with issue triage, PR testing, and repository housekeeping #4414
Replies: 2 comments
|
Hello, this is off topic and not belongs to this category Main priority today is bringing fixes / highly requested changes to the firmware, and keeping apps catalog maintained Tests that are being added to documentation is mainly for repo maintainers to keep the process After that comes the 170+ old issues in fw repo that starts from 2022 and up to 2026 Along with sorting those issues I will put active ones on the project board, + PRs that are in progress rn Thank you for offering help btw, Running tests -> please merge latest dev on top of the PR locally before doing test, do not take draft PRs ReadMe additions -> that's good, just make a PR with changes, we will check it out, if that does fit for the repo, we gonna accept that As for these two things: Project board -> Only for maintainers, open for public to see what's in todo's (will be filled) Issue triage -> I'm currently doing same thing you wanted to do, categorising them, checking what's gonna fit to discussions etc. I'm gonna close this discussion as offtopic |
|
Opened #4415 with the README additions you suggested (build status, latest release, and an "Open for Contribution" count since there's no help-wanted label). Also happy to pick up the PR-testing offer next — let me know if there's a batch you'd like reviewing first, or I'll just pick a few older non-draft ones. |
Uh oh!
There was an error while loading. Please reload this page.
Thanks for the update on the future of Flipper Zero development, and for everything that's gone into getting the firmware to where it is. Delivering on every Kickstarter promise, working around a 700 KB flash limit with dynamic app loading, and building an SDK developers actually enjoy using is a genuine achievement, especially given everything the team has had to deal with along the way.
This isn't a feature request, so it doesn't fit neatly into this category. If there's a better place for it, please let me know and I'll move it.
I'd like to offer some help with the less visible side of things: the housekeeping that makes it easier for a smaller team to work with a large community. A few concrete offers, none of which require a decision from you before I start looking into them further:
Issue triage. There are currently around 173 open issues. Some are clear, well-scoped bugs. A few look like duplicates (three near-identical RFID protocol reports were opened the same day, for example). A handful look like they'd fit better as Discussions than issues, given the new process. I'd be glad to work through these and suggest groupings, without closing or relabelling anything myself.
PR testing. There are 66 open pull requests at the moment. I noticed the published integration test suite in
documentation/testingand would like to help run it against some of these, particularly a batch of bugfix PRs that have been open for a while and look otherwise complete. Happy to report back findings rather than expecting anything to be merged on my say-so.Repository visibility. A few small ReadMe additions, build status, latest release, and a help-wanted count if that would be useful, might make it easier for new contributors to find something to work on without digging through the full issue list. Very low effort if it's wanted.
Project board. I noticed the "Project for tracking public development of Flipper Zero firmware" board is set up but currently empty. If it would help, I'd be happy to propose some initial cards from the issue triage above, though I'd want to check first whether that's something the community can do or whether it needs to go through a maintainer.
No urgency on any of this from my side. I know the team's attention is on Flipper One and the new devices right now, and I don't want to add to the load. If any of the above is useful, I'll pick it up. If it isn't, or the timing's wrong, that's completely fine too.
Happy to add more detail on any of the above if it's helpful. Wanted to keep this first post short and see how it lands.
Chris
All reactions