Im replying inline...
Jeremy Thomerson wrote:
Nino,
Does this mean that you want all Wicket Stuff projects to move to Google
Code
No I do not, I'd want to try one or two projects first, that rely on
teamcity (because we only have problems with teamcity). If we have
problems with google code as well it would be a waste of resources
switching.
because of the problems with the TeamCity builds and SourceForge? If
so, I'd be hesitant to do it this way. Here's a couple reasons why:
1. the very first sentence on your Google code page says that multiple
licenses are not allowed - I've always been under the impression that one of
the reasons we had Wicket Stuff was so that integrations with third-party
libraries (incompatible with Apache license) could be done there (just one
reason)
No there are several other reasons aswell, like the fact that the core
devs do not maintain wicketstuff. But your point are very vaild, and
some of the stuff projects uses libs that are incompatible with ASL...
So if it should work this should be sorted out.
2. We lose all code history - IF the switch were made, we should import
the old repository.
Yes, and thats one of the reasons why I've been so reluctant to do this.
It seems like the community should vote on this before such a big change is
made. Thoughts anyone?
Yes I agree, and also feel that if anyone are up to the task of further
talking with sourceforge this would probably be the way to go, one of my
problems are that I do not have any administrative rights on the server
where teamcity runs from so I cannot go further with teamcity since,
they require details of that character.
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
