From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: ConTeXt meeting 2023(!)
Date: Thu, 19 May 2022 09:25:04 +0200 [thread overview]
Message-ID: <8027bf19-9eb8-a618-eaf1-81b6d8db1013@fiee.net> (raw)
In-Reply-To: <EFBC60CB-06A0-412C-8401-5EE49AE1FFC9@scorecrow.com>
Am 19.05.22 um 00:22 schrieb bruce@scorecrow.com:
>
>
>> On 17 May 2022, at 07:49, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
>>
>> Would that make a difference for you?
>
> Seven days is a big time commitment, unless you are a major user of ConTeXt. Is there a possibility to split it up into "professional" during the week and "hobbyist" over the weekend so people could come for just the weekend, or the whole week?
For most of us it *is* a hobby and the meeting kind of holidays.
IMO meeting over the whole week is a big part of the appeal, otherwise
we couldn’t fit all the interesting stuff into the schedule and the
personal interaction also would fall short.
I remember we had a similar split when we combined with EuroTeX. I was
new to the community at that time, and I found the sudden influx of
people over the weekend very confusing. YMMV
It was always possible to register and come for just some days.
We discourage it, since it disturbs the community experience, pickup is
additional effort, and we often must pay the venue for the whole week
(it depends).
In 2022 the weekend would mean: maybe a talk or two on Friday, CG
members meeting on Saturday morning, excursion for the rest of the day
and nothing but departure on Sunday. In other years we met e.g. from
Sunday to Saturday, and on the first day we are busy arriving and
setting up.
BTW it looks like Jano will host us in Sibřina again in September of
2023. And we’re discussing “uncharted territory” for 2024.
Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-05-19 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 6:49 Henning Hraban Ramm via ntg-context
2022-05-18 22:42 ` Bruce Horrocks via ntg-context
[not found] ` <EFBC60CB-06A0-412C-8401-5EE49AE1FFC9@scorecrow.com>
2022-05-19 7:25 ` Henning Hraban Ramm via ntg-context [this message]
2022-05-17 18:22 Damien Thiriet 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=8027bf19-9eb8-a618-eaf1-81b6d8db1013@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).