Don't have the time to comment on this whole thread (seriously? yet another long post...dude! ;)) but I do have two points I want to make very quickly 1. I think talking about naming anything is premature until we know what the landscape is going to be. Right now, we have Tumbleweed and the beginnings of a new Regular Release which is currently codenamed openSUSE:42. While there is obviously some people who would prefer to keep with the old way of distribution releases, we haven't seen anyone step up to actually do the work to continue that approach. I think the suggestion to maintain the openSUSE name only for the current-style of Regular release is foolish if there is no sign of that way of doing things continuing. So I think any decision about naming (and also versioning) is pointless until things are a little further down the road. This might be a good opportunity to kick around some names, but I certainly would strongly advocate no final decisions until we're much closer to releasing stuff. And for point #2, I have to point out something about one of the suggestions so far On 16 June 2015 at 23:47, Robert Schweikert <rjschwei(a)suse.com> wrote: openSUSE is a Registered Trademark which is jointly administered by SUSE & openSUSE through the Board. SLES is a Registered Trademark belonging to SUSE, and unlike the openSUSE mark, we (the openSUSE Project) have no established agreement to use the SLES Trademark. Discussions I've already had on this topic suggest to me that SUSE would be reluctant to give permission to the Project for the use of the SLES Mark, as it would be confusing both from a market standpoint, and a practical one (as Robert points out, it's based on SLES sources, not a verbatim build of SLES) So, please, consider any and all alternatives before this one -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/16/2015 05:47 PM, Robert Schweikert wrote: 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(a)suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

On Tuesday, June 16, 2015 05:47:02 PM Robert Schweikert wrote: My proposal. Use a debian / openstack -alike scheme to name things: NAME = openSUSE THEMENAME [NUMBER] THEMENAME = list of alphabetically ordered names of the same thematic NUMBER = 1, 2, 3, 4 ... Some candidates for THEMENAME are: - Names of colors: https://en.wikipedia.org/wiki/List_of_colors:_A%E2%80%93F - Names of greens: actually used as a code name for normal openSUSE release https://en.wikipedia.org/wiki/Shades_of_green - Names of trees https://en.wikipedia.org/wiki/List_of_trees - Names of mathematicians: http://www.thefamouspeople.com/mathematicians.php - Names of chameleon species (not good list found so far) - Other So every openSUSE release based on the same SLE version will have the same name. NUMBER correspond to the SP release number for SLE. So SLE12 will have a 0 as NUMBER, SLE12 SP1 a 1. So, for example, if we use names of greens, the names will be: openSUSE Avocado SLE13 + Factory openSUSE Avocado 1 SLE13 SP1 + Factory ... openSUSE Bottle SLE14 + Factory ... openSUSE Bottle 3 SLE14 SP3 + Factory Just an idea. -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 06/16/2015 05:47 PM, Robert Schweikert wrote: Thanks to everyone who contributed to the discussion, we mostly stayed on track and thus it makes it not too difficult for me to try and pull things together. I think we have lots of ideas and it is time to move from discussions and proposal to action and come to a decision. This is a summary, thus not ever aspect or all proposals will be mentioned explicitly ;) In general it appears that the majority of those participating in the discussion is in agreement that the new release should follow openSUSE <SOME_NAME> <SOME_VERSION> Additionally it appears that we agree that <SOME_NAME> should not change from release to release, thus creating a consistent naming scheme for this releases matching the idea with Tumbleweed openSUSE Tumbleweed <VERSION_IS_SNAPSHOT_DATE> openSUSE <SOME_NAME> <SOME_VERSION> Now of course the tougher part is <SOME_NAME> and <SOME_VERSION>. Lets start with <SOME_NAME>. To stick with the "green" and "plant" theme we had <SOME_NAME> proposed as Oak, Fir, <any_other_tree_known>, with some latin thrown in I would summarize the associations one would go for with the choice of tree name as follows: - - stable, strong, longevity - From this bunch Oak appeared to have the most positive responses. A play on words and also playing on duality of two releases was the Rock & Roll naming, i.e. openSUSE Roll <VERSION_IS_SNAPSHOT_DATE> (this would be for Tumbleweed) openSUSE Rock <SOME_VERSION> (this would be the new release) This also had positive responses, although there appeared to be the underlying concern that Tumbleweed would need to be re-named as well and Tumbleweed has become a pretty recognized name. As a third theme a reference to motion was introduced as openSUSE Leap <SOME_VERSION> turns out that Leap also made a nice acronym. I would say that these themes received the most discussion. We had a number of other suggestions with replies. If the name you suggested is not listed explicitly in this summary, sorry. On the <SOME_VERSION> topic it appears that we all agree that the starting version is more or less an arbitrary choice. Most proposals did contain a . in the version which was most often related to the SLE service packs that provide the underlying sources. Thus it would be x.1 for a release based on SP1 sources, then .2 and so on with X incrementing when a completely new source base is available, such as SLE 13 in the future. With X being arbitrary 42, as the project name in OBS and having historical reference in quirkiness in openSUSE appears to have found acceptance. Although starting at 1 is of course just as feasible or even at 12. My gut feel is that people were slightly leaning more toward 42 vs. 1 or 12. Now we need to look at the timing and how we come up with the final name . As a release is targeted for the not too distant future and a milestone is close it would be great to have the milestone released with the final name. The board has been approach to facilitate a quick decision about the name. The board is generally open to have a community vote on the name, with a restricted list based on the summary above. The other option would be for the board to make the name decision. If there is a vote it would have to be a restricted timescale vote due to the timing with a voting period of about 1 week (7 days). Later complaints about "I had no time it was too short" would be considered as bikeshedding. Given that we had both options voiced in the discussions, vote or board decision, can those that have participated in the naming discussion please reply briefly with your preference. Keep in mind the voting period will be short and we'd have to be done by mid July. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei(a)suse.com IRC: robjo -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

Hi, sorry for joining the discussion so late. openSUSE Bonsai Bonsais are cool, beautiful, green, they need a lot of effort to 'create and maintain', they are traditional. It should be also easy to create brand. Best regards, Tomas Cech Sleep_Walker