Move Project to GitHub

[GoogleCodeExporter]

I'd highly encourage you to move this project over to GitHub. It's a much more 
popular 

Honestly, I'd be willing to write code to help improve this project and fix 
bugs, but only if it's on GitHub. It's so much easier to collaborate, fork 
code, make my own commits, and pass them back to you.

Plus it gets way more exposure for your code. Most developers are using GitHub 
as their primary open source repo host these days.

Would you be willing to make the switch over?

Original issue reported on code.google.com by auzigog on 19 Jan 2012 at 6:43

[GoogleCodeExporter]

There are two different concerns here. The use of Git vs SVN, and the use of 
GitHub instead of google-code.

As for the visibility of the code I don't really think I need more visibility. 
I'm referenced on Flickr's site and I'm in the first hits in Google.

As for the use of Git instead of svn, why not, but you'll have to convince me 
it has real advantages compared to svn, with which it is also easy to commit, 
make branches and merge them.

So I think we should discuss this point.

Original comment by alexis.mignon on 20 Jan 2012 at 9:36

[GoogleCodeExporter]

Original comment by alexis.mignon on 20 Jan 2012 at 9:41

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by alexis.mignon on 20 Jan 2012 at 9:48

• Changed state: Accepted

[GoogleCodeExporter]

Thanks for being open to discussion on this. I appreciate that!

Well the benefit of GitHub (or other git project hosts) is that it makes 
collaboration easier. While you technically get this benefit by just switching 
to git, tools like GitHub make it much much easier and more realistic that 
collaboration will actually occur.

For example, on GitHub, I could have forked your code, fixed all the issues I 
reported, and issued a pull request before you even logged on to see anything 
had happened. While I technically could've done that with SVN, and uploading 
patches, it would've been a pain.

Most open source projects are on github these days, so lots of developers are 
floating around that ecosystem, ready to make contributions. Or at least I am. 
:)

How does that sound? Is that enough of an advantage for you to make the switch? 
What are your concerns/interests in this regard?

Original comment by auzigog on 25 Jan 2012 at 7:27

[GoogleCodeExporter]

+1, if only so I can issue pull requests instead of patches (the latter of 
which I'm often too lazy to do and will just describe the code changes in an 
issue instead).

Original comment by he...@1337stream.com on 3 Feb 2012 at 3:59

[GoogleCodeExporter]

*+1 - I'd be interested

Original comment by sam...@productsy.com on 7 Feb 2012 at 4:58

[GoogleCodeExporter]

I wanted to revist this. Clearly there is support from other folks for this 
migration as well.

Is it something you'd be open to?

Original comment by auzigog on 26 Mar 2012 at 12:40

[GoogleCodeExporter]

I've been looking at the git support in google code which , from what I've 
read, lacks of the 'pull request' capability.

I'm open to a conversion to git, but badly lacks of time to do it right now, 
I'll think of it when I have more free time.

For now, this remains a small project and so far bugs were minor ones (in terms 
of coding) and they usually take very few time to correct, so the svn issue is 
not critical (for me at least).

I must also confess that the projects is also a way for me to test some new (to 
me) programming concepts (such as the new object api, did you have a look ?), 
so I appreciate to have the hand on the main development line.

However, the 'pull request' capability of git seems very interesting, and as I 
said, I'll really consider it when I have time.

Kind regards

Alexis

Original comment by alexis.mignon on 26 Mar 2012 at 2:48

[GoogleCodeExporter]

I'm trying to use your code on Heroku. Another problem I'm encountering is that 
heroku's version of pip doesn't allow for SVN support. So I can't have your 
repo in my requirements.txt.

For now, I'm going to make a clone of your repo on github and have references 
back this site. I'll be using git svn to make that happen.

When you're ready to move it over to github yourself and have that be the 
"primary" repo, I'll delete my github mirror.

Let me know if you have any thoughts on that. :)

Original comment by auzigog on 27 Mar 2012 at 3:47

[GoogleCodeExporter]

This is the tool I'll be using to move it over to github: 
http://stackoverflow.com/questions/796991/fork-and-synchronise-google-code-subve
rsion-repository-into-github

You can do the same thing with those first three lines if you want to in the 
future.

Original comment by auzigog on 27 Mar 2012 at 3:48

[GoogleCodeExporter]

The mirror of the repo is now here: 
https://github.com/auzigog/python-flickr-api/

I will be making changes on this branch: 
https://github.com/auzigog/python-flickr-api/tree/develop ... They won't be 
changes to the code with the intent of forking it. They will be just be a 
demonstrations of changes I think you should make. And the commits will be 
really easy to turn into patches if you want to integrate the changes I 
suggest. (This is basically the pull request functionality, but a lot more 
complicated since it is going across systems).

And when I'm able to, I will pull in the changes you make on the SVN repo using 
"git svn rebase"

Let me know what you think. :)

Original comment by auzigog on 27 Mar 2012 at 5:32

[GoogleCodeExporter]

[deleted comment]