ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Russ Urquhart <russurquhart1@verizon.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: State of documentation of ConTeXt?
Date: Wed, 16 Jul 2014 08:08:19 -0700	[thread overview]
Message-ID: <10F9DF4D-0F47-41D7-9433-3BFD50FB4641@verizon.net> (raw)
In-Reply-To: <20140716141427.6fd97741@iram-ha-003840.extra.cea.fr>

I have been a tech writer for more than 25 years. I have been using and learning Context for the last few years. I would agree with everyone in thanking Hans and everyone else for this great product and it's support. It's been mentioned that the source is available to view. Is it possible that, given some standard of commenting with the code , a tool like Doxygen could be used to compile a reference guide of sorts?
My dream would be to be able to work on a Context documentation effort. 

Russ

Sent from my iPhone

> On Jul 16, 2014, at 5:14 AM, Alan BRASLAU <alan.braslau@cea.fr> wrote:
> 
> Ah, the great documentation project!
> 
> The problem concerning writing documentation is that it must be done by
> someone who knows ConTeXt well enough to know what to say or else know
> where to look or ask about subjects that are less well known to him or
> her. Many attempts at "improving" the documentation have been started.
> 
> Anyone is free to write a book, but is there enough of a market to make
> it commercially viable? Yet a good book can also be a key to the
> success of any system.
> 
> As Hans wrote earlier, one possibility is to fund a documentation
> project that would allow someone to devote the necessary time to
> achieve this (as well as to allow a few key developers to take the time
> necessary to assist in this project, as Mojca suggests). We would need
> to identify who could fund such a project as well as who could be
> qualified to carry it through.
> 
> Right now, the community (and in particular Hans) is doing a pretty
> good job of providing resources "in our spare time".
> 
> Alan
> 
> 
> On Tue, 15 Jul 2014 16:42:25 +0200
> Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
> 
>>> 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
___________________________________________________________________________________
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-16 15:08 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 [this message]
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=10F9DF4D-0F47-41D7-9433-3BFD50FB4641@verizon.net \
    --to=russurquhart1@verizon.net \
    --cc=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).