I second everything Ayende is saying here. Fluent NH flourished after I made the move to git, and a huge part of that is Github. Moving anywhere but Github would be foolish.
On Nov 3, 11:42 am, Ayende Rahien <[email protected]> wrote: > Diego, > I know of a LOT of OSS projects which are using Git > I know of very few using HG. > > On Wed, Nov 3, 2010 at 1:37 PM, Diego Mijelshon <[email protected]>wrote: > > > > > > > > > Oren, > > > What stats do you use to say Git is more popular? > > I think they both have lots of followers. > > > I'm slightly biased towards HG, because it has an easier learning curve and > > it doesn't have the "non-native" feel of Git on Windows. > > Regarding the specific points you mentioned: aren't those just Github > > features whose current implementation you like instead of Hg/Git > > differences? > > > In any case, here's my 2c regarding source: > > > - There seems to be a consensus to move to a DVCS. Nobody wants to stay > > with SVN > > - As others said, after the release might be a good time to do the move > > - IMO, the decision should be done first by the committers and, if > > there isn't a clear winner, by the contributors. How about a poll? > > > And regarding the site (in no particular order): > > > - I've said it before: the current state of NH identity is just > > terrible. Searches for "nhibernate" "nhibernate source" "nhibernate bug > > tracker" "nhibernate docs" and "nhibernate binaries" should all point to > > a > > unified site. > > - I don't have anything against Jira per se, but having it redirect to > > an IP is just unprofessional > > - SourceForge still feels like 1999. I really like Google Code, I > > dislike CodePlex, and GitHub is meh. But the decision should be made by > > those in charge of maintaining it. > > > Diego > > > On Wed, Nov 3, 2010 at 08:03, Ayende Rahien <[email protected]> wrote: > > >> Frans, > >> Git is more popular than hg. And we aren't considering centralized SCM > > >> And yes, there is a HUGE difference between sending a patch and sending a > >> pull request. > > >> a) it is *significantly* easier to handle a pull request, because it is a > >> single command, rather than a set of operations > >> b) it allows you to have your own fork and easily merge future changes > >> c) it means that Joe can pull from you, not just from the master feed > > >> On Wed, Nov 3, 2010 at 12:54 PM, Frans Bouma <[email protected]> wrote: > > >>> > I actually do have a problem with hg. I think that Git is: > >>> > a) more popular > > >>> than what, subversion? Perforce? CVS? > > >>> > b) GitHub has tremendous pull in terms of encouraging contributions. > >>> > c) I saw a huge spike in the amount of people contributing once I moved > >>> to > >>> > github. > > >>> I have a hard time believing that the scc system used is of any > >>> relevance whether a developer is capable of contributing any code. I > >>> mean: > >>> it's not as if someone who changes some code in his own branch is > >>> suddenly > >>> able to commit those changes as well: the change has to be reviewed, > >>> tested, > >>> agreed upon and then it's committed. A svn patch is just as simple for > >>> that > >>> than any other patch. > > >>> I don't deny what you saw on ravendb stuff, I just find it a > >>> 'coincidence' rather than a correlated event. > > >>> FB > > >>> > On Wed, Nov 3, 2010 at 12:31 PM, Fabio Maulo <[email protected]> > >>> wrote: > > >>> > And move the code in CodePlex... > > >>> > -- > >>> > Fabio Maulo > > >>> > El 02/11/2010, a las 16:38, Jorge <[email protected]> escribió: > > >>> > > Hello there, > > >>> > > I am in the process of downloading the code via SVN, and it is > >>> > taking > >>> > > a very long time. > > >>> > > Can someone please enable Git repo in sourceforge, or better > >>> yet, > >>> > move > >>> > > code to Github? > > >>> > > Respectfully yours, > >>> > > Jorge
