ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: <ntg-context@ntg.nl>
Subject: Re: documentation sprint at 10th ConTeXt meeting
Date: Mon, 25 Jan 2016 10:20:25 -0700	[thread overview]
Message-ID: <20160125102025.7c31d968@cea.fr> (raw)
In-Reply-To: <56A650D9.5030600@wxs.nl>

On Mon, 25 Jan 2016 17:44:09 +0100
Hans Hagen <pragma@wxs.nl> wrote:

> > I would like to propose a documentation sprint at the meeting in
> > Kalenberg this fall to improve the situation.  
> 
> sure, just mail an abstract to Alan (who chairs the prog committee)

Documentation is an ongoing project... we discuss this regularly at the
ConTeXt users meetings and make great resolutions about completing and
updating it all. As Hans and Wolfgang point out, quite a lot of
documentation is available on the Pragma website and more and more
documentation is being included in the distribution. There are ongoing
efforts to update older documents and new documents are being written.

We will definitely discuss this some more at the next meeting.

Alan
___________________________________________________________________________________
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:[~2016-01-25 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 14:44 Jan U. Hasecke
2016-01-25 14:55 ` Wolfgang Schuster
2016-01-25 15:17   ` Jan U. Hasecke
2016-01-25 16:44 ` Hans Hagen
2016-01-25 17:20   ` Alan BRASLAU [this message]
2016-01-25 18:36     ` Jan U. Hasecke

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=20160125102025.7c31d968@cea.fr \
    --to=alan.braslau@cea.fr \
    --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).