summaryrefslogtreecommitdiffstats
path: root/blog/2022-10-16.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-10-30 19:45:24 -0400
committerSacha Chua <sacha@sachachua.com>2022-10-30 19:45:24 -0400
commit6e09b74d54b49a9fba6e0d7d1db8fb0cdc42eec0 (patch)
treea6711b8a68388383bc153dad08f4962591abf9ae /blog/2022-10-16.md
parent9d0e956f854504e1e843bf528d46f31e78fd1f30 (diff)
downloademacsconf-wiki-6e09b74d54b49a9fba6e0d7d1db8fb0cdc42eec0.tar.xz
emacsconf-wiki-6e09b74d54b49a9fba6e0d7d1db8fb0cdc42eec0.zip
Linkify
Diffstat (limited to 'blog/2022-10-16.md')
-rw-r--r--blog/2022-10-16.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/blog/2022-10-16.md b/blog/2022-10-16.md
index 51654c48..9218244b 100644
--- a/blog/2022-10-16.md
+++ b/blog/2022-10-16.md
@@ -1,4 +1,4 @@
-[[date "2022-10-16"]]
+[[!date "2022-10-16"]]
[[!meta title="Speakers confirmed, Etherpad, watch pages, shifts]]
Hello, folks! Here's the weekly update on what's happening backstage
@@ -8,7 +8,7 @@ out with. =)
- All the speakers have confirmed that they've gotten the acceptance
e-mails. Many speakers have confirmed that the schedule works for
them after I reshuffled a few talks for better availability. I've
- posted the schedule at https://emacsconf.org/2022/talks/ . We'll
+ posted the schedule at <https://emacsconf.org/2022/talks/> . We'll
announce the schedule on the emacsconf-discuss mailing, Reddit, and
various places this week.
@@ -18,12 +18,12 @@ out with. =)
can submit their videos.
- I created some watch pages to support viewing different tracks:
- https://emacsconf.org/2022/watch/ . The livestreams won't work yet
+ <https://emacsconf.org/2022/watch/> . The livestreams won't work yet
and it would be nice to figure out something that can dynamically
display info for recent/current/upcoming talks, but it's a start.
- We set up a self-hosted Etherpad (ex:
- https://pad.emacsconf.org/2022-journalism) with an easy way to
+ <https://pad.emacsconf.org/2022-journalism>) with an easy way to
redirect to using Wikimedia in case we run into scaling issues. I've
added it to our Ansible playbook
(git@git.emacsconf.org:pub/emacsconf-ansible) and I'm looking