From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Looking for wiki master(s)
Date: Wed, 28 Sep 2016 17:41:00 +0200 [thread overview]
Message-ID: <CALBOmsZTP5W64zJ=5hurVJb1ycRanu_w288c4DZcKGG7C9jBMg@mail.gmail.com> (raw)
Hi,
While discussing the state of the wiki during the ConTeXt conference,
we came up with proposal to find a person (or a small group of people)
whose task would be to:
- extract the list of all existing wiki pages (you can get help with that)
- group them in reasonable blocks (fonts, graphics, installation, ...)
- push/remind the community to look into individual blocks at scheduled times
We could for example have special "focus weeks" such as "installation
week" where a list of all pages related to installation would be
posted on the mailing list with the goal to clean those chapters up or
to write the missing content. We need someone who will post reminders
and push people.
It would also be very helpful to have someone who would come up with a
list of missing topics and some proposals to restructure and better
organize the pages.
(We realized that it might be easy to find people to go over one
single page at a time, but no one has stepped forward to actively
organize this work.)
Looking forward to hear from new volunteers,
Mojca (in the name of the brainstorming group at the ConTeXt meeting)
___________________________________________________________________________________
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 reply other threads:[~2016-09-28 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 15:41 Mojca Miklavec [this message]
2016-09-29 18:25 Jan Willem Flamma
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='CALBOmsZTP5W64zJ=5hurVJb1ycRanu_w288c4DZcKGG7C9jBMg@mail.gmail.com' \
--to=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).