Pinned discussion, issue, or readme update redirecting to fork?

[cspotcode]

EDIT: ANSWERED

There is a maintained fork of this project at https://github.com/JaapvanEkris/openrowingmonitor

Various threads mention different branches, pull requests, betas, and branches. This was initially confusing to me.

If you, like me, want to setup a rowing machine, go to https://github.com/JaapvanEkris/openrowingmonitor and use the installation instructions from the README. Use the main branch.

---

Google directed me to this repository, and it was not immediately clear that I should actually be using the fork. Is there an easy way to make this clearer to other people like me who find this repository?

Ideas

• Modify the README to redirect to JaapvanEkris/openrowingmonitor
• Pin an "Issue" linking to JaapvanEkris/openrowingmonitor
• Pin a "Discussion" linking to JaapvanEkris/openrowingmonitor

I'm guessing the problem is that nobody has permission to pin anything on this github?

---

Additionally, I see mention of multiple versions available from multiple locations - main, beta, beta_update`. Of the following branches and installation guides, which should be used? I realize it is redundant to link all of them -- some are from the same place -- but I think it is helpful to highlight potential sources of confusion.

Should I focus on JaapnvanEkris main branch and ignore everything else? Does the answer change depending on the rowing machine or raspberry pie I want to use?

• laberning branches
  • https://github.com/laberning/openrowingmonitor/tree/main
  • https://github.com/laberning/openrowingmonitor/tree/arcade
  • https://github.com/laberning/openrowingmonitor/tree/v1beta
• JaapnvanEkris branches
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/main
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision-EXTREMELY_EXPERIMENTAL
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision-EXPERIMENTAL
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/Sandbox
  • https://github.com/JaapvanEkris/openrowingmonitor/tree/v1beta_updates_Pi_Zero_W
• other versions mentioned in discussions
  • v1beta_updates - mentioned here, is it identical to JaapvanEkris branch main?

[JaapvanEkris]

Google directed me to this repository, and it was not immediately clear that I should actually be using the fork. Is there an easy way to make this clearer to other people like me who find this repository?

Ideas

• Modify the README to redirect to JaapvanEkris/openrowingmonitor
• Pin an "Issue" linking to JaapvanEkris/openrowingmonitor
• Pin a "Discussion" linking to JaapvanEkris/openrowingmonitor

I think that is a good idea, as the 'youngest' branch in this repository is now 3 years old, and requires an outdated node.js version. I honestly doubt if the branches in this repository would install well on newer versions of Raspian OS, given the many updates to packages etc. we needed to do throughout the years.

As a 'hint' to other users I have opened a PR with a huge list of improvements. But that is the best I can do.

I'm guessing the problem is that nobody has permission to pin anything on this github?

@laberning has these permission.

Should I focus on JaapnvanEkris main branch and ignore everything else? Does the answer change depending on the rowing machine or raspberry pie I want to use?

There is essentially one version really relevant:

• https://github.com/JaapvanEkris/openrowingmonitor/tree/main

This is the stable version where at least 250K of rowing has been conducted to make sure it is stable.

• https://github.com/JaapvanEkris/openrowingmonitor/tree/v1beta_updates_Pi_Zero_W

Yeah, we explained this one in our readme. This version is maintained for the original Zero_W for a grace period. We needed to abandon this platform as a lot of the required packages had become unavailable for newer versions of Raspian.

• v1beta_updates - mentioned here, is it identical to JaapvanEkris branch main?

Yeah, it was renamed to 'main' as the V1Beta_updates was initially proposed as a PR. But after two years of waiting for acceptance, we decided to move on in our own branch. Keeping the name V1Beta_updates didn't sound that future proof under that approach.

• https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision-EXTREMELY_EXPERIMENTAL
• https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision-EXPERIMENTAL
• https://github.com/JaapvanEkris/openrowingmonitor/tree/V1Beta-Architecture_Revision

In a couple of weeks these should have merged into 'main'. Just to clarify:

• 'V1Beta-Architecture_Revision' is a complete revision of the architecture, making it much more futureproof and adding new functionality. It already passed the 250K qualification, but it highlighted some small details needed to be ironed out before we put it into main (we aim for yearly releases, so getting something right the first time is important).
• 'V1Beta-Architecture_Revision-EXPERIMENTAL' contains the fixes for these small details, as well as updates for most packages. It hasn't passed the 250K qualification yet, so we seperate the proven from the unproven code.
• 'V1Beta-Architecture_Revision-EXTREMELY_EXPERIMENTAL' is actually a critical bugfix we are currently working on, as our bluetooth stack has develped issues on newer versions of both Bullseye and Bookworm (see Simultanuous use of BLE for heartrate and app connection crashes bluetooth stack JaapvanEkris/openrowingmonitor#69).. As many people use ORM for connecting to apps like EXR, it is quite essential to get it right, so that required a place to communicate the status of fixes (which are quite extensive).

[cspotcode]

Ok thanks for all the information. My key takeaway is:

As someone wanting to setup a rowing machine...
I should use https://github.com/JaapvanEkris/openrowingmonitor/tree/main
Nothing else.

I'll update my question to mention this at the top so it's easy to find. I've opened an Issue saying the same. #176

[JaapvanEkris]

Ok thanks for all the information. My key takeaway is:

As someone wanting to setup a rowing machine... I should use https://github.com/JaapvanEkris/openrowingmonitor/tree/main Nothing else.

I'll update my question to mention this at the top so it's easy to find. I've opened an Issue saying the same. #176

Thank you for your help!