samizdat-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Samizdat Status


From: Dmitry Borodaenko
Subject: Samizdat Status
Date: Sat, 2 Sep 2006 23:26:27 +0100

Greetings everyone,

Sorry for going quiet for such a long time, I had a lot of personal
matters to attend to recently, that's why this list hasn't seen much
traffic. The project isn't as dormant as it seems from the list
archive: last snapshot of Samizdat was uploaded to Debian/experimental
in April, and the last time I touched the code was late May. Since
then, I didn't have a chance to move the code forward, but now that
I've finally settled in Sheffield, I will be able to spend more time
on it. Consider my summer vacation over :)

The short-term plan (as in really-soon-now) is to get the package in
shape for 0.6.0 release (the code is ready, but unit tests and
documentation need to be updated), and make the Debian packaging fit
for unstable. Next step will be to make the software more modular and
easy to hack on: I will give Rails another try, if it doesn't help, I
will at least refactor the code to follow the MVC model more closely.

David, welcome to the list! The world is small indeed, can you tell us
what your project is about, or is it too early to let the world know?

Yes, I am tracking GPL3 progress, too, and I plan to use it once it's released.

Boud, inclusion of RDF feeds is not supported at the moment, but it
wouldn't be too difficult to add, Ruby has a very good RSS library.
Graphical representations -- I haven't seen any usable graphical RDF
representation so far, and the RDF library is the most complicated
part of Samizdat code, it won't be easy to tackle. Underlying Wiki
code in Samizdat is simple and flexible, but I suspect that many
user-friendly features in that code and elsewhere in the engine will
require better modularization of the code. On the other hand, the best
way to start with this modularization is to start doing things that
require it :)

--
Dmitry Borodaenko




reply via email to

[Prev in Thread] Current Thread [Next in Thread]