On 26 Oct, 2005, at 4:12, Beni Cherniavsky wrote:
On Sun, 2005-10-23 at 04:33 +0200, guy keren wrote:
the current things i could be helped with are:
First, how do we work?
* Is the HTML hand-written or is it generated from something else?
What do we send patches against?
* I think working with plain text source is most convenient for
discussions & patches over mail. http://docutils.sf.net or
similar can convert it to nice HTML.
rst can be nice, but then we have to deal with version control for each
update...
* Could you put it on some public version control? It will simplify
keeping updated and managing changes.
If you do, I prefer tla <http://www.gnuarch.org/>
* Alternatively, you could answer the above two points by putting it on
a wiki. Up to you -- depends whether you like wiki style of work...
I can hack an html2wiki for the transfer; it can be converted back
when we are done if needed.
No need to convert back, read on...
* The Python-IL mediawiki is not quite hebrew-friendly at present.
Putting up a small moinmoin sounds like best approach to me.
Nir, what's your advice?
I agree.
For stuff that should be viewed as static html and printed, I think rst
is a good solution - we can use rst format IN the wiki. The final
output will be created by a tiny script that download the latests rst
source from the wiki and build the output files in various formats on
the local machine using docutils.
This will make it much simpler to contribute, and much easier to see
the changes, for example, we can get mail about each change - media
wiki does not do this for us currently.
If you want to test how it works, play here:
http://nirs.dyndns.org/fix/rst_test. To get the source:
http://nirs.dyndns.org/fix/rst_test?action=raw
Little fixes are needed in the css, like hiding the page english title
and last edited info, and setting the direction for code examples to
ltr. Also, the html produced by the rst parser is sub optimal (uses
html entities), but if we build from the rst source its does not
matter.
* Licensing: you still haven't decided, right?
Its a good time to choose a license, free as possible.
1. taking the "reference book" i wrote and finish writing it.
I can do that, or at least a big part of it (I'll raise a red flag next
week if I need help).
2. suggesting a better layout for the reference book, so it can be:
1. easily browsable on the net.
2. easy to print.
and then implementing this layout.
Layout depends on tools we work with. I can take this. Anyway it's
not
first priority.
On a wiki, we can use one page using the final file name (e.g chap-01)
for one lesson. We can use separate discussion page for discussion on
the content. Images will be uploaded to each page.
Best Regards,
Nir Soffer
