From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PhD Thesis in ConTeXt
Date: Wed, 22 Oct 2008 17:25:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0810221700050.7635@nqv-yncgbc> (raw)
In-Reply-To: <200810222252.38277.alan.braslau@cea.fr>
On Wed, 22 Oct 2008, Alan BRASLAU wrote:
> My question to the mailing list: is this task structured? Is this being
> managed by anyone?
Unfortunately, not. Taco started working on the documentation and spent
more than a month rewriting the font documentation. Most of the old manual
is now under svn with a open documentation license, so anyone can
contribute. See http://foundry.supelec.fr/projects/contextman/ for
details. But, Taco is busy with luatex, and no one else has contributed
much (note to self: look at the documentation again).
I had decided to work on the wiki, but only thing that I have done so far
is reorganize the front page. I have been thinking about working on the
installation page, but ... (insert favorite excuse)
> Perhaps this was discussed at the User Meeting last August. I would have liked
> to participate (had I been available)...
It was discussed extensively. From what I understood, the conclusion was
that someone from the community needs to take the initiative to *maintain*
the manuals. Take the big manual for example. It is fairly complete, but
some of the documentation is outdated (e.g., it recommends
\setupindenting[big] instead of \setupindenting[big,yes], there are a few
more options that have been added to itemize, descriptions, enumerations,
etc.). So, in most cases, only minor corrections are needed to bring it up
to date.
We need someone to go through the manual, point out which parts are not
clear and check if all the commands work as presented. And try to correct
things if possible, or ask on the mailing list for someone else to correct
certain sections. Someone needs to manage the whole process. Hans and Taco
do not have the time to maintain the documentation. So far, no one has
taken this responsibility. One does not have to be a context expert to do
this. Just be able to devote some time to the documentation every other
week or so.
I feel that one area where context documentation is lacking is that most
of the documentation is by Hans. In Latex, there are many introductory
documentations by different authors. This is useful, because everyone has
a different style of presentation, and different users may find some
styles easier to understand than others. Right now, if someone does not
like Hans's style of writing, he/she is stuck. We need more people to
write about ConTeXt.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-22 21:25 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 17:56 Piotr
2008-10-21 18:58 ` Jeff Smith
2008-10-21 19:35 ` Henning Hraban Ramm
2008-10-21 20:32 ` Diego Depaoli
2008-10-21 22:46 ` Marcin Borkowski
2008-10-22 5:31 ` emacs (was: Re: PhD Thesis in ConTeXt) Peter Münster
2008-10-22 6:18 ` Marcin Borkowski
2008-10-22 10:50 ` emacs Gour
2008-10-23 21:08 ` emacs Peter Münster
2008-10-23 22:46 ` emacs Marcin Borkowski
2009-02-05 15:06 ` emacs Peter Münster
2009-02-05 15:19 ` emacs luigi scarso
2009-02-05 19:15 ` emacs Peter Münster
2009-02-11 15:35 ` local footnotes Albrecht Kauffmann
2009-02-13 14:44 ` Thomas Floeren
2009-02-20 8:17 ` Albrecht Kauffmann
2009-02-20 10:28 ` Thomas Floeren
2009-02-24 7:37 ` Albrecht Kauffmann
2009-02-26 19:28 ` rulethickness in columns Albrecht Kauffmann
2009-03-01 18:26 ` Mojca Miklavec
2009-03-01 18:45 ` Hans Hagen
2009-03-02 10:19 ` Wolfgang Schuster
2009-03-02 10:41 ` Hans Hagen
2009-03-03 1:25 ` Wolfgang Schuster
2009-03-03 18:04 ` Wolfgang Schuster
2009-03-03 18:26 ` Hans Hagen
2009-03-03 18:44 ` Wolfgang Schuster
2009-03-03 18:29 ` Hans Hagen
2009-03-03 18:50 ` Wolfgang Schuster
2009-03-02 14:31 ` Mojca Miklavec
2009-03-02 14:58 ` Peter Rolf
2008-10-22 1:24 ` PhD Thesis in ConTeXt Mojca Miklavec
2008-10-22 3:10 ` Aditya Mahajan
2008-10-22 5:41 ` Alan BRASLAU
2008-10-28 1:29 ` Mohamed Bana
2008-10-28 15:20 ` Aditya Mahajan
2008-10-22 7:13 ` Stephen A. Tjemkes
2008-10-22 8:18 ` Steffen Wolfrum
2008-10-22 12:45 ` John Devereux
2008-10-22 18:53 ` Peter Münster
2008-10-22 20:52 ` Alan BRASLAU
2008-10-22 21:25 ` Aditya Mahajan [this message]
2008-10-23 14:37 ` Taco Hoekwater
2008-10-23 14:54 ` John Devereux
2008-10-23 15:38 ` Documentation (Re: PhD Thesis in ConTeXt) Taco Hoekwater
2008-10-23 18:09 ` Rory Molinari
2008-10-23 22:30 ` Marcin Borkowski
2008-10-24 7:18 ` luigi scarso
2008-10-23 21:27 ` documentation, was PhD Thesis in ConTeXt Alan BRASLAU
2008-10-23 22:21 ` Marcin Borkowski
2008-10-22 13:05 Piotr
2008-10-22 13:43 ` Marcin Borkowski
2008-10-23 17:34 ` Jeff Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.00.0810221700050.7635@nqv-yncgbc \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).