Also, if things move to Github and issues need to be moved, I spent some time getting too familiar with how that process works. There are no easy to use tools to move issues, it is inexact at best, but I do have the code that was used to move the Brix issues and am happy to post to Github if anyone wants it, contact me off list.
On Dec 14, 2010, at 3:19 PM, Brian Topping wrote: > We moved Brix to Github over the last several weeks. I was somewhat > skeptical at first, but I like it a lot. People that want a patch can just > fork the project, and if the project wants their changes, they are trivial to > grab. > > The issue management at Github is pretty weak. Usable for projects the size > of Brix and WicketStuff, but weak. > > As far as wiki is concerned, it seems like Brix would be ideal for this, but > I haven't gotten any traction in this regard. I believe a wiki written in > Wicket would be valuable for a lot of projects, but this discussion shouldn't > be sidetracked into the relative (lack of) merits. Interested folks can > contact me off list if they want to discuss. > > +1 for Github. I agree in principle that being closer to Apache is a good > thing, but for widgety projects, there's too much overhead to adding new > folks. > > $0.02... > > Brian
