ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: juh via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: juh <juh+ntg-context@mailbox.org>
Subject: Workshop at FrOSCon
Date: Wed, 8 Jun 2022 07:18:45 +0200	[thread overview]
Message-ID: <YqAxNWfksirNJICi@odysseus> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1792 bytes --]

Dear all,

this year there will be a real life FrOSCon in Bonn Sankt Augustin at
the Fachhochschule Rhein-Sieg again.

https://www.froscon.org/cfp/cfpapers/

I am considering to submit a workshop to bootstrap people with ConTeXt,
but I am not the best one to do this. So I would like to discuss if we
as a community can do something.

There are several possibilities:

1. Developer Room
https://www.froscon.org/cfp/cfprojects/

This is a room where a project can organize their own schedule. They can
programme, give talks or workshops. I've done some of these in the
recent years together with the Zope/Plone Community, the Python
Community or Hostsharing. It was always great fun.

2. Workshop

A workshop is scheduled in the main programme of FrOSCon. Duration: 2h.
I think that this is a good schedule to bootstrap people with LMTX and
for the first hello world steps.

3. Booth

I guess that Dante will have a booth as they had the years before.

4. A talk. I am pondering if I should submit a talk about our production
at Hostsharing but typesetting does not fit nicely in the main topics of
the conference.

Deadline is 2022-06-12.

For the Developer Room we need at least three people willing to attend
the whole time at least for one day.

If anyone would help me to organize a 2h-Bootstrap Workshop for ConTeXt
I would be very happy. Due to my holidays I am only available today and
I am unsure if I will have a stable internet connection from tomorrow
on. Sorry for the late announcement.

Ciao!
juh
-- 
Autoren-Homepage: ......... http://literatur.hasecke.com
Satiren & Essays: ......... http://www.sudelbuch.de
Privater Blog: ............ http://www.hasecke.eu
Netzliteratur-Projekt: .... http://www.generationenprojekt.de



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2022-06-08  5:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  5:18 juh via ntg-context [this message]
2022-06-08  5:43 ` Henning Hraban Ramm via ntg-context
2022-06-08 13:17   ` juh+ntg-context--- via ntg-context
     [not found] <mailman.1.1654768801.20741.ntg-context@ntg.nl>
2022-06-09 11:01 ` a badin via ntg-context
2022-06-21  7:37   ` juh+ntg-context--- via ntg-context
2022-07-09 15:48     ` juh+ntg-context--- via ntg-context
2022-07-09 17:27       ` Henning Hraban Ramm via ntg-context
2022-07-09 17:49         ` Henning Hraban Ramm via ntg-context
2022-07-09 18:13           ` Hans Hagen via ntg-context
2022-07-09 19:16             ` Floris van Manen via ntg-context
2022-07-09 19:30               ` Henning Hraban Ramm via ntg-context
2022-07-09 20:31                 ` Hans Hagen via ntg-context
2022-07-10  6:36         ` Axel Kielhorn via ntg-context
2022-07-10  8:22           ` Henning Hraban Ramm via ntg-context
2022-07-10 14:43             ` Axel Kielhorn via ntg-context
2022-07-10 14:56               ` Henning Hraban Ramm via ntg-context
2022-07-10 15:02                 ` Axel Kielhorn via ntg-context
2022-07-10 10:24           ` Hans Hagen via ntg-context

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=YqAxNWfksirNJICi@odysseus \
    --to=ntg-context@ntg.nl \
    --cc=juh+ntg-context@mailbox.org \
    /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).