Thanks to everyone who has contributed to the discussion so far. I think that there is a general consensus to have 2 branches of Photologue: - a 2.X branch, that keeps the project in more-or-less its current state. - and a 3.X branch that adds lots of new features (as championed by Colin Powell).
As my time is limited by other commitments - e.g. wife, money and son :-) - I personally wish to concentrate on the 2.X branch. To get the ball rolling, I have created a couple of issues and milestones on the Github page (https://github.com/jdriscoll/django-photologue/issues).
There are several clones of Photologue on Github; I've thought about this for a while. Some are a lot more advanced and feature-rich than the "canonical" clone at https://github.com/jdriscoll/django-photologue. On the other hand, the canonical clone will give us good access to Pypi, and will help keep Photologue at the top of google search results for "django photo gallery" - which is very important IMO as the more people use the project, the more bug reports/enhancements will flow in. So my leaning is to use the jdriscoll repository and backport changes that people have made on other clones of django-photologue.
By the way, I've created a quick silly Django project that just contains Photologue and uploaded it to http://photologue.arbee-design.co.uk/ This is so that I can check that the current Photologue codebase works against different versions of Django, etc.... This was just done for myself, but if anyone thinks it could be useful, please let me know and I will upload a copy to my Github account.
I look forward to seeing the first pull request :-)
> Thanks to everyone who has contributed to the discussion so far. I think
> that there is a general consensus to have 2 branches of Photologue:
> - a 2.X branch, that keeps the project in more-or-less its current state.
> - and a 3.X branch that adds lots of new features (as championed by Colin
> Powell).
> As my time is limited by other commitments - e.g. wife, money and son :-)
> - I personally wish to concentrate on the 2.X branch. To get the ball
> rolling, I have created a couple of issues and milestones on the Github
> page (https://github.com/jdriscoll/django-photologue/issues).
> There are several clones of Photologue on Github; I've thought about this
> for a while. Some are a lot more advanced and feature-rich than the
> "canonical" clone at https://github.com/jdriscoll/django-photologue.
> On the other hand, the canonical clone will give us good access to Pypi,
> and will help keep Photologue at the top of google search results for
> "django photo gallery" - which is very important IMO as the more people use
> the project, the more bug reports/enhancements will flow in.
> So my leaning is to use the jdriscoll repository and backport changes that
> people have made on other clones of django-photologue.
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 :)
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://??"
> By the way, I've created a quick silly Django project that just contains
> Photologue and uploaded it to http://photologue.arbee-design.co.uk/ > This is so that I can check that the current Photologue codebase works
> against different versions of Django, etc.... This was just done for
> myself, but if anyone thinks it could be useful, please let me know and I
> will upload a copy to my Github account.
> I look forward to seeing the first pull request :-)
> - Richard
> --
> You received this message because you are subscribed to the Google Groups
> "Django Photologue" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-photologue/-/G0LViDWQb_UJ.
> To post to this group, send email to django-photologue@googlegroups.com.
> To unsubscribe from this group, send email to
> django-photologue+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-photologue?hl=en.
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 :-)
> 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.
I believe that my fork fits in this situation, with the exception of the
layout of the change list, all changes that were implemented were intended
only for the evolution of project, and all changes have a good test coverage
if everyone agrees, we can use it as a basis respository, or at least as a
temporary repository and then migrate the changes to the final repository
> 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
> :-)
> --
> You received this message because you are subscribed to the Google Groups
> "Django Photologue" group.
> To post to this group, send email to django-photologue@googlegroups.com.
> To unsubscribe from this group, send email to
> django-photologue+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-photologue?hl=en.
