Move Lobby/ out of trunk/!?

[Auswaschbar]

They are now in https://spring.clan-sy.com/svn/spring/trunk/Lobby, increasing the checkout size, consuming bandwith on updates and fill the commitlog with stuff im not interested in.

My suggestion is to move them to https://spring.clan-sy.com/svn/spring/Lobby/

What do you think (AF, Satirik)?

[Satirik]

i don't care

[imbaczek]

/spring/Lobby/trunk

or, perhaps, each lobby could get its own trunk/branches/tags.

even better: lobbies should have their own repositories, preferably not svn

[Forboding Angel]

assembla is free, fast, and reliable.

[aegis]

maybe only commit major versions to the main svn? (can still track minor revisions elsewhere to prevent coding in a closet syndrome)

[jcnossen]

assembla is free, fast, and reliable.

+1, its awesome indeed: git, mercurial, svn, trac support...

[AF]

kick all the lobby projects including TASServer and the python lobbies out of the spring svn, they don't belong and I and satirik both have alternative hosting for svn.

[Satirik]

i don't ...

[AF]

You know numerous people who do though including me, if you cant find anyone else to host it Ill give you an svn repo at darkstars

The same goes for any other lobby related projects sitting in svn such as TASServer, unity lobby and springie, its about time we had eviction notices for related projects with the capacity to host their own svn repositories.

[Satirik]

without lobby, spring is useless, so lobbies are part of the spring project, so no i don't want another repository, but you can move the lobbies whereever you want

[clericvash]

without lobby, spring is useless, so lobbies are part of the spring project, so no i don't want another repository, but you can move the lobbies whereever you want

I actually agree lobbies directly made for spring should stay in spring svn.

"or, perhaps, each lobby could get its own trunk/branches/tags."

Best idea i have heard, seperates them while keeping them close.

[AF]

Thank you for relinquishing all control of your lobby and every other lobby project under the /lobby folder to Tobi ( he is project leader after all)!!!! =p

However your reasoning is higgledy piggledy because by extension all the AIs are part of the core spring project and so are all the lua widgets ever made and all the mods and games ever built.

Alternatively you could swallow your pride and accept my gesture of friendship by taking the personal svn repository and webspace I offered you.

[jcnossen]

http://www.assembla.com takes all your worries away!

[Auswaschbar]

I did the move now.

without lobby, spring is useless, so lobbies are part of the spring project, so no i don't want another repository, but you can move the lobbies whereever you want

I actually agree lobbies directly made for spring should stay in spring svn.

"or, perhaps, each lobby could get its own trunk/branches/tags."

Best idea i have heard, seperates them while keeping them close.

You can do with the Lobby/ folder whatever you want, svn can make branches / tags in every directory. So its possible to make /Lobby/TASCLient/trunk, /Lobby/TASCLient/branches/branch1 etc.

Thank you for relinquishing all control of your lobby and every other lobby project under the /lobby folder to Tobi ( he is project leader after all)!!!! =p

However your reasoning is higgledy piggledy because by extension all the AIs are part of the core spring project and so are all the lua widgets ever made and all the mods and games ever built.

Alternatively you could swallow your pride and accept my gesture of friendship by taking the personal svn repository and webspace I offered you.

Its not a matter of "its needed to play" or "you can use it together", but of release cycles n stuff.

[bibim]

I believe some TASClient files are used by the installer:

Code: Select all

$ grep Lobby tasclient.nsh
File "..\Lobby\TASClient\lobby\var\groups.ini"
File "..\Lobby\TASClient\lobby\var\tips.txt"

Maybe they should be moved to a subdirectory of the external directory ("external/TASClient") ?