Next steps, and congratulations!

[Henry Andrews]

Hi folks,

  Congratulations to Jochen and everyone else involved on the new version of the site!  The reprint links are fantastic and it's great to see a specific feature so long-anticipated become a reality.

  Jochen, do you have any particular plans for tech work right now?  I don't know exactly when or how steadily I'll be able to work on it, but I would like to start working on search.  I also think that my original design for the OI is starting to show its limitations and I kind of want to poke around with some ideas that might make features like reprint linking (and similar stuff that we'll want to do for other features) easier to present.  I think what you have is as good as it's going to get in the current design, but I've picked up some jQuery UI skills in the last year that might open up some more options.  AJAX can be overused, but I think in the case of the reprints work it could really help a lot with only a bit of effort (now that I know jQuery reasonably well).

  But if you're still planning on doing a lot of active tinkering with the reprint UI, or have other major plans, I don't want to step on that.

  On a technical level, I know you use git for a local repository.  I would really not object to switching things over to git entirely.  I chose Subversion because it was what I was using at work at the time, but at this point it's pretty clear that git is technically superior for our usage.  No urgency at all there, but I hear it's not that hard to migrate SVN to git with history preserved.

  Finally, what version of Django are we on now?  1.4 is out, although for search I need to make certain that Haystack 2.0.0 beta is compatible with it.  Haystack 1.x and 2.0 are different enough, and the development is active enough, that we should probably work with 2.0.0-beta unless we encounter problems.

thanks,

-henry

[Daniel Nauschuetz]

Outstanding work to everybody involved in the upgrade!  Thank you, thank you, thank you.

 

Daniel

--
GCD-Tech mailing list - gcd-...@googlegroups.com
To unsubscribe send email to gcd-tech+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/gcd-tech

[Lionel English]

Me too, me too, me too!

--
Lionel English
San Diego, CA
lio...@beanmar.net

[Mark]

Here here, cracking job all round!

>>   On a technical level, I know you use git for a local repository.  I would
>> really not object to switching things over to git entirely.  I chose
>> Subversion because it was what I was using at work at the time, but at this
>> point it's pretty clear that git is technically superior for our usage.  No
>> urgency at all there, but I hear it's not that hard to migrate SVN to git
>> with history preserved.

You can actually hook git to pull/push into svn, might help allowing
you to run side by side?
http://schacon.github.com/git/git-svn.html

Conversion help is here (also links a few guides)
http://help.github.com/import-from-subversion/

Mark

[Jochen G.]

I have no big plans for tech work. Some further clean up of problems,
some changes based on experience now that editing of reprints is in full
use.

I have to admit I never fully understood what we actually mean by OI vs
UI... So I can't answer those questions ;-)

I actually use bazaar when I have bigger changes going on which other
changes depend. But I am fine with git as well. Does sourceforge support
migration from svn to git ? post-review and review-board probably do use
it ?

I recently looked at django 1.4 and we surely want to directly update to
it from django 1.2 since it has some nice improvements we can use
(select_for_update, some support for select_related over m2m-relations).

If haystack 2.0 doesn't support django 1.4 now it will do so at some
point, so we surely should go with the newest version of haystack right
from the beginning.

We could use a name for 0.7 which should mainly be the release for
haystack and the update of the code to django 1.4.

Jochen