Question about maintaining a fork focused on stability and device-neutral installation

[pentecosthub]

Hi,

I’ve been working through a fresh install of PiRowFlo on a current Debian-based system and documenting the process carefully. During this work, I ran into several reproducible install and startup issues that make it difficult for new users to get the project running on a clean system.

Rather than applying local fixes ad hoc, I’m trying to approach this in a maintainable way. Based on what I’ve observed, I’m considering maintaining a fork of the project with the following goals:

• Fix reproducible install and startup errors found on clean installs
• Document required system dependencies that are currently implicit
• Improve startup behavior so optional hardware adapters do not block execution
• Reduce Raspberry Pi–specific assumptions so the project can run on other small Linux devices, such as thin clients

Before proceeding, I wanted to ask whether you would be comfortable with me maintaining a fork focused on stability, documentation, and device neutrality. I would clearly credit and link back to the original project.

If you would prefer issues or pull requests against this repository instead, I’m open to that as well. I mainly wanted to respect the original intent of the project before moving forward.

Thanks for your work on PiRowFlo.

[klausj62]

Hi all,
I would highly appreciate for any progress here. Thanks to anybody, who supported the initial work.
I think it es a very good idea, as a starting point, to update the documentation, as you suggested.
I can contribute with testing.

[pentecosthub]

I think the project was abandoned when Google changed the app permissions. I have a working fork that simply broadcasts S4 data over bluetooth, none of all the other stuff. The waterrower app can then pair your hr strap if you want.  -------- Original message --------From: klausj62 ***@***.***> Date: 3/1/26 3:50 AM (GMT-05:00) To: inonoob/pirowflo ***@***.***> Cc: pentecosthub ***@***.***>, Author ***@***.***> Subject: Re: [inonoob/pirowflo] Question about maintaining a fork focused on stability and device-neutral installation (Issue #86) klausj62 left a comment (inonoob/pirowflo#86) Hi all, I would highly appreciate for any progress here. Thanks to anybody, who supported the initial work. I think it es a very good idea, as a starting point, to update the documentation, as you suggested. I can contribute with testing. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>