From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: meeting, journal etc. (was: midi)
Date: Thu, 4 Feb 2021 14:39:57 +0100 [thread overview]
Message-ID: <1EE8F0EF-2B5C-40C5-A397-003DEE55A3E7@fiee.net> (raw)
In-Reply-To: <1BC6B32D-E9A1-479F-8C22-DE2636C0C104@gmail.com>
> Am 04.02.2021 um 04:25 schrieb Fabrice L <fabrice.alpha@gmail.com>:
>>> Thanks ! Yes, I can do and article with pleasure. Just give me more indications about the level (perhaps some examples) and length of the paper.
>>
>> Well, the range of level and length of articles in our (ConTeXt group’s) journal is quite big.
>
> OK. Maybe I could start with an article explaining the approach to do the video, highlighting problems and solutions, and then we can discuss on this ?
That would be great. Just send it to my personal address hraban@fiee.net
>>> I would be delighted and honoured to present at a ConTeXt meeting, but they are usually in Europe and I’m in Canada, so this could be really challenging.
>>
>> I understand. This fall we’ll meet in Belgium again, and in 2022 in Germany.
>> Maybe we could include you remotely? Last time we had “online” talks by Taco – personally is better.
>
> Why not ? ;-)
We had long discussions about online participation in the meeting. The regulars like the “intimate” atmosphere, and that doesn’t work online. We don’t want to stream anything publicly, but at least allow “known” members of the community to participate remotely.
We’ll further discuss this within the CG board, I guess.
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:[~2021-02-04 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 17:09 midi Hans Hagen
2021-02-03 18:09 ` midi Henning Hraban Ramm
2021-02-03 18:39 ` midi Hans Hagen
2021-02-03 21:06 ` midi Henning Hraban Ramm
2021-02-04 13:39 ` midi Hans Åberg
2021-02-04 14:55 ` midi Mojca Miklavec
2021-02-04 15:53 ` midi Hans Hagen
2021-02-04 20:14 ` midi Henning Hraban Ramm
2021-02-03 19:00 ` midi Fabrice L
2021-02-03 20:33 ` midi Jairo A. del Rio
2021-02-03 21:04 ` midi Jano Kula
2021-02-04 0:41 ` midi Hans Hagen
2021-02-04 3:15 ` midi Fabrice L
2021-02-04 4:38 ` midi Aditya Mahajan
2021-02-04 7:42 ` midi Marco Patzer
2021-02-04 8:21 ` midi luigi scarso
2021-02-04 13:31 ` midi Henning Hraban Ramm
2021-02-04 13:55 ` midi Fabrice L
2021-02-04 18:56 ` midi juh
2021-02-03 20:50 ` midi Henning Hraban Ramm
2021-02-03 21:14 ` midi Fabrice L
2021-02-03 21:29 ` midi Henning Hraban Ramm
2021-02-04 3:25 ` midi Fabrice L
2021-02-04 13:39 ` Henning Hraban Ramm [this message]
2021-02-03 22:48 ` midi Jairo A. del Rio
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=1EE8F0EF-2B5C-40C5-A397-003DEE55A3E7@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).