naali repo renamed to tundra / Tundra tomorrow 12:00 Finnish time

[Toni Alatalo]

Hi,

we now decided to finally rename the Tundra SDK repository from the old original naali name (which was client code only, back when opensimulator was used as the server).

We’ll do it tomorrow at noon (Finnish time).

We still have to decide whether it will be ‘tundra’ or ‘Tundra’ (or ‘TundraSDK’ but I don’t think we want that). We’ll decide that by 10am :)

This will not break the github network — forks and pull requests and all those will remain intact. That got tested recently when we renamed WebTundraNetworking to WebTundra, after playsign had already forked it, and that caused no problems.

Only required actions I’m aware of are:
0. the actual repo rename in github web ui (I can do it at noon)
1. every clone devs have in their own compus need to change the remote url (in .git/config, can use git commands or gui for that too but i usually just edit the conf)
* direct clones of reX-Tundra - devs using Adminotech or Ludocraft work don’t need to do anything
2. we need to change links on the web:
* realxtend.org
* code.google.com old naali project page, which links to github now
* possibly Opensimulator wiki and such if they have github links, I’ll check

Optionally we could also create an empty dummy ‘naali’ repository that just tells that it’s renamed to tundra now, in case there are links in places we can’t change. But if we do that I think it’s good later to not get confused during the transition.

I think now is a good time to do this as there’s not much publicity or outside activity (like there was when we did the naali -> tundra transition, for example my IEEE Internet Computing magazine article had links to the example codes in the naali repo etc).

Soon there will be more, possibly a lot of, activity and publicity etc. as we’ll be making new releases also as EU fi-ware deliverables (first now in January already) etc. and the documentation for those will be up in fi-ware.eu wiki etc. And web client releases with apps using it are coming soon. So is good to do this now to not be stuck with the old name forever! We’ll post more info about the fi-ware project and web client plans etc. a bit later, now still need to work on them (anyone can follow it on github and discuss here or on irc at will already). Basic background announcement of the fi-ware & realXtend partnership was on CIE’s website in August, "Oulu Companies to develop Europe-wide future 3D internet platform” http://www.cie.fi/?sid=85&src=news&udpview=displayitem&lang=en

After the repo rename we could also get to normal branch naming like we did back in the naali days (applying http://nvie.com/posts/a-successful-git-branching-model/).

~Toni

P.S. currently I think lowercase ‘tundra’ is the stronger candidate but is good to sleep on it - if someone wants to check arguments for and against so far, I copy-pasted that part of the irc discussion to http://pastebin.com/ijEF145g :) .. as often with programming, naming decisions are frustratingly nontrivial (tech decisions are often simpler as there pros and cons are clearer)

[Jonne Nauha]

As said on IRC +1 for the new name to be "tundra" and renaming other repos to reflect this. Its a mess of mixed things now: "web-tundra", "tundra-addons" etc.

Here is some help for people that have active forks or clones of Tundra. How to change the URL after the change. My example assumes that the new name will be "tundra", if not change it. In general just use "git remote -h" it is pretty clear what you need to do :)

git remote -v

// See what remote name points to github.com/realXtend/naali.git, if you have cloned the repo from it will 

// most likely be "origin" otherwise whatever you named it when adding the remote to your fork "rex" "upstream" or similar.

git remote set-url <remote-name> git://github.com/realXtend/tundra.git

// If you have commit rights and want the remote to be pushable, the above should afaik be g...@github.com/realXtend/tundra.git

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.

www.meshmoon.com

--
--
http://groups.google.com/group/realxtend-dev
http://wiki.realxtend.org
http://dev.realxtend.org
---
You received this message because you are subscribed to the Google Groups "realXtend-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to realxtend-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Ali Kämäräinen]

I'd vote for "Tundra" for at least two reasons:
1) "Tundra" is a proper noun, and the name of the product/project, and
2) the repository name is essentially a file/folder name and the majority of the files in the repository use title case (even the executables are "Tundra" and "TundraConsole")

[Antti Ilomäki]

IIRC the name "Tundra" was originally my idea, so any other name is probably much better.

2014/1/9 Ali Kämäräinen <stink...@gmail.com>

[Ali Kämäräinen]

This might have been one of those rare occasions that you're blabbering has not been completely ridiculous. ;) 

[Toni Alatalo]

good points i find,

1) is obviously kind of strong, but

exactly 2) is what it makes it a practical consideration too:

< Pforce_> i dont like FolderNames on windows either

< Pforce_> it looks horrible

< Pforce_> im very ocd about this

< e`> unix is case sensitive so "cd tundra" or having "tundra" in a path name will just break

< Pforce_> yeah cd /home/jonnenau/code/t <TAB> not going there would be a disaster

< Pforce_> :D

< Pforce_> that would bug me out so much

perhaps that’s why we went with lowercase in the first place.

~Toni

[Jonne Nauha]

I don't think any grammar reasoning nor that its a project name should have any impact on it :P The repo url and the folder on the hard drive is used by developers on a daily basis. People are certainly not going to wonder about why its lower case in the github url or why the projects code space is lower cased. It's not something that will affect anyone. It will however affect us who work with the repo, look at the url, clone, add remotes, manage forks.

I know you can make <TAB> be case insensitive on linux and it is that already on windows. I know you can change the dest folder to be lower case when you fork.

Looking at the Windows Tundra dependency folder where we build our deps from sources (either cloning a repo or unpacking a source zip etc.). I have 23 folders which all but "OpenAL" is all lower case, all the way, most replacing spaces with "-" (which i also like :). I would say that this is the norm out there in the world.

As said this is a trivial thing but still everyone has their opinion about it :)

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.

www.meshmoon.com

[Toni Alatalo]

https://github.com/realXtend/tundra

apparently github nowadays does redirects so also the old urls work, at least from web and possibly as a remote url ref in your local git clones too — which is great .. so https://github.com/realXtend/naali goes to that same now. i’m in a workshop still so no change to change web links yet but i’ll do that soon — nice that they are not broken now anyhow.

~Toni