From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: State of documentation of ConTeXt?
Date: Tue, 15 Jul 2014 22:23:31 +0200 [thread overview]
Message-ID: <53C58DC3.8080103@wxs.nl> (raw)
In-Reply-To: <BEDB53B0-6F56-476C-8548-CDEFF63173A0@rna.nl>
On 7/15/2014 11:59 AM, Gerben Wierda wrote:
> On 14 Jul 2014, at 19:29, Hans Hagen <pragma@wxs.nl
> <mailto:pragma@wxs.nl>> wrote:
>
>> quite some sub-systems are described in their own manuals (fonts,
>> tables, xml, ...) and these manuals are quite up to date (and easier
>> to maintain than one big fat manual
>>
>> also, additional documentation is something that users need to
>> participate in (just pick a topic)
>>
>> even if it has high priority, that doesn't mean that those involved
>> have much free time left to do that next to their regular work (as
>> usual most development is done in spare time)
>>
>> so, patience is needed,
>
> 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.
>
> BTW, you can’t be serious asking the /users/ to provide the
> documentation, can you?
Well, you need to keep this in mind:
- we are using it ourselves (already for a long time) so we depend on it
and so we keep it going
- we spend most of our company time on development and support .. and we
live with that
- our roadmap does *not* include getting big (with open source as
stepping stone), *not* messing with users by selling ourselves after a
while, and *not* splitting between 'context for users' and 'context
professional or enterprise', so everyone gets what we have (which also
means that documentation will always be behind!)
- we have no big projects that pay for development (from which we can
then work on documentation) .. in fact, our projects are rather niche
and special
- we're quite satisfied with the users (they are demanding and creative)
... context never aimed at one-time-users
Now, we don't ask users to provide documentation, but on the other hand,
if you look at latex, lost of documentation starts at users.
Maybe some day I find more time ...
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-07-15 20:23 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
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 [this message]
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=53C58DC3.8080103@wxs.nl \
--to=pragma@wxs.nl \
--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).