organizing events
diff --git a/source/organize/__index.md b/source/organize/__index.md
index bd4871e..a25e09e 100644
--- a/source/organize/__index.md
+++ b/source/organize/__index.md
@@ -4,11 +4,16 @@
---
If you want to host your own Apache project event, or propose a
-[roadshow](/about/roadshow.html) about the ASF, get in touch with us on the [community
-development mailing list](/involved/mailing-lists.html).
+[roadshow](/about/roadshow.html) about the ASF, get in touch with us on the [Event Planning
+mailing list](mailto:planners@apachecon.com).
**Important!** While we appreciate other parties producing events to tell the world about
our many great Apache projects and communities, [Apache trademarks and brands](https://whimsy.apache.org/brand/list)
are also important to us. To use any Apache trademarks in conjunctions with events,
you **must** request permission by following the
[Third Party Event Branding Policy](https://www.apache.org/foundation/marks/events.html).
+
+ * [Organizing a Roadshow event](roadshow)
+ * [Running an event on Apache's online events platform](online)
+
+
diff --git a/source/organize/online.md b/source/organize/online.md
new file mode 100644
index 0000000..4c53abf
--- /dev/null
+++ b/source/organize/online.md
@@ -0,0 +1,29 @@
+---
+title: Running an online Apache event
+---
+
+If you want to run your community event on Apache's online events
+platform, here's what you need to know.
+
+ * Contact us at planners@apachecon.com to begin talking about your
+ event.
+ * We have an account on the [Hopin platform](https://hopin.com/)
+ * Hosted events must be aproved by one or more Apache project PMCs.
+ Provide a pointer to the discussion on your PMC mailing list for
+ verification.
+ * Events can be as long as 72 hours. There's no limit on the number of
+ tracks or sessions you can run during that time.
+ * Please provide an estimated number of attendees. While we know this
+ can be very hard to estimate, getting some idea of how many attendees
+ you'll have helps us with budget, since we pay per seat.
+ * You will need to identify an event chair, who will be the primary
+ contact person for communicating with the Conferences Committee. This
+ helps to avoid miscommunication and contradictory decisions.
+ * Your event chair must subscribe to the planners@apachecon.com mailing
+ list for the duration of event planning, so that you can be informed
+ about updates to policy, platform, and so on. Any questions you have
+ about any aspect of the online events process should be asked there.
+ This ensures that your question will be seen by more than one person.
+ It also ensures that the answers are archived and available to other
+ communities who are trying to solve the same problems.
+
diff --git a/source/organize/roadshow.md b/source/organize/roadshow.md
index 8815cbd..5d7e227 100644
--- a/source/organize/roadshow.md
+++ b/source/organize/roadshow.md
@@ -26,5 +26,6 @@
To run a roadshow or other small event without ASF budget, you only need to:
* Follow our branding guidelines - https://www.apache.org/foundation/marks/events
-* Tell us about it
+* [Tell us about it](mailto:planners@apachecon.com)
* Have an Apache member involved in the planning
+