[$] SUSE asks openSUSE to consider name change
SUSE has, in a somewhat clumsy fashion, asked openSUSE to consider rebranding to clear up confusion over the relationship between SUSE the company and openSUSE as a community proje [...]
[$] SUSE asks openSUSE to consider name change
SUSE has, in a somewhat clumsy fashion, asked openSUSE to consider rebranding to clear up confusion over the relationship between SUSE the company and openSUSE as a community proje [...]
@omenos @monsieurborni @LWN It's not straightforward even to us who deal with it all the time. That was a point many people tried to make in the conference talk and the ensuing discussion.
@monsieurborni @LWN I would say associated is a bit of a broad term. I would go with "confused" instead. For example, let's look at the Red Hat ecosystem:
RHEL, CentOS, Fedora. None of these legally related projects can be confused with each other. The numerous derived projects of Fedora (Nobara, Universal Blue, etc) aren't confused with Fedora proper.
But SUSE and openSUSE? Before even getting to Leap or Tumbleweed one just sounds like a free version of the other.
@monsieurborni @LWN Which comes to the point of project vs product confusion. openSUSE shares a package pool base with SUSE, but the actual deliverables are not 1:1 with SUSE's offerings. As someone who had to explain the value of RHEL versus related projects like CentOS, I would not want the headache that would come from explaining the minute details of the SUSE ecosystem.
It may seem straightforward to us, but many businesses don't make decisions based on our way of thinking.
@LWN So, do I understand this correctly: they don't want the community project to be associated with their brand?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.