Small status update

[Aurelien Bompard]

Hi guys !

Just a quick status update to let you know what I'm working on.
I've converted KittyStore to use the Storm ORM instead of SQLAlchemy
internally. This is the same ORM that Mailman's using, so it makes
sense if KS is ever to merge into MM.
I've adapted HyperKitty to work with that.
I've improved KS here and there, mostly as regards to message loading
and its external API, which is still Python-based. At some point I'll
try to implement an HTTP REST API, but that's still far away.
I've also fixed a few bugs in HK, nothing too serious.

Here's my plan now. In my opinion, the aim should be to have a working
version of HK/KS with the smallest number of features to make it
usable as soon as possible, in case Mailman decides to release the
version 3 tomorrow (well, let's say next month).
If you're all OK with this, I'll try to make a usable and tested
version of HK/KS which would be equivalent to the old Pipermail
feature-wise, but with all the required features described here :
http://wiki.list.org/display/DEV/ModernArchiving
Then, we can work on this base and add features incrementally, to
eventually reach the original HyperKitty design.
I would hate to see Mailman release version 3 before HyperKitty's ready :-)

What do you think ?

I'm also going to push my changes back to Bazaar, right now it's still
on my (public!) fedorapeople git repo.

Cheers !
Aurélien

[Aamir Khan]

On Wed, Sep 5, 2012 at 10:19 PM, Aurelien Bompard <
abompard(a)fedoraproject.org&gt; wrote:

>  Hi guys !
>
>  Just a quick status update to let you know what I'm working on.
>  I've converted KittyStore to use the Storm ORM instead of SQLAlchemy
>  internally. This is the same ORM that Mailman's using, so it makes
>  sense if KS is ever to merge into MM.
>  I've adapted HyperKitty to work with that.
>  I've improved KS here and there, mostly as regards to message loading
>  and its external API, which is still Python-based. At some point I'll
>  try to implement an HTTP REST API, but that's still far away.
>  I've also fixed a few bugs in HK, nothing too serious. 

>  Here's my plan now. In my opinion, the aim should be to have a
> working
>  version of HK/KS with the smallest number of features to make it
>  usable as soon as possible, in case Mailman decides to release the
>  version 3 tomorrow (well, let's say next month).
>  If you're all OK with this, I'll try to make a usable and tested
>  version of HK/KS which would be equivalent to the old Pipermail
>  feature-wise, but with all the required features described here :
>  http://wiki.list.org/display/DEV/ModernArchiving
>  Then, we can work on this base and add features incrementally, to
>  eventually reach the original HyperKitty design.
>  
+1

I would hate to see Mailman release version 3 before HyperKitty's ready :-)
>  What do you think ?
>
>  I'm also going to push my changes back to Bazaar, right now it's still
>  on my (public!) fedorapeople git repo. 

>  Cheers !
>  Aurélien
>  _______________________________________________
>  hyperkitty-devel mailing list
>  hyperkitty-devel(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/hyperkitty-devel
>  


-- 



Aamir Khan | 3rd Year  | Computer Science & Engineering | IIT Roorkee

[Pierre-Yves Chibon]

On Wed, 2012-09-05 at 18:49 +0200, Aurelien Bompard wrote:
>  At some point I'll try to implement an HTTP REST API, but
> that's still
>  far away.  
Do note that there is a simple REST API within HK itself, that might
make our life simpler (or not).

Other than that, I am quite looking forward to see what you've changed
(I know I could just checkout your repo ^^).

Cheers,
Pierre