From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Tue, 11 Oct 2016 22:40:44 +0200 [thread overview]
Message-ID: <56B2F3D7-B4B9-4E6E-A58A-573C5991336A@fiee.net> (raw)
In-Reply-To: <aee6dd2c-4578-7188-fab2-a4a2653024da@tranquille.ch>
Am 2016-10-11 um 22:26 schrieb Jonas Baggett <jonasb@tranquille.ch>:
>> http://meta.stackoverflow.com/questions/328667/new-tags-and-documentation-beta
>
> And a ConTeXt tag must already exist on Stack Overflow, which I didn't find. So it seems we can wait a while before there would be examples in ConTeXt.
There are ConTeXt threads on tex.stackexchange.com
> I find stackoverflow too elitist, once I was reading a question and I wanted to help with an answer but it wasn't possible to do because it was the first time I wanted to contribute in stackoverflow and of course I was lacking the needed reputation. I am interested to help when I see an occasion to and when I am in the mood for that ;-). So I found that frustrating and it didn't make me interested to contribute there.
>
> On the other hand, I understand their will to have good quality questions and answer and I appreciate that. I am just feeling it must be a better way to do that.
Hm, in my experience you get the necessary basic permissions really soon.
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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-11 20:40 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
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 [this message]
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=56B2F3D7-B4B9-4E6E-A58A-573C5991336A@fiee.net \
--to=texml@fiee.net \
--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).