Contribution Pipeline and Development Transparency — Following Up on Announcement #500 #909
Replies: 4 comments 15 replies
-
|
Hi @virtualian Ian, thanks for this nudge. @danielmiessler and I will meet soon and discuss the best way forward. Thank you for offering to help, I may take you up on it. Regarding your questions:
Your concrete ask is reasonable and I'll look at how we want to set that up for PAI. Feel free to message me privately or connect via LinkedIn if you'd like to continue the discussion. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we haven't met yet to get this going, but we will soon. |
Beta Was this translation helpful? Give feedback.
-
|
Dear all naturally I perceive the same issues and I might be able to offer an interim workaround if you're interested. With my assistant I created a tracking system for all the changes that I do, including changes to system files. In addition, I created a skill that continuously checks the upstream repo, is able to do updates to new Pi versions, check whether local fixes have now been included upstream or whether they need to reapply and make sure that after that update it is still a fully working setup including all my modifications. Has worked pretty well now updating 4.0.0 or 4.0.3. Happy to share if you want. |
Beta Was this translation helpful? Give feedback.
-
|
I'm definitely interested in this. I'm developing a CalDAV skill (calendaring, tasks, contacts), and I want to contribute it back up, but right now the skills/etc are actually in release sub-dirs. I was expecting a singular directory that is the current Is this the intention, that that's how this is going to be for contributions? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
@danielmiessler (and @ksylvan),
I'm Ian Marr (@virtualian / linkedin.com/in/ianmarr).I've been using PAI since early in the v2.x cycle, have raised several issues, including #393 (voice server path mismatch) and #614, and have been following the project closely across Issues, Discussions, and releases.
This post is a direct follow-up to #500, where you outlined two priorities: a better install wizard and an improved contribution pipeline, and you formally welcomed Kayvan to professionalise the repo the way he did for Fabric. I'm not raising a complaint and simply want to follow up to solicit an update from you.
The current situation has real implications for PAI's community, and the path forward has already been described by both of you. It's been roughly five weeks, and I haven't seen any visible progress on the contribution pipeline. I perceive frustration, but maybe that's just me!
The problem, in your own words from #500:
That's still the structural reality. PRs are accumulating (44 open as of today), the merge path runs through a private staging repo that contributors can't see, and there's no reliable signal about whether a contribution is actively in review or sitting in a queue indefinitely.
What you promised in #500:
The ask — narrow and specific:
A designated
contribbranch that accepts PRs directly, reviewed and merged by you or Kayvan as Collaborator, with you retaining sole authority over what is promoted tomainfor official releases. This is not a governance request. Architecture, design principles, and release cadence — all stay with you. This is purely about making the contribution pipeline visible and functional rather than opaque and manual.Fabric already works this way. Kayvan built that. The model is proven.
Concrete questions:
The community building on PAI — and the quality of the project itself — would benefit from even a partial answer to those three questions.
I'm happy to help move this forward practically. I have a background in IT infrastructure, I'm passionate about AI and DAs, and have been running PAI hands-on since the v2.x cycle. If useful, and as inexperienced as I am with open-source projects, I have time to assist with whatever reduces the burden on you and Kayvan rather than adding to it. My goal: a more resilient project that can absorb community energy without creating overhead for the core team.
— Ian
Beta Was this translation helpful? Give feedback.
All reactions