SVN about lightopenid HOT 5 CLOSED

I use a git repository, located at http://gitorious.org/lightopenid.

I don't think that using svn would make viewing changes any easier.

Well, I thought it is easier to use SVN. 
* You only have to type `svn commit . -m "Bug XY removed" --username 
YourUsername` and all changes to all files get uploaded. Can you do this also 
with git?
* If you just want do make a quick change, you can do it (see 
http://googlecode.blogspot.com/2011/01/make-quick-fixes-quicker-on-google.html 
) 
* You can see the difference between two files, (e.g. 
http://code.google.com/p/closure-datepicker/source/diff?spec=svn17&r=17&format=s
ide&path=/trunk/closureDatepicker.js&old_path=/trunk/closureDatepicker.js&old=16
) ... well, this can also be done with diff / colordiff on Linux, but it is 
much more comfortable to use this function online
* Everything of this project would be hosted on one service

This was only a proposal for you. If you think this would take you more time to 
use SVN than git, please don't do it. I like your work and would rather like 
you developing lightopenid than changing from git to SVN ;-)

I am under impression that git is easier to use than subversion, but that's 
probably a matter of preference.

  * It is possible to commit changes and upload them as easily: `git commit -am "Buy XY removed"; git push`. Again, it's a matter of preference whether you want the changes to get uploaded immediately or not. svn seems to do it, and git doesn't (and I prefer it that way -- it's possible to change it).

  * True, I can't make quick changes on the web like in google -- but since I test each change I make, and therefore have to change it locally, this feature is of no use to me.

  * As for diffs, a sample commit diff: http://gitorious.org/lightopenid/lightopenid/commit/af58649ab3a6f43142900b6d4173f16a51ae3acd?diffmode=sidebyside . So it's also possible to do it online, which is indeed useful.

  * Actually, the google code project is an addition to gitorious hosting, not the other way. I just needed a bug tracker for the project.

That said, there is one upside to using gitorious: merge requests. It sometimes 
happens that someone wants to add their code to LightOpenID (see example[1]). 
Gitorious allows me to easily view the change online, provides me with 
instructions how to merge it, and most importantly -- does in a standard git 
way, attributing the changes to people that posted them, along with their 
commit messages.
Now as far as I know, if I wanted to import someone's code into an svn repo, I 
would have to either copy-paste the code, or give the person write access to 
the repository. With git, I do neither. I review the changes before importing 
it to my local repo, then test it myself, fix possible bugs, and only then, 
commit.

So I think that this is enough to stay with gitorious. Do you agree?

By the way, if you're interested in reading more pro-git propaganda, see 
http://whygitisbetterthanx.com/ .

  [1]: http://gitorious.org/lightopenid/lightopenid/merge_requests/2

I agree with you. I will test git with my next little online project, thanks 
for the links and the explanation.

I just want to ask you three little questions more and I don't want to start a 
new issue for that, so I'll ask here:

Did you think about a "Donate" button? If you don't know how to create one, I 
have written a little post about that: 
http://martin-thoma.blogspot.com/2011/01/using-paypal-for-your-online-project.ht
ml

Do you have a demo page? I always enjoy to see the code in a example-page.

Do you know how many projects are using your library?

I did think of a "Donate" button, but didn't implement it after all. But maybe 
I will.

There is little to show off, and as far as I know, neither google code, nor 
gitorious allow a demo page hosting. I don't know any other openid library 
(written in php) that has demos anyway. That said, since LightOpenID includes 
working examples that should be functional without any configuration, it's easy 
to test it yourself.

I don't know exactly how many projects use it. I know that there are several 
more or less useless forks that do nothing but change the api or remove random 
functionality for no apparent reason, so even if I wanted, I couldn't count it 
in any way.
By googling lightopenid, I could find at least two projects that documented 
their usage of the library, and several blogs describing how easy to use it is. 
Also, since people write mails to me, asking about it, I think that there are 
projects that actually use it, and their numbers seem to grow.
The download counter from this project shows 21 downloads of v0.4, released 5 
days ago.

That's the most accurate measure I have. However, from what I've seen on 
stackoverflow, when asked about an php openid library, people are recommending 
either php-openid (that is bloated and currently unmaintained), lightopenid, or 
some fork of lightopenid, so I think that most new users end up using code from 
this project.