Jukka Zitting has a mirror of Wicket in git. However, git is rather exlusive to unix developers, and doesn't have a proper integration with Eclipse.
AFAIUI, there is no need for refactoring support in git, because it tracks directory changes and file renames better than subversion. That said, (iirc) windows users are left out of developing using git, which makes it an elitist solution. If you want core developers to look at your stuff you'll need to send in patches. If you want to contribute larger works, you really should file an ICLA with the ASF secretary, and possibly a CCLA [1]. Martijn [1] http://www.apache.org/licenses/ On Fri, Oct 10, 2008 at 6:14 PM, James Carman <[EMAIL PROTECTED]> wrote: > I would be careful setting up a repository which closely "tracks" the > SVN repository at the ASF. I don't know if their servers will see it > as a DoS attack or not. I seem to remember someone playing around > with Git and getting their IP address blocked or some other trouble > when trying to hit the ASF SVN server pretty hard. I don't know how > much traffic your git tracking will cause, but if it's going to be > somewhat significant, a quick note to [EMAIL PROTECTED] might > be a good idea. I'm very ignorant when it comes to git, so forgive me > if my fears are unfounded. :) > > On a separate note, if you guys are the only ones contributing to the > portal support and have been the ones maintaining it, perhaps the > Wicket PMC will consider adding you as committers. I'm not on the PMC > so I can't speak for them, though. But, if you are the ones > contributing such a big piece of functionality, I think you have a > pretty strong case. > > On Fri, Oct 10, 2008 at 12:04 PM, Antony Stubbs <[EMAIL PROTECTED]> wrote: >> Fine, but myself and the couple of other people who want to work on this >> don't have commit access to a branch on svn, so one of the many features of >> Git is it allows us to easily setup a repository, and branches, while >> tracking the Wicket repo, allowing us to collaborate much more effectively >> than exchanging patch files. >> >> Having a branch what we could commit to on the apache wicket svn would >> alleviate a lot of those issues, but that's probably not going to happen. >> >> I'm not going to hi-jack this thread, but there are multitudes of reasons >> why Git > SVN. >> >> I'm kind of surprised by your comments Jonathan as the person who started >> Wicket after all :) >> >> 2008/10/10 James Carman <[EMAIL PROTECTED]> >> >>> On Fri, Oct 10, 2008 at 11:35 AM, Jonathan Locke >>> <[EMAIL PROTECTED]> wrote: >>> > -1 >>> > >>> > i'm sick of new version control systems. i want simple eclipse >>> integration >>> > and since SVN finally works for me i wish people would stick with it. >>> >>> Agreed! The git vs. svn discussion had been done before in different >>> ASF forums and the bottom line is that the ASF uses SVN (currently) >>> for its version control. Also, since source work is not supposed to >>> be done "behind closed doors" (ASF is all about community) it's best >>> if the work is done using the SVN repository. >>> >> >> >> >> -- >> ___________________________ >> http://stubbisms.wordpress.com/ >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
