Community Apps >>> Cloudron Catalog Apps

[creative567145]

Hi everybody

It's logical that the following scenario would occur:

1. As more Community apps are added
2. Those that have been marked as very stable
3. Can be processed by the Cloudron team and added in the official Cloudron Catalog

---

In that scenario, the people that have been using a Community App
(examples: Hermes, Fizzy, Garage S3, Ente, Browserless),
would have 2 choices:

1. Stay on the Community version (if the maintainer decides to keep maintaining it)

2. Switch to get the new updates from the Cloudron source

• This post is about that.
• It would be awesome if the Cloudron team could (some day) release an update which includes the option to switch from the Community source, to the Cloudron source.
• This way, a migration is not needed and the transition goes smooth.

---

This way, the Cloudron Catalog can grow much faster while with max stability.

Hope that was useful

[girish]

@creative567145 good you bring it up. At least in my mind, the Cloudron catalog is not the "next step" in a community package's lifecycle. In some cases it might actively hamper the community package author. For example, if we were to take over @luckow 's packages from his recently announced package store, I am not sure how he feels (given he has invested much time and resources into this).

Maybe it makes sense for Cloudron team to take over when the package is popular and well in use but the community packager does not want to maintain anymore. This probably requires collection of some stats on package installs which we don't collect (but probably the packager can collect on their server to get a guesstimate).

Not sure how others perceive all this though, happy to collect some input here.

[ruihildt]

@girish As a cloudron customer, I will always trust more cloudron to do a good job maintaining a package, so if it makes sense to take over an existing package which is community maintained (due to general demand for example), then Cloudron should do it.