Mend & Renovate & Naming plans #29885
Replies: 4 comments 3 replies
-
I usually refer to Renovate Bot as the "individual" that interacts with us. 🤖 |
Beta Was this translation helpful? Give feedback.
-
Names feedbackI like the new names. I agree that we should standardize. We have so many ways to run Renovate, it's easy to get lost. CLI
I like how the CLI name leads you towards the concept of a "program you run". Community
A possible confusion is that Community implies "for the common good" or "for the commons", so maybe people expect the community stuff to be open source. But this is a really minor nitpick. People will understand that Community means: "thing you're getting from Mend, for free, for the community". Enterprise
With software, Enterprise has always meant that you need to pay to use it. So Enterprise is good for any paid offerings. Draft list of todos for renameIt will be a lot of work to update the docs, readmes, and code. Here's a draft todo list. I'll let you make proper issues for these todos, when you're ready to start work:
|
Beta Was this translation helpful? Give feedback.
-
Sounds like a good plan to try and simplify the naming, and make it a bit easier for newer folks to get up and running on what's what. One thing I will note is that - in a transition period at $work - we've got folks using I wonder if it's worth making a distinction between hosted and self hosted Mend Renovate Community? |
Beta Was this translation helpful? Give feedback.
-
From a naming perspective I think they're all just Renovate (Mend Renovate if you prefer, I don't think it necessary but then my usage pre-dates it being whitesource too). In my opinion what you're really talking about is the license/pricing tier, e.g. Free - open source cli or container images; self-hosted |
Beta Was this translation helpful? Give feedback.
-
Tell us more.
Here's a heads-up about naming adjustments around Renovate, and I'm also happy to hear feedback.
Today we have multiple variants and ways to run Renovate, and it can be confusing. I'll try to list them all in the most descriptive/distinguishable way here:
renovate
. This is also available as:A related challenge has been when to use the Mend name or not (Mend Renovate or simply Renovate), whether to use "Bot" or not (Renovate Bot or Renovate), etc. In general we've dropped the "bot" part but it's totally ok to use it whenever it needs clarification that we're talking Renovate the dependency updater and not renovating bathrooms. For a while I experimented with using "Mend Renovate" when it's Mend-hosted or Mend-enhanced Renovate such as CE/EE, and "Renovate" when it's the pure Open Source part. It's worked OK, but I think this approach created confusion.
Going forward I've decided to align on this approach:
Therefore the planned list of terms/names is:
Mend Renovate CLI: "CLI" refers mostly to this repo's output - the original/core/OSS Renovate. Available as npm package, Docker images, GitHub Action, GitLab pipeline template, etc. We'll keep the simple
renovate
npm package name, but migrate the rest under Mend's orgs.Mend Renovate Community: "Community" will refer to any non-OSS but free offering from Mend, e.g. the existing Mend Renovate Community Edition, or the existing free Renovate plan on the Mend Renovate app for github.com and Bitbucket Cloud.
Mend Renovate Enterprise: "Enterprise" will refer to any commercial/non-free Renovate offering from Mend, e.g. the existing Mend Renovate Enterprise Edition, or any future paid plan on the Mend hosted apps.
Beta Was this translation helpful? Give feedback.
All reactions