would yii go for github and with git ?

[Simos]

+1 for GitHub. As we already have our own Yii repo there with Yii 1.1.8 lol

I think it’s important for the Yii project to move to some GitHub-like environment (there must be others, I’ve only seen GitHub) where it’s easy for others to fork and contribute…

[jacmoe (Jacob Moena)]

From the Atlassian blog:

Why Mercurial over Git or Bazaar?

Mercurial, Bazaar and Git are all awesome tools, but we had to choose one of them. After trying out the DVCS alternatives we decided to go for Mercurial because:

• We felt it had an easier learning curve than Git when moving from a Subversion background.
• Mercurial provides full cross-operating system support
• It comes with a simple set of base commands but powerful bundled extensions which advanced users can enable.
• It provides a great API for writing your own extensions using Python, a language which a reasonable amount of developers at Atlassian have knowledge of.
• It maintains a historical record of its branches and which branch a commit was made on. This can be incredibly helpful when trying to determine the context in which a change or bug was introduced.

Source: moving_to_mercurial_-_why_we_did_it

They recently acquired BitBucket, but you don’t have to use that.

Google.Code already offers Mercurial.

So go for it.

Mercurial would also be nice because NetBeans (my favorite PHP IDE) features excellent support for Mercurial (because the NetBeans team uses it)

And it would also be nice because TortoiseHg works on all platforms (due to the cross-platform-ness of Python)

[samdark (Alexander Makarov)]

We felt it had an easier learning curve than Git when moving from a Subversion background.

Both Git and Mercurial aren’t that easy compared to SVN.

Mercurial provides full cross-operating system support

Same as Git does.

[jacmoe (Jacob Moena)]

Both Git and Mercurial aren’t that easy compared to SVN.

Mercurial is a bit easier, due to the way it’s designed.

Let me quote from this blog post:

Each git command is like a Swiss Army knife. For example, git checkout can switch the working directory to a new branch, update file contents to that of a previous revision, and even create a new branch. It’s an efficient way to work once you learn all the arguments and how they interact with each other. Mercurial is like a well-equipped kitchen — it has a lot of tools that each do one simple, well-defined thing, and do it well. To switch the working directory you use hg update. To update file contents to what they were at a previous revision you use hg revert. To create a new branch you use hg branch. This means there are more commands to learn, but each command is much simpler and more specific to a single conceptual task.

Git is extremely efficient, when you know the arguments.

Mercurial has more commands, but they (generally) do one thing each. Less arguments to remember. Less chance to screw things up.

Same as Git does.

No, not quite.

Git is based on bash-scripts and C, which means that in order to make it run in other OSs than Gnu/Linux, you need to run it through an emulation layer, like MSYS (on Windows), which provides bash and the required subset of GNU/Linux commands.

Mercurial is based on Python and C, and runs on any system on which Python and C runs.

I think I’ll stop my evangelizing now - just want to say that all the cool kids are using Mercurial now.

In the end, all that matters is that the Yii team choose whatever versioning tool that you feel comfortable using.

The difference between Git and Mercurial is truly minimal - it’s just down to preference.

[samdark (Alexander Makarov)]

jacmoe

As I’m aware command line isn’t that different. Anyway, I’m not using it to work with Git or Mercurial and prefer GUI tools. Well, until it’s absolutely needed.

As end user I don’t care about layers needed for Git or other software to function as long as I can just download an archive, unpack it and use the tool. For Git you can get such an archive from http://code.google.com/p/msysgit/downloads/list.

Anyway, as Yii core developer I care more about possible impact on the way framework will evolve and since Git and Mercurial are both offering nearly equal features in terms of DVCS, both have GUI clients, this is more a choice between social features of GitHub and BitBucket.

[jacmoe (Jacob Moena)]

jacmoe

As I’m aware command line isn’t that different. Anyway, I’m not using it to work with Git or Mercurial and prefer GUI tools. Well, until it’s absolutely needed.

I am *definitely * using the command-line as often as possible.

It’s so much quicker to do this:

hg pull -u

to update your repository with external changes than having to open up a GUI tool.

I do use the GUI for commit and log, though.

[samdark (Alexander Makarov)]

jacmoe

I prefer having GUI always launched and just minimizing it when it’s not needed so pulling is as fast as using Mercurial’s command line.

[samdark (Alexander Makarov)]

Google Code now have Git support. Waiting for official announcement and details.

[dongbeta (I)]

to wk,

lucky! google code now support git.

[zekus (Zekus One)]

to wk,

lucky! google code now support git.

still lack that “fork/pull request” that made github famous and many opensource projects fly (Symfony2 to stay in the php framework field). The question is: why don’t we want this to happen to Yii?

[gregmolnar (Molnargerg)]

+1 for github.

I think it would have a good impact on the framework. more contributors, etc.

[Haensel (Johannes)]

There is one thing that people tend to forget: At the end of the day it is also a matter of marketing. Git(hub) is “the new black”. And even if there are other solutions it is equally important for a framework to reach new developers and motivate them to participate. I don’t say that this should be the main focus of course but I really think that Yii would benefit from a broad base of young developers contributing to it. I found myself following projects on GitHub and participating because it is so easy and natural and this is a huge +.

[gregmolnar (Molnargerg)]

participating because it is so easy and natural

very well said. this is why I really like github.

[jacmoe (Jacob Moena)]

Blahblahblah - you start sounding like a bunch of happy priests.

[ianare]

For me, the submodule function in Git is perfect for including other repos in my project. I can have the Yii framework as submodule, and then all the Yii extensions can also be submodules. No more checking out from SVN and copying into my project, and I can be sure I’m always using the latest code.

I realize that mercuarial has something similar, but a lot of Yii extensions are already on github, so that is the main draw for me.

[lightglitch (Mario Ffranco)]

+1

[musterknabe (Jgirnatis)]

+1 for github

would make contributing that much easier.

[chnax (Bx)]

+1 for git / github

Not evangelizing here, but it seems whoever prefers mercurial, can use the Hg-Git mercurial plugin

(http:\\hg-git.github.com/)

Since this is one of your first posts, you are not allowed to embed links in your post.

[meklop (Alejandrofonseca)]

Personally Subversion is still my favorite. It does anything i ever needed from a versioning system.

But maybe i’m just “ugly and stupid”, as Linus Torvalds likes to call those who don’t use git (don’t miss his TechTalk vid on git here: http://www.youtube.com/watch?v=4XpnKHJAok8).

Hi there,

Just a simple question. Have you got a good tutorial that explains how to manage a site on a Web server using Subversion? I’m kind of new to this world and would like to control my code no matters how many developers make changes to it.

Thanks a lot.

Alejandro.

[weavora (Yury Tolochko)]

… this is more a choice between social features of GitHub and BitBucket.

If Yii team really cares about community contributing they can easily check what use active community part (I mean extension contributors). Here is search results into extensions:

github - 108 extensions

bitbucket - 8 extensions

Interesting, right?