-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/16/2015 05:47 PM, Robert Schweikert wrote:
Oh no, not another lengthy thread.... I am afraid it is going to be, but hopefully we can stick to the topic and only focus on the name.
A brief summary:
Stephan as the release manager has decided that he will concentrate on building a distribution around the project known as openSUSE:42. In [1] he also tried to start the discussion about the naming of the new distro. However, this did get sidetracked rather quickly, thus, please focus on naming only.
- Not all questions for the new release have been answered, we do not need to revisit this. Some answers will only emerge as the baby starts to crawl and then walk.... - Just because Stephan will take on the release manager responsibilities of a distro around the SLE sources does not preclude another person or team to build/release... a distro based on Factory snapshots.
As the distribution is a representation of the project as a whole, i.e. all contributors, I think it is fair that people get an opportunity to weigh in with their concerns. This view may not be shared by everyone, so please bare with the rest of us as your mailbox once again fills up ;) However, to those participating in the discussion please focus on the name not on side issues.
It has been advocated in other threads that a vote on the name should be considered as the final solution. There are reasonable arguments for and against such a direction. Thus, lets not focus on the voting part at this point either, lets just focus on the name and see where the discussion goes. If this should or should not be voted on can be a separate discussion once we collectively understand the concerns people have with respect to the name.
In a "thread renaming" post we have had the following suggestion:
* openSUSE Oak
"""" So how about Oak? It's a solid tree, it fits with the green theme and it will give us:
* openSUSE Tumbleweed * openSUSE Oak """"
"openSLES" has also been suggested a few times but lets just say that we will probably run afoul with a number of legal restrictions. Plus it is not really SLES, it is based on SLES sources and not a verbatim build of the SLES sources.
My suggestion would be to focus on the name while considering that we should not create a name that would produce a potential conflict as described in [2], also consider the reply [3]
So please lets focus on the name the child might have. State your case for the name you propose, include in the proposal a numbering scheme, if you think we should stick with numbers.
Staring at 1 for a numbering scheme has rather obvious disadvantages, all other numbers are probably equally arbitrary, but you can certainly state the case why the number being proposed is favorable.
I propose the above as the guidelines for the naming discussion. I will add my personal opinion about the name as a follow up post. Lets see if I can manage to stay within my own proposed guidelines ;)
My comments on the name. I think with the developments as they present themselves we should abandon "openSUSE XY.Z" as a name and we should use names in the form of openSUSE SOME_NAME SOME_VERSION This, IMHO, will have the effect that there is no finger pointing as in "why does this release team get the 'openSUSE VERSION_NUMBER' over another release team". I also believe that such a naming scheme will help us in the forming of a marketing campaign built around "The builders choice" tag line proposed at oSC15. openSUSE Tumbleweed - The builders choice for developers openSUSE XXX - The builders choice for sysdamins and devops, rock solid and long term support The choices are clearly differentiated by name and each has a specific target audience. I am using XXX as a place holder for the name of a distribution created around SLES sources. Last but not least I believe this allows us to avoid naming conflicts if/when a distribution based on Factory snapshots should emerge, reference [2] in the original e-mail. The "openSUSE SOME_NAME SOME_VERSION" naming scheme will probably/hopefully not be perceived as a deterrent to such a possible effort and I think this is important. Numbering, given that 1 is not, IMHO, a good solution as a starting position given that we would soon repeat numbers used in the "openSUSE XY.Z" scheme and we have a history of doing quirky things I do like the idea of starting with 42. Given that all numbers after 1 as a starting position can probably be considered equally arbitrary as a selection I think 42 is just as good as any number and it is after all the "Answer to The Ultimate Question of Life, the Universe, and Everything" ;) At this point I really have no strong preference about the middle part, Solar - ever lasting, green energy, shining bright Forest - green, stable ecosystem but new things growing/happening, diverse, sticks with the plant theme Thus, the name for the first release would be something like this openSUSE Oak 42 Then add .1, .2 etc as the base changes with SLE service pack releases and when SLE 13 becomes the base it turns into openSUSE Solar 43 AS I said, no strong preference yet on the middle part ;) That is my contribution to the naming I think I stayed reasonably within my own proposed guidelines ;) Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVgKGxAAoJEE4FgL32d2UkFD4H/RlK6Op2kAVJ+6oGCMDVIJsE OsiFw835JZHt7o9vLkCQgit0PUl/g0WtFkR5fcKDPepO64mzIKzjNR7Sl7uPTFxy htKsUR/sir6r/WaEYZ0SNbeLgnOfFBFV+bzVJFOrE6mqO72g2PDb77mevwktyO/t nFIblKz05D29zgNQm5/LopKwq3uVa6/yfwokunSGvJdEUG6Rs8Y2wGhvnPnn9SzS /g6/xs+yk+J1Vgx6uFz06GCAcwqzhC6mK0/1AsCl6pmq7OU1ZhGKtfAUVG3cXwYD Tu8Uc/8rLkR2M5drt5dWM5rkQbt3YN5j+xOq57tmYJvvF8A3eqBevl9dMEtbdhw= =72T8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org