ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: State of documentation of ConTeXt?
Date: Tue, 15 Jul 2014 16:42:25 +0200	[thread overview]
Message-ID: <CALBOmsbeNYnRTFVzT58f=GERcjpLgXcG=GX6wmSn=VZ6xZarzQ@mail.gmail.com> (raw)
In-Reply-To: <BEDB53B0-6F56-476C-8548-CDEFF63173A0@rna.nl>

On Tue, Jul 15, 2014 at 11:59 AM, Gerben Wierda wrote:
>
> I like ConTeXt (still do, I liked its approach when I first encountered it).
> But the project is more the ongoing private tinkering of a small in-crowd
> (that communicates with some followers).
>
> ConTeXt is managed a bit like a small group of researchers sharing a couple
> of complex and undocumented models/programs and tinkering with them as they
> go along. It’s an activity without formal design, but with a lot of
> trial-and-error/testing.
>
> Given that status (and the fact that it has had that status for over a
> decennium), I don’t expect it to ever become a serious product that is
> (semi-)professionally managed. I prefer content over management every day,
> but something like this needs some minimal management. That requires both
> time (=money) and capabilities. Besides, the tinkering researchers may not
> be inclined to do that, they want to tinker.

Basically all the development in ConTeXt is voluntarily. Pro bono.
Besides "tinkering", Hans still needs to earn some money from
somewhere. I find it amazing how much time he already spends doing
good things for the community. But he's not omnipotent.

If there is interest from some commercial company to fund the project
enough to allow some people to work full-time on documentation
(including paying Hans to allow him to spend more time on the
project), I'm sure that it could be done.

> BTW, you can’t be serious asking the users to provide the documentation, can
> you?

There are many excellent books out there written by "writers", not the
authors of software.

(I didn't even get a manual for Windows or OS X where the companies
make big money. Certain things or tricks can only be done when hackers
find a way to do X without anyone documenting feature X. And the last
phone I bought also came without any documentation whatsoever.)

There are more than enough *users* of ConTeXt capable of coming up
with proper documentation (depending on the definition of user of
course, but one could count Taco and Wolfgang as users and they are
certainly not the only ones knowing ConTeXt from inside out). But
there's of course always a question of motivation (combined with time
and money of course).

ConTeXt comes with full source code, so users can easily study the
source code. The project could easily employ two people to work full
time just to keep up with the pace of development (once they would
catch up). Ohloh estimates that it took more than 300 person-years to
write the source code for example ;) Sure, the estimate is problematic
because ConTeXt includes the complete Unicode as well as all
hyphenation patterns which simply count as lines. But it's still an
enormous project.

Oven once you remove the hyphenation patterns and char-def.lua, there
are still 36 MB remaining. The pgf project has a 1200 page manual for
less that 5 MB of source code. LaTeX has a gazillion of manuals and if
you don't know what package you should be looking for, it's not really
helping.

I agree that it would be awesome if there was complete documentation
available + maybe three manuals/tutorials from beginner to master, but
you cannot expect it from Hans to do all the work on his own.

Mojca
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2014-07-15 14:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 12:18 Gerben Wierda
2014-07-14 13:03 ` Rob Heusdens
2014-07-14 17:29   ` Hans Hagen
2014-07-15  9:59     ` Gerben Wierda
2014-07-15 14:42       ` Mojca Miklavec [this message]
2014-07-16 11:24         ` Rob Heusdens
2014-07-16 12:14         ` Alan BRASLAU
2014-07-16 15:08           ` Russ Urquhart
2014-07-16 15:20             ` Hans Hagen
2014-07-16 15:23               ` luigi scarso
2014-07-17 16:28             ` Mica Semrick
2014-07-15 14:55       ` luigi scarso
2014-07-15 15:33         ` Yuri Teixeira
2014-07-15 20:08           ` Hans Hagen
2014-07-15 20:23       ` Hans Hagen
2014-07-15 22:26       ` David Wooten
2014-07-15 22:54         ` Hans Hagen
2014-07-15 23:10           ` David Wooten
2014-07-16  6:30           ` Gour
2014-07-20 12:14         ` Gerben Wierda
2014-07-20 14:55           ` Gerben Wierda
2014-07-20 20:24           ` Mojca Miklavec
2014-07-20 21:07             ` Gerben Wierda
2014-07-21  3:07               ` Henning Hraban Ramm
2014-07-23 12:36               ` Ulrike Fischer

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='CALBOmsbeNYnRTFVzT58f=GERcjpLgXcG=GX6wmSn=VZ6xZarzQ@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.com \
    --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).