[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

Original

Like hackathons, but more inclusive. Like events, but more impactful. Designed for those without enough time.

Feedback:

• describes what is isn't, not what it is
• misses open as a core idea
• misses that it's for action
• feels powerful and good.
• okay in the near-term

Ideas to address:

• action for open (at start / end)
• open for action (at start / end)

Current

Action for Open. Like hackathons, but more inclusive. Like events, but more impactful. Designed for those without enough time.

Feedback:

• not sure I cracked it

cc @rchampieux / @nshockey / @Daniel-Mietchen

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

First example includes:

• upload-a-thon
• book digitization

I want to keep the git landing page as friendly & organised as possible to hiding index et al in /docs would be helpful!

Great idea from April Clyburne-Sherin.

I think little discrete events where people can actually accomplish something concrete would keep people engaged. I was imaging it as a do-one-thing event - so people would leave with a sense of accomplishment.

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

[//]: # "=======================
Instructions for posting issues:
(1) Review what is already there. Perhaps a comment to an existing issue would be more appropriate than opening a new one? Issues can be a topic idea, a cry for help, an introduction to yourself, a to-do, or a discussion / question about the event itself.
(2) Write your post below the "==" line at the bottom of this text blob using Markdown (as per https://guides.github.com/features/mastering-markdown/ ) or just plain text.
(3) Don't worry about these introductory lines - you can leave or delete them, as they won't display anyway (you can check this via Preview).
(4) Hit the 'Submit new issue' button.
============================"

I've started saying doathon, but not clear if that's better or not!

At the very least, Github needs to be played down in the communications & website.