posting pdf's on the wiki would create an extra barrier to people, and
counter to the aim of making quick adaptions/growing the specification. Lat=
is nice, but again an extra barrier. CVS is nice to see how things
doesn't wiki enable the same?
In stead of complaining, let me be constructive.
What is needed is a wiki entry for every report in my view.
I would suggest the following, I'll try to start making pages in the wiki, =
convert the odt to html text in the wiki.
Like this several people can collaborate. Also the one's who did not instal=
tetex. Your help would be most appreciated however. Once the wiki is set up
(which on modem could take long), viewing and editing from a slow modem
connection should not be too much work. Especially as much of this could be
done offline (Press edit button on the wiki, and copy the text locally, whe=
I would suggest that I now set up the basic wiki, and convert the ODT files=
that. Future specifications can then be divided between us, depending on
whether your computer can handle it or not.
The wiki can also group requested reports, user made reports, no longer
supported reports, ...
If anyone has reasons to object to this, raise your voice.
PS: if you have slow connection you can ask to have ubuntu shipped to you f=
free: https://shipit.ubuntu.com/ I have this running on 733Mhz Pentium III'=
for the children, and it's fine. You do need minimum 256Mb mem, but that is
cheap to buy in a specialized shop (watch out to buy the correct one,
old one to shop for comparing).
Alternitively, you can buy a linux magazine, like eg linuxformat
(www.linuxformat.co.uk) which pack a dvd with several distributions on it w=
Quoting Stefan Bj=F6rk <stefan.bjork@...>:
>> We have some contributed report specifications now
>> (from Don, Stefan, and J=E9r=F4me). As there's more than
>> one, we could really use some organizational help.
>> It would probably make sense to maintain the specs
>> some place where everybody can see them, correct
>> typos, add requirements, etc.
>> Should we do it on our wiki? Would anybody like
>> to step up and maintain that? The effort would
>> involve updating the specifications as they
>> evolve, and bringing the new specs to everybody's
>> attention so that the people can discuss them.
> This is the task I ment I could help you with, although I have some
> problems (no fast internet connection and quite old Linux).
> My proposal is to use LaTeX for the source of the specifications, and
> PDF versions are posted to the Wiki. If I may use SVN for the sources,
> we can easily keep track on changes; otherwise, I will use my own CVS
> If this is ok, just send me the specifications so far (not in ODT; SXW,
> DOC, plain text or anything else goes), and I'll convert them to LaTeX,
> add version numbers and post them to the Wiki (or wherever you want them
This message was sent using IMP, the Internet Messaging Program.