On 08/19/2011 02:11 PM, Frank Lanitz wrote:
On Fri, 19 Aug 2011 08:57:36 -0500 Joshjoshua.rh@comcast.net wrote:
@Lex: That makes sense. After this weekend I'll still have time, but it'll be more sparse. I'd like to be a part of it; so let me know what we/I need to do to get this going. Thanks!
1st step: We need to check for points the new system needs to offer (just because github is cool at the moment, I would have a bad feeling if we don't think about what we need before doing anything) and which system might could solve them.
According to the long drawn-out discussions we've had for some time on this topic, I felt the overwhelming opinion was to use Git for version control. As for your concerns about GitHub, it's important to remember that it's just a server to host one of the repositories. They could go offline a week after switching and we would still have all of our code and history. The main reasons people are mentioning GitHub is because it's extremely popular, developer friendly, and a lot of open source projects are hosting their code there.
There is at least github, gitourios and google code if we just have a
Nope, I think it's just GitHub and Gitorious if we want contributor-friendly Git project hosting. I don't think Google Projects does Git at all.
view onto git. There are also a couple of services offering hg or bzr
Except most of the developers don't already know and use Mercurial or Bazaar as much Git (I think).
which are pretty similar to git. So pretty much I'm looking for a specification sheet with possible matches for solution. I suggest to collect this inside the wiki.
We could do this, but it's just more "beating around the bush". We already did have long discussions about this in multiple threads and I think everyone who would like to contribute (besides yourself?), at least those who have spoken up, would prefer Git and a better project site. How much more discussion is needed?
IMO, the only remaining questions are:
1) GitHub or Gitorious or Other (maybe a poll needed?) 2) When (maybe after next release) 3) Does anyone actually like or want to keep using SVN/SourceForge/the current development process?
Cheers, Matthew Brush