From: Jonas Baggett <jonas17b@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Wed, 12 Oct 2016 13:30:04 +0200 [thread overview]
Message-ID: <16f1eb17-4c1e-b1fc-323c-51d381306de6@gmail.com> (raw)
In-Reply-To: <24923648-13b2-ccb0-146e-47183a22a43a@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1033 bytes --]
Le 10. 10. 16 à 09:24, Hans Hagen a écrit :
> This will only work when someone takes the lead. If you do that you
> then others will help you. If you need something special on the wiki,
> just discuss it with Taco and Mojca who deal with the technicalities.
Yes that would be great to have a page on the wiki. Then I could
describe there the goals of the project and elaborate and put there the
specifications of the project. Then waiting for some feed-back in order
to improve the ideas behind the project. When the specifications are
mature enough, the technological choices could be made and finally I
will be able to put there a roadmap. At which point it would be easier
to know what needs to be done and how much time investment will be
needed, and what are the tasks I can reasonably do for the project and
what are those where help is welcome. Hopefully there would be other
people at that point who could share the vision and are willing to help.
How do you think about that ?
Have a nice afternoon,
Jonas
[-- Attachment #1.2: Type: text/html, Size: 1508 bytes --]
[-- Attachment #2: Type: text/plain, Size: 489 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-12 11:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 11:18 Jonas Baggett
2016-10-09 13:49 ` Yi Qingliang
2016-10-10 5:21 ` Jonas Baggett
2016-10-09 19:31 ` Henri Menke
2016-10-09 22:49 ` Jonas Baggett
2016-10-10 7:35 ` Hans Hagen
2016-10-11 21:36 ` Jonas Baggett
2016-10-09 20:51 ` Wolfgang Schuster
2016-10-10 5:43 ` Jonas Baggett
2016-10-10 7:24 ` Hans Hagen
2016-10-11 21:05 ` Jonas Baggett
2016-10-12 11:30 ` Jonas Baggett [this message]
2016-10-12 15:29 ` Yi Qingliang
2016-10-12 15:33 ` Mica Semrick
2016-10-12 17:32 ` Jonas Baggett
2016-10-12 17:45 ` Bomber K.
2016-10-12 17:55 ` Bomber K.
2016-10-10 7:57 ` Thomas A. Schmitz
2016-10-10 17:04 ` Jean-Pierre Delange
2016-10-10 17:34 ` Hans Hagen
2016-10-10 21:41 ` Henning Hraban Ramm
2016-10-11 5:20 ` Jean-Pierre Delange
2016-10-12 21:18 ` Jonas Baggett
2016-10-12 10:17 ` Jonas Baggett
2016-10-10 5:32 ` Aditya Mahajan
2016-10-10 5:43 ` Aditya Mahajan
2016-10-11 20:26 ` Jonas Baggett
2016-10-11 20:40 ` Henning Hraban Ramm
2016-10-12 21:27 ` Jonas Baggett
2016-10-13 8:15 ` Henning Hraban Ramm
2016-10-13 9:23 ` Aditya Mahajan
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=16f1eb17-4c1e-b1fc-323c-51d381306de6@gmail.com \
--to=jonas17b@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).