On 24/03/2008, at 10:15, Christian Vogler wrote:
Ok, so, let's get started. I made a few modifications to SOLR-216
that fix
some unicode and timezone conversion issues, and I can upload them
wherever
we want to host the project.
There is at an outstanding XML unicode bug that was discussed on the
list
about a month ago, so we could take a stab at fixing it, as well.
Best regards
- Christian
On Monday 24 March 2008 14:11:44 Ed Summers wrote:
On Mon, Mar 24, 2008 at 6:32 AM, Leonardo Santagada
<[EMAIL PROTECTED]> wrote:
Thanks, I think most of the stuff that I wanted to do is there... I
will take a closer look and if there is omething missing I will
add to
that. Why is this on the issue tracker and was not commited to the
svn?
Back in September of last year I started with SOLR-216 and ran into a
few problems (one of which is documented in that ticket history).
Personally, I'd like to see a little project on google-code, and a
record up at the CheeseShop so the code could be easily installed and
deployed.
I'd be willing to help out on it too, as I'm embarking on another
Solr
project where python integration is key.
//Ed
I created the project on google code, the url is http://code.google.com/p/solrpy/
please send me your google account if you want to join the project.
I already added Vogler as another adimin to the project.
Christian, please commit your modified version inside the trunk
directory... or better yet, commit the issue 216 version then your
modified version so we keep history of the changes. Later we should
discuss writing the necessary distutils files and maybe make a test
directory and choosing a testing framework (I would vote to use
py.test or nose and not unittest but I am ok with anything you guys
want). When everyone joins we should make a mailing list to discuss
this things or meet on IRC.
--
Leonardo Santagada
