You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
congratulations on your project. I have been looking at CraftBeerPi only recently and like it very much. Thank you for your work and effort you put into this.
Not long ago I started to build a small home brewery and was looking for software that could be used to operate it. I'm also a big fan of automation so a software like CraftBeerPi seems pretty nice to use. There are a lot of threads in forums about CraftBeerPi (in different versions) and as it seems - a lot of users that are quite happy with it. So I decided to try it.
It wasn't really easy, though. After finding this repository I was unsure if I should continue to look into CraftBeerPi. There are other versions in other repositories and this version. Craftbeerpi4 seemed like the most recent one but the last change is from 7 month ago. This almost scared me away from the project as it looked as it was not maintained. After searching for alternatives and reading through forums I found some forks that were promoted in the forums as working alternatives to this repository. By coincidence I had a look at the fork of @avollkopf. This fork is the only one I found that can be installed, has a documentation and is actively developed.
Now my suggestion:
Would you consider to create a new github organization and transfer the CraftBeerPi and its plugins to this repository?
Why am I suggesting this? I think this would have multiple advantages for the users of CraftBeerPi as well as its maintainers.
Clear single source of truth
A github organization could be used to have a clearly defined single source of truth. It would be clear that this is the 'main' repository that changes should be pulled into. For example would it be clear that the craftbeerpi/craftbeerpi4 repository is the official one and randomusername/craftbeerpi is 'just' a fork.
Project maintenance by more people
Also more people could help to keep the project maintained. Don't get me wrong, it is of course totally understandable if a maintainer prioritizes their private life over the maintenance of an open source project. The project would then benefit of others that can jump in to help during this time.
And to be clear: I don't want to take the project away from you. You should still be the owner of that organization and the repo and deserve the credit for it. I just want people to be able to continue maintaining the official repo.
And to be clear again: I don't expect to be one of those maintainers, just because I'm suggesting it. I think that should be people that are already actively contributing to the project and that you trust to be good maintainers.
Better perception by new users
I think an organization (or account) that bundles the relevant repositories without the noise of unrelated repositories and that has a name that is clearly distinguishable from a random user name would help users to gain trust to the project and will try it and possibly even start contributing. The current situation with unclear maintenance and a lot of forks of which only few are developed further is not optimal for the project and its users. Certainly not for people who want to contribute.
I would love to hear what you think about that suggestion. Of course from other contributors, too. Please let me know.
All the best!
Philipp
The text was updated successfully, but these errors were encountered:
Hi @Manuel83,
congratulations on your project. I have been looking at CraftBeerPi only recently and like it very much. Thank you for your work and effort you put into this.
Not long ago I started to build a small home brewery and was looking for software that could be used to operate it. I'm also a big fan of automation so a software like CraftBeerPi seems pretty nice to use. There are a lot of threads in forums about CraftBeerPi (in different versions) and as it seems - a lot of users that are quite happy with it. So I decided to try it.
It wasn't really easy, though. After finding this repository I was unsure if I should continue to look into CraftBeerPi. There are other versions in other repositories and this version. Craftbeerpi4 seemed like the most recent one but the last change is from 7 month ago. This almost scared me away from the project as it looked as it was not maintained. After searching for alternatives and reading through forums I found some forks that were promoted in the forums as working alternatives to this repository. By coincidence I had a look at the fork of @avollkopf. This fork is the only one I found that can be installed, has a documentation and is actively developed.
Now my suggestion:
Would you consider to create a new github organization and transfer the CraftBeerPi and its plugins to this repository?
Why am I suggesting this? I think this would have multiple advantages for the users of CraftBeerPi as well as its maintainers.
Clear single source of truth
A github organization could be used to have a clearly defined single source of truth. It would be clear that this is the 'main' repository that changes should be pulled into. For example would it be clear that the
craftbeerpi/craftbeerpi4
repository is the official one andrandomusername/craftbeerpi
is 'just' a fork.Project maintenance by more people
Also more people could help to keep the project maintained. Don't get me wrong, it is of course totally understandable if a maintainer prioritizes their private life over the maintenance of an open source project. The project would then benefit of others that can jump in to help during this time.
And to be clear: I don't want to take the project away from you. You should still be the owner of that organization and the repo and deserve the credit for it. I just want people to be able to continue maintaining the official repo.
And to be clear again: I don't expect to be one of those maintainers, just because I'm suggesting it. I think that should be people that are already actively contributing to the project and that you trust to be good maintainers.
Better perception by new users
I think an organization (or account) that bundles the relevant repositories without the noise of unrelated repositories and that has a name that is clearly distinguishable from a random user name would help users to gain trust to the project and will try it and possibly even start contributing. The current situation with unclear maintenance and a lot of forks of which only few are developed further is not optimal for the project and its users. Certainly not for people who want to contribute.
I would love to hear what you think about that suggestion. Of course from other contributors, too. Please let me know.
All the best!
Philipp
The text was updated successfully, but these errors were encountered: