Gallery switches to Git and GitHub

Submitted by bharat on Wed, 2009-05-27 04:17

You may have noticed that in Gallery 3 we're tightening the scope of the product considerably. We're setting our laser focus on our most common users, those who will benefit the most from our hard work. But this means that some set of our users will always feel sad and abandoned that we're not creating the features that they want or supporting the platform that they use. We hear you, and we're switching to GitHub to try to help you be successful too. Check out our new repository on the web at http://github.com/gallery and read more to learn all the details...

Git is a type of revision control system that's very similar to Subversion and CVS (two other revision control systems that we've used over the past 9 years). The difference is that Git is decentralized which means that everybody's copy of the code is just as good as everybody else's. In fact, each person's copy of the code is a complete copy including the entire history of the code. What does this mean? It means that anybody can create their own fork of Gallery 3 and make it awesome. In short, we're making it as easy as possible for you to create your own version of Gallery that does things exactly the way that you want.

GitHub is a really cool website that makes it easy to use Git. Sign up with them and create an account. Then you can browse on over to our version of Gallery 3 code and click on the fork button and presto-- you've got your own version of Gallery 3. You can make whatever changes you want there, and you can amass a following. Do you have an idea that you believe is right for Gallery? Now it's easier than ever for you to try out this idea and get others involved. Once you've made some changes, GitHub makes it really easy for you to tell us about them and it's just a few clicks on their website for us to pull those changes back into our code base too.

If you were tracking the Gallery 3 code on Subversion, switching to Git is pretty easy. Or perhaps you want just want to download a copy of the code? You can always get the latest copy of the code direct from GitHub at any time.

We're excited about Git. We hope that you are too!

PS: We left Gallery 1, Gallery 2 and Gallery Remote where they are in Subversion. It was easier that way.

dmolavi's picture
Submitted by dmolavi on Wed, 2009-05-27 12:56.

Hey B-
This makes it easier for integration devs to have their own forks, but how does it work w.r.t. having official changes reflected into a fork?

--
For PHPNuke, phpBB2, and phpBB3 integration help, please visit NukedGallery.net.

santm's picture
Submitted by santm on Fri, 2009-05-29 13:31.

if

Quote:
git clone git://github.com/radiant/radiant.git

fails please ensure to use

Quote:
git clone http://github.com/gallery/gallery3.git

as I had trouble with "git" protocol in a share hosting.

jezmck's picture
Submitted by jezmck on Sat, 2009-05-30 07:57.

[EDITED, was a typo]

bharat's picture
Submitted by bharat on Fri, 2009-05-29 22:52.

@dmolavi: it's really easy to integrate production changes into a fork. You just "git remote add" the production repo into your fork, and then "git pull" from it whenever you want to get the latest official changes. I've been maintaining my own fork on github just to see how difficult it is and I'm happy to say it's very straightforward.

@jezmck: I don't know what the problem is there. Best thing I can suggest is that you delete everything and try again and see if that works, if not you might try posting on the GitHub support forums: http://support.github.com -- perhaps they can help?

---
Gallery 3 problems? Check gallery3/var/logs before you post!
Gallery 3 latest code: http://github.com/gallery/gallery3/zipball/master
Gallery 3 from git: http://codex.gallery2.org/Gallery:Using_Git