On 7 Aug 2012, at 17:06, Marcos Daniel Petry wrote:
> I'm not sure if this would be the best approach, but I think the best way is take one of the forks who is more mature and work on it, then we avoid possives problem with merges and we can focus on improving django-photologue :)
I'd looked at several of the forks of django-photologue that exist on Github, and one problem that I found was that all of them in some way had 'personalised' photologue to fit specific circumstances. If I'm wrong, then please point me to a good fork, and - in theory - it should only take an hour or two for me to take all the commits on it and apply them to the jdriscoll codebase.
> the repository that appears at the top of google searches is the GoogleCode. is it not better put in this repository a message "moved to http://??"
Yes, it's on my list of things to do to contact Justin Driscoll about it :-)