AwesomeWiki - User contributions [en]

Social Media

2019-05-07T18:17:15Z

Dough: Revised what the page is

Many chapters have a social media presence. Being on Facebook, Twitter, and Instagram helps you get the word out about your chapter, drum up interest in current projects, and attract new applications.

=== Strategies ===

Here are some thoughts on social media

=== Account list ===

Here is a list of accounts

Social Media

2019-05-07T18:16:12Z

Dough: Initial draft

== Social Media ==

Many chapters have a social media presence.

=== Strategies ===

Here are some thoughts on social media

=== Account list ===

Here is a list of accounts

Main Page

2019-05-07T18:14:15Z

Dough: Add link to social media page

{{TOC right}}

Welcome to the Awesome Foundation wiki! This is a shared repository of operational information and resources for [http://www.awesomefoundation.org Awesome Foundation] chapters.

If you are a trustee and would like an account to contribute to the wiki, please email [mailto:wiki@awesomefoundation.org wiki@awesomefoundation.org] with your desired username.

== Chapter Resources ==

* [[Chapter Resources]]
* [[Chapter Resources#Trustee Resources]]

== Communication Platforms ==

There are a number of platforms for communicating with other members of the Awesome Foundation Community. All trustees and deans are welcome to join these. Please note, your request to join will probably have to be approved by an admin so please be patient.

* [https://groups.google.com/forum/#!forum/awesome-foundation Global e-mail list (Google Group)]
* [https://www.facebook.com/groups/awesomefound/ Facebook group]
* [https://awesomefoundation.slack.com Slack]

== Design Resources and References ==
This section includes logos and other design templates as well as other guides & references to getting around in the Awesome Universe.

* [[Resources_and_References|Design Resources]]
* [[Resources_and_References#Video_Footage|Video Footage]]
* [[Social_Media|Social Media]]

== Talks and Presentations ==

Since its inception in 2009, many of our trustees have given talks about the Awesome Foundation in various venues.

* [[Talks and Presentations]]

== Global Press ==

* [[Press]]

== Global Awesome Summits ==
* [http://bit.ly/awesummit19 Awesome Summit 2019 Notes and Photos]
* [http://bit.ly/awesummit17 Awesome Summit 2017 Notes and Photos] | [[:Category:Summit 2017|Panel and Lightning Talk Recordings]]
* [[:Category:Summit 2016|Awesome Summit 2016 Notes]]
* [[:Category:Summit 2014|Awesome Summit 2014 Notes]]
* [[:Category:Summit 2013|Awesome Summit 2013 Notes]]
* [[:Category:Summit 2012|Awesome Summit 2012 Notes]]

== Using the Wiki ==
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki.

Resources and References

2017-10-18T04:40:50Z

Dough: Added Awesome Portland flyer

{{TOC right}}

== Resources and Lists ==
* [http://wiki.awesomestudies.org/images/9/92/Awesome_Foundation_New_Chapter_Handbook.pdf New Chapter Handbook]
* [http://wiki.awesomestudies.org/images/1/12/Awesome_Foundation_Manual_de_orientacion_para_capitulos_nuevos.pdf Manual de orientación para capítulos nuevos]
* [[Resources for Awesome Fellows]]
* [https://docs.google.com/document/d/1-KuQZlQTlNsrm3QXRvTZ4dq_5kjxEeaHoBUl5Yxcw9I/edit?usp=sharing Trustee Handbook Template]
* [https://docs.google.com/document/d/1DiMllJQxR2OZK6sPynh9dSgBmIhwnGfOOChCm6ofqvI/edit Trustee Voting Guide] how to use the AF site to vote on projects
* [https://docs.google.com/presentation/d/1SPMNibLqjgPP48csc_b9MWvEa9jMs8BbeNAbWuI66kQ/edit?usp=sharing Global Inspirational Projects List]

== Technical References ==

* [[Website Manual]]
* [[Localization Guide]] - How to translate the website into different languages!

== Talks and Videos About Awesome Foundation ==

* November 2016 - [https://www.youtube.com/watch?v=dMzyIUHQLTk Awesome Newcastle video]
* September 2014 - Tim Hwang (San Francisco), Emily Daniels (Ottawa), and Ana Luisa Santos (Rio de Janeiro) [http://soundcloud.com/awesomeottawa/cbcawesummit on CBC Radio], in Ottawa, ahead of Awesome Summit 2014 (10 minutes).
* September 2013 - Nikki Lee and Rachel Popkin (Awesome Seattle) at Schoolhouse Craft. (~15 min, no video). Slide deck [https://db.tt/uHvWus0p here].
* February 2013 - Ellen Chisa and Nikki Lee (Awesome Seattle) at [https://vimeo.com/59261997 Creative Mornings Seattle] (17 minutes + Q&A). Download their slide deck here: [[File:Seattle Creative Mornings - The Awesome Foundation.pptx]].
* January 2013 - Rachel Popkin and Abe Passaglia (Awesome Seattle) at HUB Social Giving Night. (>5 min, no video). Slide deck: [[FIle:AFSEA_presentation_at_HUB_1_16_13.pptx.zip‎]].
* October 2012 - Gabriel Platt's (Awesome Nurenberg) Ignite Talk. [[:File:20141009_AwesomeFoundation_Webmontag_gp.ppt|Slide Deck]], [https://www.slideshare.net/gabrielplatt/20121004-awesome-foundationignitegp Slideshare]
* September 2012 - Christina Xu (IHAS/Awesome Boston) at FEAST. Annotated slide deck [https://www.dropbox.com/s/iqbqrq4iss1iiia/Feast.ppt here].
* June 2011 - Christina Xu (IHAS/Awesome Boston) at [http://www.youtube.com/watch?v=WThSnniic2s TEDxBoston]. A later version of the talk's slides [https://www.dropbox.com/s/3uw6201llzik7wk/PublicEd%20Shortened.key are here] (9 minutes)
* April 2010 (old school!) - Tim Hwang (IHAS/Awesome San Francisco) at [http://www.youtube.com/watch?v=ZOq8gAGrmDM Ignite Boston]. (5 minutes)

== Design References ==

===Font===
* We generally use Futura as our font but feel free to use whatever you'd like!

=== Logos ===
* [http://wiki.awesomestudies.org/images/3/31/AF-logo.eps EPS Awesome Foundation Logo]
* [http://wiki.awesomestudies.org/images/4/4f/AF-logo.png PNG Awesome Foundation Logo]
* [http://wiki.awesomestudies.org/images/8/8d/AF-Calgary-square.png PNG Awesome Foundation - Calgary Logo]
* [http://wiki.awesomestudies.org/images/1/1e/Awesomefoundation.png PNG AF Favicon]
* [http://wiki.awesomestudies.org/index.php?title=File:Normal-logo-eps.eps EPS Awesome Foundation Logo with city name]
* [http://wiki.awesomestudies.org/index.php?title=File:Share-idea-logo.eps Share An Idea >> logo]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome_Tshirts_vF-DoMore.ai Do More Awesome logo]

=== Stickers ===
* AF Die Cut Stickers, Futura Font (2017) - [[:File:Af-sticker.ai|.AI File]] [[:File:1190796r.png|.PNG File]]
* [http://wiki.awesomestudies.org/images/5/53/AFStickers5.png AF Die-Cut Stickers (AweSummit 2012) - .PNG File]
* [http://wiki.awesomestudies.org/images/8/89/AF_sticker_concept.ai AF Rectangular Stickers (AweSummit 2012) - .AI File]
* [http://wiki.awesomestudies.org/images/1/19/AF_sticker_concept.png AF Rectangular Stickers (AweSummit 2012) - .PNG File]
* [http://wiki.awesomestudies.org/images/4/49/Sticker_Design_Revision2.pdf Sticker Design (AF-San Francisco) - PDF File]
* [http://wiki.awesomestudies.org/images/f/fe/AFSF-stickers.indd Sticker Design (AF-San Francisco - INDD File]

=== Postcards & Posters ===
* [http://wiki.awesomestudies.org/images/6/65/AFSF-postcard.indd Awesome Foundation Postcard Design (AF-San Francisco) - .INDD File]
* [http://wiki.awesomestudies.org/images/8/86/AFSF-postcard.pdf Awesome Foundation Postcard Design (AF-San Francisco) - .PDF File]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-5.5x8.5-Poster-w-Bleed.psd 5.5 x 8.5 poster from Antigonish that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-11x17-Poster.psd 11x17 poster that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-Vertical-Banner.psd Tall vertical conference/event 31.5" x 83.3" banner that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome_Ottawa_poster.ai "Awesome idea? We want to give you $1,000 to make it happen" poster that you can modify for your chapter (for poles, walls, poster collars, etc.)]

=== Flyers ===
* [http://wiki.awesomestudies.org/images/7/7c/Awesome_Foundation_NYC_flyer_quarters_9-26-12.docx Awesome NYC mini flier - .DOCX File]
* [http://wiki.awesomestudies.org/images/b/be/Awesome_Foundation_NYC_Flyer_quarters_9-26-12.pdf Awesome NYC mini flier - .PDF File]
* [http://wiki.awesomestudies.org/images/6/61/Awesome_Foundation_NYC_flyer_9-26-12.docx Awesome NYC full-page flier - .DOCX File]
* [http://wiki.awesomestudies.org/images/6/69/Awesome_Foundation_NYC_flyer_9-26-12.pdf Awesome NYC full-page flier - .PDF File]
* [http://wiki.awesomestudies.org/images/6/66/Grant-flyers-4x6_print.pdf Awesome Portland 4x6 flier - .PDF]

=== Shirts ===
* [http://wiki.awesomestudies.org/images/d/d4/AF-Summit-Tshirt-FINAL.eps AweSummit 2012 T-Shirt Design - .EPS File]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_114434.jpg Biz cards and paper flier examples]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_163517.jpg A bunch of tshirt examples from Saturday]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_134248.jpg Awesome Foundation DC tshirts]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_160310.jpg Jeff's pursuit of Awesome tshirt]

=== Business Cards ===
* [http://wiki.awesomestudies.org/images/8/81/AwesomeFoundation_B-Cards.pdf AF Business Cards (PDF Version)]
* [http://wiki.awesomestudies.org/images/2/24/AwesomeFoundation_B-Cards.indd AF Business Cards (.indd Version)]
* [http://wiki.awesomestudies.org/images/e/ef/ANTD_Card_Both.pdf Awesome News Taskforce Business Cards (PDF version)]
* Awesome Ottawa Business Card - [http://wiki.awesomestudies.org/images/5/55/Awesome_Ottawa_business_card_front.ai front] / [http://wiki.awesomestudies.org/images/5/57/Awesome_Ottawa_business_card_back_with_type_layer.ai back] (AI version)
* Awesome Portland business card [http://wiki.awesomestudies.org/images/f/f6/00000-0_2x35_bizcard_template-awesome-portland-2016-03.psd front] / [http://wiki.awesomestudies.org/images/8/8d/00000-0_2x35_bizcard_template-awesome-portland-2016-03-BACK.psd back] (PSD)

=== Sunglasses ===
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo.png AF logo and name, 600dpi, white on transparent background]
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo_url.png AF logo and name and url, 600dpi, white on transparent background]
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo_SF_url.png AF logo and name and SF url, 600dpi, white on transparent background]
* [[Ordering_Sunglasses|How to order AF hot pink sunglasses with the above artwork from Branders.com]]

=== Giant Check ===
* [http://wiki.awesomestudies.org/images/a/a6/AwesomeCheque.zip Awesome Ottawa Giant Check 18x36" (PDF + AI + Fonts)]

=== Photos ===
* [http://wiki.awesomestudies.org/images/3/3d/Awesome_February-29-Halifax_-_credit_Applehead_Studio.jpg Gathering funds for Awesome Halifax] (please credit Applehead Studio)
* [http://wiki.awesomestudies.org/images/b/be/Awesome_February-30_-_credit_Applehead_Studio.jpg Close-up of gathering funds for Awesome Halifax] (please credit Applehead Studio)
* [http://wiki.awesomestudies.org/images/3/32/AHS3207-Halifax_-_credit_Applehead_Studio.jpg Live pitches being made to Awesome Halifax] (please credit Applehead Studio)

===Homepage World Pixel Map===
* [[File:Awesome-chapters-map.eps]]
* [[File:Awesome-foundation-wolrd.ai]]

===AF Austin Postcards and Business Cards===
The Austin chapter really liked the SF postcards and some of the previous business card designs, so we made multiple versions so we could mix and match fronts and backs using both high-quality Moo prints and less-expensive Vistaprint prints. [http://wiki.awesomestudies.org/images/e/ec/AFAustinBusinessCardsPreview.pdf Here's a PDF preview of the six card designs.] We've provided the original Illustrator files in case other chapters want to just change the chapter location and URL to get started on their own. If you don't have an artist you work with, we hired local Austin artist [http://ahernpaul.com/ Paul Ahern] to make these for us.
* AF Austin [http://wiki.awesomestudies.org/images/9/98/AFAustinBusinessCardsAIMoo1.zip Adobe Illustrator files for Moo, 1/2]
* AF Austin [http://wiki.awesomestudies.org/images/3/32/AFAustinBusinessCardsAIMoo2.zip Adobe Illustrator files for Moo, 2/2]
* AF Austin [http://wiki.awesomestudies.org/images/4/41/AFAustinBusinessCardsAIVistaprint.zip Adobe Illustrator files for Vistaprint]
* AF Austin [http://wiki.awesomestudies.org/images/4/4f/AFAustinBusinessCardsPDF.zip print-ready PDFs for both Moo and Vistaprint] (note these say Austin on them, you should edit the .ai files!)
* AF Austin [http://wiki.awesomestudies.org/images/c/c9/AFAustin12x18Poster.pdf print-ready PDF of a 12x18 poster version of the pink card] (again, this says Austin on it)

=== Institute on Higher Awesome Studies ===
* [http://wiki.awesomestudies.org/images/9/9f/IHAS_3.png IHAS Logo (Color)]
* [http://wiki.awesomestudies.org/images/c/c8/IHAS_BW.png IHAS Logo (B/W)]

=== Report Templates ===
* [http://wiki.awesomestudies.org/images/4/48/State-of-Awesome-Dec10-Rev2.indd State of the Awesome 2010 INDD File]
* [http://wiki.awesomestudies.org/images/0/03/State-of-Awesome-Dec10-Rev2.pdf State of the Awesome 2010 PDF File]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish.pptx Power point Slide Template]

=== Other Random Stuff ===
* [http://wiki.awesomestudies.org/images/6/63/Awesome_Foundation_New_Chapter_Handbook_-_March_2015.indd New Chapter Handbook layout - .INDD File]
* [http://wiki.awesomestudies.org/images/2/29/AF-tattoo.eps AF Tattoo Design - .EPS File]
* [http://wiki.awesomestudies.org/images/0/00/Seal_of_the_Dean.png Abandoned "Seal of the Dean" Design - (AF-Boston 2010)]
* [http://wiki.awesomestudies.org/images/0/0e/AF_Global_Poster.pdf.zip Global Awesome Foundation Chapters Map (AweSummit 2012) - Zipped PDF File]
* [http://wiki.awesomestudies.org/images/5/57/Awesome_Letterhead.doc Awesome Foundation Letterhead (.doc)]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-2%27x2%27-Standard-Sign.psd#file Awesome Foundation 2'x2' logo with city name sign]
* [http://wiki.awesomestudies.org/index.php?title=File:2014-12-01_What_Is_Awesome_Antigonish.docx What is Awesome Foundation poster explainer]

== Video Footage ==

* Ottawa Summit [https://drive.google.com/drive/folders/0B2ghRS_DVCZDdDZNcVo3ZHlGamc?usp=sharing Part 1] | [https://drive.google.com/drive/folders/0B5fsfGx8zcS3bHM3LUFNSUtkV3c?usp=sharing Part 2] (please credit Andrea Conte)
* [https://www.dropbox.com/sh/efjstlapfs2iydo/AADgotMyFAUYL-tKtjt9ZfN9a?dl=0&lst= Seattle Summit]

== Ongoing Projects / Teams ==

* [[ Web Team ]] - Maintaining and improving our web tools.
* [[ New Chapters Team ]] - Helping new chapters get started.

File:Grant-flyers-4x6 print.pdf

2017-10-18T04:39:40Z

Dough: Awesome Portland flyer (4x6)

Awesome Portland flyer (4x6)

Resources and References

2017-10-18T04:34:53Z

Dough: Added Awesome Portland business cards

{{TOC right}}

== Resources and Lists ==
* [http://wiki.awesomestudies.org/images/9/92/Awesome_Foundation_New_Chapter_Handbook.pdf New Chapter Handbook]
* [http://wiki.awesomestudies.org/images/1/12/Awesome_Foundation_Manual_de_orientacion_para_capitulos_nuevos.pdf Manual de orientación para capítulos nuevos]
* [[Resources for Awesome Fellows]]
* [https://docs.google.com/document/d/1-KuQZlQTlNsrm3QXRvTZ4dq_5kjxEeaHoBUl5Yxcw9I/edit?usp=sharing Trustee Handbook Template]
* [https://docs.google.com/document/d/1DiMllJQxR2OZK6sPynh9dSgBmIhwnGfOOChCm6ofqvI/edit Trustee Voting Guide] how to use the AF site to vote on projects
* [https://docs.google.com/presentation/d/1SPMNibLqjgPP48csc_b9MWvEa9jMs8BbeNAbWuI66kQ/edit?usp=sharing Global Inspirational Projects List]

== Technical References ==

* [[Website Manual]]
* [[Localization Guide]] - How to translate the website into different languages!

== Talks and Videos About Awesome Foundation ==

* November 2016 - [https://www.youtube.com/watch?v=dMzyIUHQLTk Awesome Newcastle video]
* September 2014 - Tim Hwang (San Francisco), Emily Daniels (Ottawa), and Ana Luisa Santos (Rio de Janeiro) [http://soundcloud.com/awesomeottawa/cbcawesummit on CBC Radio], in Ottawa, ahead of Awesome Summit 2014 (10 minutes).
* September 2013 - Nikki Lee and Rachel Popkin (Awesome Seattle) at Schoolhouse Craft. (~15 min, no video). Slide deck [https://db.tt/uHvWus0p here].
* February 2013 - Ellen Chisa and Nikki Lee (Awesome Seattle) at [https://vimeo.com/59261997 Creative Mornings Seattle] (17 minutes + Q&A). Download their slide deck here: [[File:Seattle Creative Mornings - The Awesome Foundation.pptx]].
* January 2013 - Rachel Popkin and Abe Passaglia (Awesome Seattle) at HUB Social Giving Night. (>5 min, no video). Slide deck: [[FIle:AFSEA_presentation_at_HUB_1_16_13.pptx.zip‎]].
* October 2012 - Gabriel Platt's (Awesome Nurenberg) Ignite Talk. [[:File:20141009_AwesomeFoundation_Webmontag_gp.ppt|Slide Deck]], [https://www.slideshare.net/gabrielplatt/20121004-awesome-foundationignitegp Slideshare]
* September 2012 - Christina Xu (IHAS/Awesome Boston) at FEAST. Annotated slide deck [https://www.dropbox.com/s/iqbqrq4iss1iiia/Feast.ppt here].
* June 2011 - Christina Xu (IHAS/Awesome Boston) at [http://www.youtube.com/watch?v=WThSnniic2s TEDxBoston]. A later version of the talk's slides [https://www.dropbox.com/s/3uw6201llzik7wk/PublicEd%20Shortened.key are here] (9 minutes)
* April 2010 (old school!) - Tim Hwang (IHAS/Awesome San Francisco) at [http://www.youtube.com/watch?v=ZOq8gAGrmDM Ignite Boston]. (5 minutes)

== Design References ==

===Font===
* We generally use Futura as our font but feel free to use whatever you'd like!

=== Logos ===
* [http://wiki.awesomestudies.org/images/3/31/AF-logo.eps EPS Awesome Foundation Logo]
* [http://wiki.awesomestudies.org/images/4/4f/AF-logo.png PNG Awesome Foundation Logo]
* [http://wiki.awesomestudies.org/images/8/8d/AF-Calgary-square.png PNG Awesome Foundation - Calgary Logo]
* [http://wiki.awesomestudies.org/images/1/1e/Awesomefoundation.png PNG AF Favicon]
* [http://wiki.awesomestudies.org/index.php?title=File:Normal-logo-eps.eps EPS Awesome Foundation Logo with city name]
* [http://wiki.awesomestudies.org/index.php?title=File:Share-idea-logo.eps Share An Idea >> logo]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome_Tshirts_vF-DoMore.ai Do More Awesome logo]

=== Stickers ===
* AF Die Cut Stickers, Futura Font (2017) - [[:File:Af-sticker.ai|.AI File]] [[:File:1190796r.png|.PNG File]]
* [http://wiki.awesomestudies.org/images/5/53/AFStickers5.png AF Die-Cut Stickers (AweSummit 2012) - .PNG File]
* [http://wiki.awesomestudies.org/images/8/89/AF_sticker_concept.ai AF Rectangular Stickers (AweSummit 2012) - .AI File]
* [http://wiki.awesomestudies.org/images/1/19/AF_sticker_concept.png AF Rectangular Stickers (AweSummit 2012) - .PNG File]
* [http://wiki.awesomestudies.org/images/4/49/Sticker_Design_Revision2.pdf Sticker Design (AF-San Francisco) - PDF File]
* [http://wiki.awesomestudies.org/images/f/fe/AFSF-stickers.indd Sticker Design (AF-San Francisco - INDD File]

=== Postcards & Posters ===
* [http://wiki.awesomestudies.org/images/6/65/AFSF-postcard.indd Awesome Foundation Postcard Design (AF-San Francisco) - .INDD File]
* [http://wiki.awesomestudies.org/images/8/86/AFSF-postcard.pdf Awesome Foundation Postcard Design (AF-San Francisco) - .PDF File]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-5.5x8.5-Poster-w-Bleed.psd 5.5 x 8.5 poster from Antigonish that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-11x17-Poster.psd 11x17 poster that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-Vertical-Banner.psd Tall vertical conference/event 31.5" x 83.3" banner that you can modify for your chapter]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome_Ottawa_poster.ai "Awesome idea? We want to give you $1,000 to make it happen" poster that you can modify for your chapter (for poles, walls, poster collars, etc.)]

=== Flyers ===
* [http://wiki.awesomestudies.org/images/7/7c/Awesome_Foundation_NYC_flyer_quarters_9-26-12.docx Awesome NYC mini flier - .DOCX File]
* [http://wiki.awesomestudies.org/images/b/be/Awesome_Foundation_NYC_Flyer_quarters_9-26-12.pdf Awesome NYC mini flier - .PDF File]
* [http://wiki.awesomestudies.org/images/6/61/Awesome_Foundation_NYC_flyer_9-26-12.docx Awesome NYC full-page flier - .DOCX File]
* [http://wiki.awesomestudies.org/images/6/69/Awesome_Foundation_NYC_flyer_9-26-12.pdf Awesome NYC full-page flier - .PDF File]

=== Shirts ===
* [http://wiki.awesomestudies.org/images/d/d4/AF-Summit-Tshirt-FINAL.eps AweSummit 2012 T-Shirt Design - .EPS File]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_114434.jpg Biz cards and paper flier examples]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_163517.jpg A bunch of tshirt examples from Saturday]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_134248.jpg Awesome Foundation DC tshirts]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_160310.jpg Jeff's pursuit of Awesome tshirt]

=== Business Cards ===
* [http://wiki.awesomestudies.org/images/8/81/AwesomeFoundation_B-Cards.pdf AF Business Cards (PDF Version)]
* [http://wiki.awesomestudies.org/images/2/24/AwesomeFoundation_B-Cards.indd AF Business Cards (.indd Version)]
* [http://wiki.awesomestudies.org/images/e/ef/ANTD_Card_Both.pdf Awesome News Taskforce Business Cards (PDF version)]
* Awesome Ottawa Business Card - [http://wiki.awesomestudies.org/images/5/55/Awesome_Ottawa_business_card_front.ai front] / [http://wiki.awesomestudies.org/images/5/57/Awesome_Ottawa_business_card_back_with_type_layer.ai back] (AI version)
* Awesome Portland business card [http://wiki.awesomestudies.org/images/f/f6/00000-0_2x35_bizcard_template-awesome-portland-2016-03.psd front] / [http://wiki.awesomestudies.org/images/8/8d/00000-0_2x35_bizcard_template-awesome-portland-2016-03-BACK.psd back] (PSD)

=== Sunglasses ===
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo.png AF logo and name, 600dpi, white on transparent background]
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo_url.png AF logo and name and url, 600dpi, white on transparent background]
* [http://wiki.awesomestudies.org/index.php?title=File:AFlogo_SF_url.png AF logo and name and SF url, 600dpi, white on transparent background]
* [[Ordering_Sunglasses|How to order AF hot pink sunglasses with the above artwork from Branders.com]]

=== Giant Check ===
* [http://wiki.awesomestudies.org/images/a/a6/AwesomeCheque.zip Awesome Ottawa Giant Check 18x36" (PDF + AI + Fonts)]

=== Photos ===
* [http://wiki.awesomestudies.org/images/3/3d/Awesome_February-29-Halifax_-_credit_Applehead_Studio.jpg Gathering funds for Awesome Halifax] (please credit Applehead Studio)
* [http://wiki.awesomestudies.org/images/b/be/Awesome_February-30_-_credit_Applehead_Studio.jpg Close-up of gathering funds for Awesome Halifax] (please credit Applehead Studio)
* [http://wiki.awesomestudies.org/images/3/32/AHS3207-Halifax_-_credit_Applehead_Studio.jpg Live pitches being made to Awesome Halifax] (please credit Applehead Studio)

===Homepage World Pixel Map===
* [[File:Awesome-chapters-map.eps]]
* [[File:Awesome-foundation-wolrd.ai]]

===AF Austin Postcards and Business Cards===
The Austin chapter really liked the SF postcards and some of the previous business card designs, so we made multiple versions so we could mix and match fronts and backs using both high-quality Moo prints and less-expensive Vistaprint prints. [http://wiki.awesomestudies.org/images/e/ec/AFAustinBusinessCardsPreview.pdf Here's a PDF preview of the six card designs.] We've provided the original Illustrator files in case other chapters want to just change the chapter location and URL to get started on their own. If you don't have an artist you work with, we hired local Austin artist [http://ahernpaul.com/ Paul Ahern] to make these for us.
* AF Austin [http://wiki.awesomestudies.org/images/9/98/AFAustinBusinessCardsAIMoo1.zip Adobe Illustrator files for Moo, 1/2]
* AF Austin [http://wiki.awesomestudies.org/images/3/32/AFAustinBusinessCardsAIMoo2.zip Adobe Illustrator files for Moo, 2/2]
* AF Austin [http://wiki.awesomestudies.org/images/4/41/AFAustinBusinessCardsAIVistaprint.zip Adobe Illustrator files for Vistaprint]
* AF Austin [http://wiki.awesomestudies.org/images/4/4f/AFAustinBusinessCardsPDF.zip print-ready PDFs for both Moo and Vistaprint] (note these say Austin on them, you should edit the .ai files!)
* AF Austin [http://wiki.awesomestudies.org/images/c/c9/AFAustin12x18Poster.pdf print-ready PDF of a 12x18 poster version of the pink card] (again, this says Austin on it)

=== Institute on Higher Awesome Studies ===
* [http://wiki.awesomestudies.org/images/9/9f/IHAS_3.png IHAS Logo (Color)]
* [http://wiki.awesomestudies.org/images/c/c8/IHAS_BW.png IHAS Logo (B/W)]

=== Report Templates ===
* [http://wiki.awesomestudies.org/images/4/48/State-of-Awesome-Dec10-Rev2.indd State of the Awesome 2010 INDD File]
* [http://wiki.awesomestudies.org/images/0/03/State-of-Awesome-Dec10-Rev2.pdf State of the Awesome 2010 PDF File]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish.pptx Power point Slide Template]

=== Other Random Stuff ===
* [http://wiki.awesomestudies.org/images/6/63/Awesome_Foundation_New_Chapter_Handbook_-_March_2015.indd New Chapter Handbook layout - .INDD File]
* [http://wiki.awesomestudies.org/images/2/29/AF-tattoo.eps AF Tattoo Design - .EPS File]
* [http://wiki.awesomestudies.org/images/0/00/Seal_of_the_Dean.png Abandoned "Seal of the Dean" Design - (AF-Boston 2010)]
* [http://wiki.awesomestudies.org/images/0/0e/AF_Global_Poster.pdf.zip Global Awesome Foundation Chapters Map (AweSummit 2012) - Zipped PDF File]
* [http://wiki.awesomestudies.org/images/5/57/Awesome_Letterhead.doc Awesome Foundation Letterhead (.doc)]
* [http://wiki.awesomestudies.org/index.php?title=File:Awesome-Antigonish-2%27x2%27-Standard-Sign.psd#file Awesome Foundation 2'x2' logo with city name sign]
* [http://wiki.awesomestudies.org/index.php?title=File:2014-12-01_What_Is_Awesome_Antigonish.docx What is Awesome Foundation poster explainer]

== Video Footage ==

* Ottawa Summit [https://drive.google.com/drive/folders/0B2ghRS_DVCZDdDZNcVo3ZHlGamc?usp=sharing Part 1] | [https://drive.google.com/drive/folders/0B5fsfGx8zcS3bHM3LUFNSUtkV3c?usp=sharing Part 2] (please credit Andrea Conte)
* [https://www.dropbox.com/sh/efjstlapfs2iydo/AADgotMyFAUYL-tKtjt9ZfN9a?dl=0&lst= Seattle Summit]

== Ongoing Projects / Teams ==

* [[ Web Team ]] - Maintaining and improving our web tools.
* [[ New Chapters Team ]] - Helping new chapters get started.

File:00000-0 2x35 bizcard template-awesome-portland-2016-03-BACK.psd

2017-10-18T04:30:51Z

Dough: Back of Awesome Portland business card

Back of Awesome Portland business card

File:00000-0 2x35 bizcard template-awesome-portland-2016-03.psd

2017-10-18T04:30:21Z

Dough: Front of Awesome Portland business card

Front of Awesome Portland business card

Working Group: How to host Awesome Summit

2016-03-17T07:49:40Z

Dough: split up text, expanded note about local businesses

== Rough Schedule ==
'''Friday'''
* Social events to organize people, also a travel day for some

'''Saturday'''
* All-day summit stuff
* Party

'''Sunday'''
* All-day summit
* Some sort of after-party

== Things you need to run a summit: ==
* Places to have events
** Main venue
** Venue for the big party, different in style and shape than
** Alternative places for other parties (as needed)
* People
** Attend
** volunteer
** (It also helps if you have a city that people want to go to)
* Early Announcement
** Travel and housing assistance (bulk of SEA budget was travel assistance)
* Food
** Breakfast
** Lunch
* Parties
* Alcohol
** Something that can be had a parties
* Swag

== Timeline ==
Helps if you start about 9 months in advance, getting funding assistance. The longer runway you have, the easier it is to get starters
Planning events long-term is essential!

=== Sponsorship ===
In all fairness, didn’t go great in Seattle

Bailouts are not a sustainable way to do business

Put together a letter talking about the summit, what the foundation is, had tiers of sponsorships

== If you want to run a summit ==
* Have a project manager and a schedule
* Have a bunch of people to do the work
* Would have been great: have somebody who could do scheduling and resource management
* Helps to know what people are good at

Every summit is a little smaller than before--first summit in Boston had 200, New York had 100, Ottawa had 50, Seattle had 67

Second time we ran the summit, extra day of external-to-Foundation partners, was a little weird because it wasn’t quite an Awesome thing, may be a backburner thing

=== Donations ===
MailChimp has historically donated money to help run the Summit

Historically it’s been local businesses as well--get their products in front of a group of people with a track record of spending money on things for no material gain

Chapters that are equipped to run a summit may not be equipped to fund a summit (Unsolved problem across multiple foundations)

=== Other options ===
Running a “New Philanthropy” conference on the side: happened for the New York Summit had that but it was problematic
* Winning the next summit
* Presentations to IHAS
What opportunities are there to NOT have it in North America?
* Or what about multiple summits for various countries? Stable established chapters are all in North America, for better or worse right now
* The travel assistance alone for Europe would be crippling

== Timeline of Summit Preparation ==
=== 9-12 months in advance===
* Hey, we’re having an event!
* (The event choosing process that we have right now doesn’t really give it enough runway: what if we announced the next two bids?)
* Start asking for money and venues, follow up weekly
* Used Proximate to get the registration site up and running
* Get trustees to add their registration to the site

=== 6 months in advance ===
* Everything nailed down
* Confirm travel assistance confirmation (Seattle had about 12 needing assistance)
* Travel and housing assistance can take many forms, some were PayPal sending of message
* Decide what kind of in-kind donations you might want

=== 3 months in advance ===
* Start working on housing assistance
* Start booking hotels in advance

=== Inside of 3 months ===
* Not planning, executing on plan
* Designs complete, printing complete, ideally weeks in advance to avoid rush fees
* Any in-kind donations done by 2 months
* If you want things from a major brand or a local brand that has been acquired by a local brand, leadtime is helpful there
* Relationship with Kind began when they wanted to send stuff to Awesome Foundation

=== Two weeks out ===
* Food for lunch
* Take advantage of Costco memberships

=== Day Zero===
Have the Summit!

=== Post-Summit ===
Recovery

== Documents to create ==
# Brands that are worth reaching out to
# Kinds of letters sent to people

== Deciding the program ==
* Decided partially because the exact same conversations happen in the same order almost every time
* Breakout sessions are the things that people normally want to talk about
* Having facilitators is helpful
* Think about making a bit more Unconference style with pre-filled boxes

== Questions / Thoughts ==
* Why are we not pulling together a super-committee of Awesome Summit folks?
* Can we reach out to designers outside of the chapters, for example?
* Not everybody has been to every conference, would be helpful for people to have some knowledge
* Documenting the experience--sometimes the stuff from the conference ends up in the New Chapters Handbook
* How do we take the gems of stuff and transfer it over to the working committees?

== Awesome Summit Audiences ==
Two audiences for Awesome Summit:
# New people who have never been to one before
#* Approach the summit with the wild optimism of Awesome
#* Meeting new people
# Old hands who have been to them before
#* Don’t need to go to the “what challenges to chapters face?” meetings because they’ve lived those questions before
#* Value is to see old friends, make new ones
#* Get tactical things done

Would be great to have some sort of way for people to make an opt-in to contact people

== Post-mortem ==
Had access to the budgets, verbal communications
But that was about it

Working Group: How to host Awesome Summit

2016-03-17T07:48:37Z

Dough: broke up blocks of text

== Rough Schedule ==
'''Friday'''
* Social events to organize people, also a travel day for some

'''Saturday'''
* All-day summit stuff
* Party

'''Sunday'''
* All-day summit
* Some sort of after-party

== Things you need to run a summit: ==
* Places to have events
** Main venue
** Venue for the big party, different in style and shape than
** Alternative places for other parties (as needed)
* People
** Attend
** volunteer
** (It also helps if you have a city that people want to go to)
* Early Announcement
** Travel and housing assistance (bulk of SEA budget was travel assistance)
* Food
** Breakfast
** Lunch
* Parties
* Alcohol
** Something that can be had a parties
* Swag

== Timeline ==
Helps if you start about 9 months in advance, getting funding assistance. The longer runway you have, the easier it is to get starters
Planning events long-term is essential!

=== Sponsorship ===
In all fairness, didn’t go great in Seattle

Bailouts are not a sustainable way to do business

Put together a letter talking about the summit, what the foundation is, had tiers of sponsorships

== If you want to run a summit ==
* Have a project manager and a schedule
* Have a bunch of people to do the work
* Would have been great: have somebody who could do scheduling and resource management
* Helps to know what people are good at

Every summit is a little smaller than before--first summit in Boston had 200, New York had 100, Ottawa had 50, Seattle had 67

Second time we ran the summit, extra day of external-to-Foundation partners, was a little weird because it wasn’t quite an Awesome thing, may be a backburner thing

=== Donations ===
MailChimp has historically donated money
Historically it’s been local businesses
Chapters that are equipped to run a summit may not be equipped to fund a summit (Unsolved problem across multiple foundations)

=== Other options ===
Running a “New Philanthropy” conference on the side: happened for the New York Summit had that but it was problematic
* Winning the next summit
* Presentations to IHAS
What opportunities are there to NOT have it in North America?
* Or what about multiple summits for various countries? Stable established chapters are all in North America, for better or worse right now
* The travel assistance alone for Europe would be crippling

== Timeline of Summit Preparation ==
=== 9-12 months in advance===
* Hey, we’re having an event!
* (The event choosing process that we have right now doesn’t really give it enough runway: what if we announced the next two bids?)
* Start asking for money and venues, follow up weekly
* Used Proximate to get the registration site up and running
* Get trustees to add their registration to the site

=== 6 months in advance ===
* Everything nailed down
* Confirm travel assistance confirmation (Seattle had about 12 needing assistance)
* Travel and housing assistance can take many forms, some were PayPal sending of message
* Decide what kind of in-kind donations you might want

=== 3 months in advance ===
* Start working on housing assistance
* Start booking hotels in advance

=== Inside of 3 months ===
* Not planning, executing on plan
* Designs complete, printing complete, ideally weeks in advance to avoid rush fees
* Any in-kind donations done by 2 months
* If you want things from a major brand or a local brand that has been acquired by a local brand, leadtime is helpful there
* Relationship with Kind began when they wanted to send stuff to Awesome Foundation

=== Two weeks out ===
* Food for lunch
* Take advantage of Costco memberships

=== Day Zero===
Have the Summit!

=== Post-Summit ===
Recovery

== Documents to create ==
# Brands that are worth reaching out to
# Kinds of letters sent to people

== Deciding the program ==
* Decided partially because the exact same conversations happen in the same order almost every time
* Breakout sessions are the things that people normally want to talk about
* Having facilitators is helpful
* Think about making a bit more Unconference style with pre-filled boxes

== Questions / Thoughts ==
* Why are we not pulling together a super-committee of Awesome Summit folks?
* Can we reach out to designers outside of the chapters, for example?
* Not everybody has been to every conference, would be helpful for people to have some knowledge
* Documenting the experience--sometimes the stuff from the conference ends up in the New Chapters Handbook
* How do we take the gems of stuff and transfer it over to the working committees?

== Awesome Summit Audiences ==
Two audiences for Awesome Summit:
# New people who have never been to one before
#* Approach the summit with the wild optimism of Awesome
#* Meeting new people
# Old hands who have been to them before
#* Don’t need to go to the “what challenges to chapters face?” meetings because they’ve lived those questions before
#* Value is to see old friends, make new ones
#* Get tactical things done

Would be great to have some sort of way for people to make an opt-in to contact people

== Post-mortem ==
Had access to the budgets, verbal communications
But that was about it

Getting more applications 2016

2016-03-17T07:46:35Z

Dough: Broke big blocks o' text into more manageable chunks

== Submission variability ==
Started off with a custom question on the application form from Seattle chapter: Who else would you suggest apply for the grant?

Some chapters have noticed a “sine wave of quality in submissions” - at the lowest point, all of them have potential, but they’re not the greatest applications. Possible solutions:
* Question: why would you think one of the trustees think this idea was awesome?
* How do we help bad presentations?
* [https://nielschrist.wordpress.com/2012/07/13/the-nabc-method-standford-research-institute-sri/ ONABC pitch tool], which teaches you how to get a grant

== Picking grants to find ==
Don’t split grants, bad things happen when people are coming in thinking it's $1000 and it only ends up being $500
Idea for giving out grant money: Bright Pink Envelopes from Amazon!

Question: do you fund grant where it's a portion of a $10K range? Not so much, if people target the grant at something specific, it seems something better
The difference between a $300 event and a $1300 event is repeatability - sometimes the money will be required to just go forward

== Different places to solicit applications ==
Some ideas:
* Alternative gathering of pitches
* Live application solicitation at a Farmer’s Market or maker faire
* Ordering drinks in a bar and having people come in, people had a hard time following up on the ideas

Question: what do chapters do to maintain relationship with previous winners
25th Pitch Night in Boston - bring projects back

Pitch party
Ottawa’s third birthday party had an amazing story about one winner turning over the prize to another applicant, which resulted in some fun media coverage

Is this worthy vs is this awesome? Ideally it’s both

On the waves of applications that go through--as word-of-mouth spreads through a group, like attracts like, so we do get waves of things
How does one expand that group?
Making tactical grants can come into play: do you make a grant with a group with the hopes of gaining more traction with them?

Try Themed Calls for Pitches:
* Food - (Kind of failed, need to find networks that will share and raise the organization message)
* Pot?
* Youth Communities
* Homeless
* Animals
* Teachers
* Transportation (who rides the bus, bikes, etc.)
* ->>>> What’s your city passionate about? What’s a hot button topic? Fund that.

== Roles for trustees ==
Residency program - Chicago chapter is looking to get more geographic representation by bringing in people from different groups to be champions of awesome, mix up the debate, vote but don’t contribute money
Media student representative as unpaid internship to handle media queries and process
PR person - how do other chapters do it?

Debating about how to help applicants reapply--how to suggest different approaches, rephrasing what's going on

Question about the number of applicants that a chapter gets
Seattle goes from 30 applications to 3 finalists
Ottawa gets more exposure when they do media - radio ads work well
Chicago talked about doing a sample application -> here’s a good one and bad one

== Advertising and merchandise ==

Advertising - billboards (Portland has had some success with partnering with [http://thejoyteam.org/ The Joy Team]),

A Seattle project - [http://rain.works rain.works] could have some potential

Liverpool chapter distributed pink envelopes with “open me” (very ‘Alice in Wonderland’) - containing 5 pounds and a letter about what the
Awesome Foundation is - distributed throughout town and asked people to tweet what they did with the money: press and media attention

Trustees: pitch ideas to each other to create and plug marketing ideas

=== Marketing pitches and resources ===
* Marketing pitches: given that we want money to go to pitches, is it weird to spend money on advertising?
* It’s OK to take a month off and take that money to be more proactive
* T-shirt sales aren’t huge, but people tend to buy
* Dropbox full of files for all sorts of ads - vertical banner with Awesome branding, “sponsored by” gets a lot of foot traffic (Add link to Awesome Wiki, too)
* Graphic design - asked students to have new logo and branding campaign

=== Flyers, flyers flyers ===
* Advertising at sporting events with flyers - created a small little park on Parking Day
* Ottawa had somebody pack in flyers in the take-home pizza boxes from a restaurant
* Stack of flyers in an Uber or Lyft car

=== Other ideas ===
* Incubator sessions of ideas / implementations on YouTube - create an idea but no time to implement them
* How does one get more into maker spaces? It’s hard to organize an event, but if one can piggyback onto an existing one (there are “so many”)
* Identify your target network and think about how to reach them
* Focus a grant on another existing event like Parking Day - Bicycle Festival
* Chicago was really successful with one group of puppeteers, so much so that “We had to put a year-long moratorium on puppeteering projects”

The idea of the “hustler trustees” - identify all the local media contacts and send to them. DC does a newsletter that’s about things that are not just about Awesome but other quirky winners as well. Portland did spend a lot of time on Facebook updates, sending notices of other projects, but there wasn't much impact on applications from it (but it was great to get the word out)

Getting more applications 2016

2016-03-17T07:42:28Z

Dough: Made list into actual list

== Submission variability ==
Started off with a custom question on the application form from Seattle chapter: Who else would you suggest apply for the grant?

Some chapters have noticed a “sine wave of quality in submissions” - at the lowest point, all of them have potential, but they’re not the greatest applications. Possible solutions:
* Question: why would you think one of the trustees think this idea was awesome?
* How do we help bad presentations?
* [https://nielschrist.wordpress.com/2012/07/13/the-nabc-method-standford-research-institute-sri/ ONABC pitch tool], which teaches you how to get a grant

== Picking grants to find ==
Don’t split grants, bad things happen when people are coming in thinking it's $1000 and it only ends up being $500
Idea for giving out grant money: Bright Pink Envelopes from Amazon!

Question: do you fund grant where it's a portion of a $10K range? Not so much, if people target the grant at something specific, it seems something better
The difference between a $300 event and a $1300 event is repeatability - sometimes the money will be required to just go forward

== Different places to solicit applications ==
Some ideas:
* Alternative gathering of pitches
* Live application solicitation at a Farmer’s Market or maker faire
* Ordering drinks in a bar and having people come in, people had a hard time following up on the ideas

Question: what do chapters do to maintain relationship with previous winners
25th Pitch Night in Boston - bring projects back

Pitch party
Ottawa’s third birthday party had an amazing story about one winner turning over the prize to another applicant, which resulted in some fun media coverage

Is this worthy vs is this awesome? Ideally it’s both

On the waves of applications that go through--as word-of-mouth spreads through a group, like attracts like, so we do get waves of things
How does one expand that group?
Making tactical grants can come into play: do you make a grant with a group with the hopes of gaining more traction with them?

Try Themed Calls for Pitches:
* Food - (Kind of failed, need to find networks that will share and raise the organization message)
* Pot?
* Youth Communities
* Homeless
* Animals
* Teachers
* Transportation (who rides the bus, bikes, etc.)
* ->>>> What’s your city passionate about? What’s a hot button topic? Fund that.

== Roles for trustees ==
Residency program - Chicago chapter is looking to get more geographic representation by bringing in people from different groups to be champions of awesome, mix up the debate, vote but don’t contribute money
Media student representative as unpaid internship to handle media queries and process
PR person - how do other chapters do it?

Debating about how to help applicants reapply--how to suggest different approaches, rephrasing what's going on

Question about the number of applicants that a chapter gets
Seattle goes from 30 applications to 3 finalists
Ottawa gets more exposure when they do media - radio ads work well
Chicago talked about doing a sample application -> here’s a good one and bad one

== Advertising and merchandise ==
Advertising - billboards (Portland has had some success with partnering with [http://thejoyteam.org/ The Joy Team]), rain.works
Liverpool chapter distributed pink envelopes with “open me” (very ‘Alice in Wonderland’) - containing 5 pounds and a letter about what the Awesome Foundation is - distributed throughout town and asked people to tweet what they did with the money: press and media attention
Trustees: pitch ideas to each other to create and plug marketing ideas

Marketing pitches: given that we want money to go to pitches, is it weird to spend money on advertising?
It’s OK to take a month off and take that money to be more proactive
T-shirt sales aren’t huge, but people tend to buy
Dropbox full of files for all sorts of ads - vertical banner with Awesome branding, “sponsored by” gets a lot of foot traffic
(Add link to Awesome Wiki, too)
Graphic design - asked students to have new logo and branding campaign

Advertising at sporting events with flyers - created a small little park on Parking Day
Ottawa had somebody pack in flyers in the take-home pizza boxes from a restaurant
Stack of flyers in an Uber or Lyft car
Incubator sessions of ideas / implementations on YouTube - create an idea but no time to implement them
How does one get more into maker spaces? It’s hard to organize an event, but if one can piggyback onto an existing one (there are “so many”)
Identify your target network and think about how to reach them
Focus a grant on another existing event like Parking Day - Bicycle Festival
Chicago was really successful with one group of puppeteers, so much so that “We had to put a year-long moratorium on puppeteering projects”

The idea of the “hustler trustees” - identify all the local media contacts and send to them. DC does a newsletter that’s about things that are not just about Awesome but other quirky winners as well.

The Future of the Institute for Higher Awesome Studies

2016-03-09T06:48:29Z

Dough: Kitten Voltron is the best

Presentation by Cristina Xu, Chancellor of IHAS

== What is an IHAS? ==
* IHAS = Institute on Higher Awesome Studies
* Experiment to develop minimal infrastructure to support Awesome Foundation without bogging it down
* Incorporated as a 503C
* Not affiliated with any chapter
* Want to enable faster and stronger growth for the foundation
* NOT: a service organization

== Past projects ==
* Designing Awesome Foundation site with Jessie Chan-Norris & web team
* Started and support Awesome Summit
* Foundation support to launch and support chapters in Detroit and New Orleans -- those chapters have now been wound down

== What’s next? ==
* When we started IHAS, goal was to get infrastructure down so we can get it to grow
* Reached the limit of Christina’s vision, definitely time for new visions

== Working session ==
* How should IHAS and AF work together or not
* What should the responsibilities of the next chancellor be? Should it even be called a chancellor?
* How should we choose the next IHAS chancellor?
* How do we make the decisions in a way that involves chapters who are not here
* “And now, Kitten Voltron” - When all the kittens (chapters) have to work together, we summon [https://s-media-cache-ak0.pinimg.com/736x/f4/1f/c8/f41fc8b144d49bdfc0b38e6e6fc4e307.jpg Kitten Voltron!]

Awesome Beyond Awesome

2016-03-09T06:44:11Z

Dough: Initial dump of notes

Presentation by Kevin F. Adler

== How to extend the awesomeness beyond the Awesome Foundation ==
Or, the short talk that will lead to a breakout session that I rewrote at 2:30 yesterday

Talking a bit about the San Francisco chapter, and their first project: [http://blog.awesomefoundation.org/2010/05/21/history-of-the-sky-wins-the-first-bay-area-awesome-grant/ History of the Sky] to take time-lapse photography of the sky

'''Thesis 1:'''
More people want to be trustees than is possible

'''Thesis 2:'''
There are more worthy projects that apply for grants than are possible

'''Thesis 3'''
What do we know? Over the past few years, we have as of right now: $1,951,000 granted, 1951 projects funded, 82 chapters, 18 countries

What can we take from all of these experiments that we can do?

All of these theses are maybe not true, so what are we left with?

== 4 questions: ==
# What projects do we fund? (orphans and flamethrowers, but maybe we need to rethink what a flamethrower really means, maybe we have to start w/ kindling)
#* (Guest mini-lecture from Caprice from Detroit about [http://www.awesomefoundation.org/en/projects/40748-caprice-connects-with-detroit Caprice Connects], her short film about connections, which led to being a trustee, which led to presenting at Sundance)
#* One project by itself can grow beyond what it originally started as
# What communities do we engage?
#* Detroit allows the community to hear the pitches, build collaboration among the public where necessary
#* His research has been on how disasters and how it engages people--people are MORE likely to connect during times of stress than less
#* The applications that come in are a gold mine of information
# Who are our trustees?
#* Old-school philanthropy is stodgy old dudes, this is not who we are
#* We need to tell our own stories as well as that of our grantees
#* New trustees team as well as a new chapters team
# How do we celebrate others?
#* Even just a word of support will help without a grant. ''We're the Awesome Foundation. And we believe in you.''

Category:Summit 2016

2016-03-09T06:29:03Z

Dough: Added notes about a couple of the Sunday talks

The 2016 Summit was held in Seattle, Washington.

== Saturday Sessions ==

* [[2016 Summit Kickoff]]
* [[Taking Awesome Beyond North America]]
* [[Getting more applications 2016]]
* [[Lunch Lean Coffee Discussion]]
* [[Awesome partnerships]]

== Sunday Sessions ==
* [[Awesome Beyond Awesome]]
* [[The Future of the Institute for Higher Awesome Studies]]
* [[Working Group: How to host Awesome Summit]]
* [[Working Group: Awesome Foundation Website]]
* [[Working Group: Culture]]

== Schwag Examples ==
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_114434.jpg Biz cards and paper flier examples]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_163517.jpg A bunch of tshirt examples from Saturday]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160305_134248.jpg Awesome Foundation DC tshirts]
* [http://wiki.awesomestudies.org/index.php?title=File:IMG_20160306_160310.jpg Jeff's pursuit of Awesome tshirt]

Working Group: How to host Awesome Summit

2016-03-09T06:24:29Z

Dough: Initial dump of notes

== Rough Schedule ==
'''Friday'''
* Social events to organize people, also a travel day for some

'''Saturday'''
* All-day summit stuff
* Party

'''Sunday'''
* All-day summit
* Some sort of after-party

== Things you need to run a summit: ==
* Places to have events
** Main venue
** Venue for the big party, different in style and shape than
** Alternative places for other parties (as needed)
* People
** Attend
** volunteer
** (It also helps if you have a city that people want to go to)
* Early Announcement
** Travel and housing assistance (bulk of SEA budget was travel assistance)
* Food
** Breakfast
** Lunch
* Parties
* Alcohol
** Something that can be had a parties
* Swag

== Timeline ==
Helps if you start about 9 months in advance, getting funding assistance. The longer runway you have, the easier it is to get starters
Planning events long-term is essential!

=== Sponsorship ===
In all fairness, didn’t go great in Seattle
Bailouts are not a sustainable way to do business
Put together a letter talking about the summit, what the foundation is, had tiers of sponsorships

== If you want to run a summit ==
* Have a project manager and a schedule
* Have a bunch of people to do the work
* Would have been great: have somebody who could do scheduling and resource management
* Helps to know what people are good at

Every summit is a little smaller than before--first summit in Boston had 200, New York had 100, Ottawa had 50, Seattle had 67

Second time we ran the summit, extra day of external-to-Foundation partners, was a little weird because it wasn’t quite an Awesome thing, may be a backburner thing

=== Donations ===
MailChimp has historically donated money
Historically it’s been local businesses
Chapters that are equipped to run a summit may not be equipped to fund a summit (Unsolved problem across multiple foundations)

=== Other options ===
Running a “New Philanthropy” conference on the side: happened for the New York Summit had that but it was problematic
* Winning the next summit
* Presentations to IHAS
What opportunities are there to NOT have it in North America?
* Or what about multiple summits for various countries? Stable established chapters are all in North America, for better or worse right now
* The travel assistance alone for Europe would be crippling

== Timeline of Summit Preparation ==
=== 9-12 months in advance===
* Hey, we’re having an event!
* (The event choosing process that we have right now doesn’t really give it enough runway: what if we announced the next two bids?)
* Start asking for money and venues, follow up weekly
* Used Proximate to get the registration site up and running
* Get trustees to add their registration to the site

=== 6 months in advance ===
* Everything nailed down
* Confirm travel assistance confirmation (Seattle had about 12 needing assistance)
* Travel and housing assistance can take many forms, some were PayPal sending of message
* Decide what kind of in-kind donations you might want

=== 3 months in advance ===
* Start working on housing assistance
* Start booking hotels in advance

=== Inside of 3 months ===
* Not planning, executing on plan
* Designs complete, printing complete, ideally weeks in advance to avoid rush fees
* Any in-kind donations done by 2 months
* If you want things from a major brand or a local brand that has been acquired by a local brand, leadtime is helpful there
* Relationship with Kind began when they wanted to send stuff to Awesome Foundation

=== Two weeks out ===
* Food for lunch
* Take advantage of Costco memberships

=== Day Zero===
Have the Summit!

=== Post-Summit ===
Recovery

== Documents to create ==
# Brands that are worth reaching out to
# Kinds of letters sent to people

== Deciding the program ==
* Decided partially because the exact same conversations happen in the same order almost every time
* Breakout sessions are the things that people normally want to talk about
* Having facilitators is helpful
* Think about making a bit more Unconference style with pre-filled boxes

== Questions / Thoughts ==
* Why are we not pulling together a super-committee of Awesome Summit folks?
* Can we reach out to designers outside of the chapters, for example?
* Not everybody has been to every conference, would be helpful for people to have some knowledge
* Documenting the experience--sometimes the stuff from the conference ends up in the New Chapters Handbook
* How do we take the gems of stuff and transfer it over to the working committees?

== Awesome Summit Audiences ==
Two audiences for Awesome Summit:
# New people who have never been to one before
#* Approach the summit with the wild optimism of Awesome
#* Meeting new people
# Old hands who have been to them before
#* Don’t need to go to the “what challenges to chapters face?” meetings because they’ve lived those questions before
#* Value is to see old friends, make new ones
#* Get tactical things done

Would be great to have some sort of way for people to make an opt-in to contact people

== Post-mortem ==
Had access to the budgets, verbal communications
But that was about it

User:Dough

2016-03-08T22:41:47Z

Dough: Created page with "Doug from the Portland, OR chapter"

Doug from the Portland, OR chapter

Working Group: Awesome Foundation Website

2016-03-08T22:40:55Z

Dough: added line break

== Website Background ==
The website - [http://awesomefoundation.org/ awesomefoundation.org] - tool for the management of Awesome Foundation projects
* Website is paid for by IHAS (Institute for Higher Awesome Studies), originally a Wordpress blog. Now built as Rails app running on Heroku with a PostgreSQL backend
* Been stripping away things from the site, now focusing on the core of project management (stripped out blog, global blog, these were things that nobody used)
* Every chapter gets its own page, that page highlights the projects that chapter has funded
* Inbound collection side will collect and organize applications
* Trustees log in, review applications, choose the winner, winner then reported on site
* Allows chapters to have email forwarding (something@awesomefoundation.org)

Things chapters do that the site does not do:
* Register/host their own domain name
* Have their own branding or functionality
* Some chapters have rolled their own application flow, not many but a few
* Maintain their own blog
* The main awesomefoundation.org will get your RSS feed

Other web infrastructure: the Wiki
* Closed to account creation because of spammers
* Email [wiki@awesomefoundation.org to create an account
* Is this the right tool for the job? Propose one if you can think of one
* Has a lot of logos, collateral, t-shirt designs

We can go a couple of different ways:
* Talk about new features, collect requirements and scope them later for GitHub issues
* Broader question about what the website does, are there functions that exist but nobody uses, or were there but pulled out

== Discussion Questions: ==
Is Jesse content to continue guiding the design of the web team? Yes, site is paid for by IHAS, optimized to be cheap to run, code is open source

How can people contribute?
* Contributing to the web site: do the work and submit a pull request that describes the change to be reviewed, optimized, checked for internationalization, that sort of thing. Stuff like Rails security updates are usually done without going through the process
* There is a staging environment to test pull requests
* Process went through recently with a new piece of functionality allows deans to hide specific applications from the list, can be overridden if need be (will be open to other trustees later, after deans try it out first)
* So far 39 applications have been hidden, so it’s working
* Sidebar: why hide vs delete? Delete removes the application completely, so deleting them erases the institutional memory of a chapter)
* Sidebar sidebar: general philosophy is that features that are added should
** Not hinder the way that chapters currently do things
** Add new features that are as broadly applicable as possible (there are as many processes as there are chapters, would like to be as agnostic as possible)
* There are probably things that are dean-only that should be opened a little more

== Discussion based on outstanding feature requests ==
Ideas for website in Cale’s discussion for the $2 million press release project:
# Last month at a glance
# Easier finding/viewing past funded projects from the public-facing side either by chapter or across chapters
# Identify winners in “finalist view”
# Modify standard questions (or add new ones)
# Alphabetically sort countries
# Project updates
# Is there a way to which information about the chapter that people applied to, because right now the application doesn’t tell you anything about where you're applying

=== Updating application with information about chapter ===
Discussion on how it might work, what the text should be, could be a configurable option

=== Finding past-funded projects ===
* Would be great to be able to sort/filter, see all projects
* On the list of tasks - issue #197
* If we had a prioritized list of things for something like a hackathon

=== Finalist view change ===
* In finalist view, find a way to identify the winner in the list (something like a star or background change)
* Would like to have ability to configure month or month/date view on the chapter list
* Idea to name features and tweaks based on the person/chapter who originated it

=== Modifying standard questions ===
Compiled a list of 14 questions that other chapters have, some of them are in common. Some people also combine questions into a single question because they only get three custom questions:
# How did you hear about us?
# What makes your project unique?
# What makes [CITY/AREA] more awesome?
# How will you measure success?
# What inspired you to come up with this project?
# How much covers salaries/stipends?
# Will the public be able to participate in this?
# What is your favorite movie quote?
# Would you like to join our mailing list? (Unless you're Portland and then you ask it in a passive-aggressive way)
# Can we publicize your project even if it doesn’t win?
# What is the estimated number of people served by your project?
# Whom would you recommend to apply and what’s their contact information?
# Tell us about your audience?
# What is the shortest, clearest way to describe your project?
# What is the drop-dead date on your project (when will the funds no longer be useful)?

These questions have always been problematic, should have been more flexible from the get-go. Main question is how flexible should the questions be?
* The three foundational questions are from the original Boston chapter
* Two ways to go about it:
** Seed a new chapter with the three main questions and allow them to go nuts with the extra questions -- but how do we migrate the data?
** Also to handle internationalization for the questions--we already have a problem with the extra questions being in a single language

Going forward:
* Add multiple additional questions and allow that to be configured on a chapter-by-chapter basis (not a big change but would allow
* Question about whether the questions should all be hard-coded but internationalization would be helpful
* If we did have everything configurable, would it be a nightmare for some chapters if they just asked all the questions
* Sidebar about the NABC method--if you ask the right questions, would you you get the right answers? This question is a bit out-of-scope of our little meeting
* Some discussion about picking a region: small discussion about where people can and can’t apply--Ottawa, Chicago, Boston, New York, and others have all funded projects based elsewhere geographically

=== Alphabetically sorting chapters ===
Already in the system as a feature request

=== Project Updates ===
Looking at a project it’s basically what the project wrote originally
* Under the funded description, sets a date that the project has been funded, then you can type in a description for the funded project (Dean function that none of us have ever heard of)
* Philosophy moving forward will be to allow all the trustees to do thing, the permissions system seems to be make things more difficult than they need to be

== Final thoughts ==
If there are features that are frustrating or would like to discuss: post to the global list but be gentle because this is all a volunteer effort

Working Group: Awesome Foundation Website

2016-03-08T22:40:21Z

Dough: Fixed formatting of sublist

== Website Background ==
The website - [http://awesomefoundation.org/ awesomefoundation.org] - tool for the management of Awesome Foundation projects
* Website is paid for by IHAS (Institute for Higher Awesome Studies), originally a Wordpress blog. Now built as Rails app running on Heroku with a PostgreSQL backend
* Been stripping away things from the site, now focusing on the core of project management (stripped out blog, global blog, these were things that nobody used)
* Every chapter gets its own page, that page highlights the projects that chapter has funded
* Inbound collection side will collect and organize applications
* Trustees log in, review applications, choose the winner, winner then reported on site
* Allows chapters to have email forwarding (something@awesomefoundation.org)

Things chapters do that the site does not do:
* Register/host their own domain name
* Have their own branding or functionality
* Some chapters have rolled their own application flow, not many but a few
* Maintain their own blog
* The main awesomefoundation.org will get your RSS feed

Other web infrastructure: the Wiki
* Closed to account creation because of spammers
* Email [wiki@awesomefoundation.org to create an account
* Is this the right tool for the job? Propose one if you can think of one
* Has a lot of logos, collateral, t-shirt designs

We can go a couple of different ways:
* Talk about new features, collect requirements and scope them later for GitHub issues
* Broader question about what the website does, are there functions that exist but nobody uses, or were there but pulled out

== Discussion Questions: ==
Is Jesse content to continue guiding the design of the web team? Yes, site is paid for by IHAS, optimized to be cheap to run, code is open source

How can people contribute?
* Contributing to the web site: do the work and submit a pull request that describes the change to be reviewed, optimized, checked for internationalization, that sort of thing. Stuff like Rails security updates are usually done without going through the process
* There is a staging environment to test pull requests
* Process went through recently with a new piece of functionality allows deans to hide specific applications from the list, can be overridden if need be (will be open to other trustees later, after deans try it out first)
* So far 39 applications have been hidden, so it’s working
* Sidebar: why hide vs delete? Delete removes the application completely, so deleting them erases the institutional memory of a chapter)
* Sidebar sidebar: general philosophy is that features that are added should
** Not hinder the way that chapters currently do things
** Add new features that are as broadly applicable as possible (there are as many processes as there are chapters, would like to be as agnostic as possible)
* There are probably things that are dean-only that should be opened a little more

== Discussion based on outstanding feature requests ==
Ideas for website in Cale’s discussion for the $2 million press release project:
# Last month at a glance
# Easier finding/viewing past funded projects from the public-facing side either by chapter or across chapters
# Identify winners in “finalist view”
# Modify standard questions (or add new ones)
# Alphabetically sort countries
# Project updates
# Is there a way to which information about the chapter that people applied to, because right now the application doesn’t tell you anything about where you're applying

=== Updating application with information about chapter ===
Discussion on how it might work, what the text should be, could be a configurable option

=== Finding past-funded projects ===
* Would be great to be able to sort/filter, see all projects
* On the list of tasks - issue #197
* If we had a prioritized list of things for something like a hackathon

=== Finalist view change ===
* In finalist view, find a way to identify the winner in the list (something like a star or background change)
* Would like to have ability to configure month or month/date view on the chapter list
* Idea to name features and tweaks based on the person/chapter who originated it

=== Modifying standard questions ===
Compiled a list of 14 questions that other chapters have, some of them are in common. Some people also combine questions into a single question because they only get three custom questions:
# How did you hear about us?
# What makes your project unique?
# What makes [CITY/AREA] more awesome?
# How will you measure success?
# What inspired you to come up with this project?
# How much covers salaries/stipends?
# Will the public be able to participate in this?
# What is your favorite movie quote?
# Would you like to join our mailing list? (Unless you're Portland and then you ask it in a passive-aggressive way)
# Can we publicize your project even if it doesn’t win?
# What is the estimated number of people served by your project?
# Whom would you recommend to apply and what’s their contact information?
# Tell us about your audience?
# What is the shortest, clearest way to describe your project?
# What is the drop-dead date on your project (when will the funds no longer be useful)?

These questions have always been problematic, should have been more flexible from the get-go. Main question is how flexible should the questions be?
* The three foundational questions are from the original Boston chapter
* Two ways to go about it:
** Seed a new chapter with the three main questions and allow them to go nuts with the extra questions -- but how do we migrate the data? ** Also to handle internationalization for the questions--we already have a problem with the extra questions being in a single language

Going forward:
* Add multiple additional questions and allow that to be configured on a chapter-by-chapter basis (not a big change but would allow
* Question about whether the questions should all be hard-coded but internationalization would be helpful
* If we did have everything configurable, would it be a nightmare for some chapters if they just asked all the questions
* Sidebar about the NABC method--if you ask the right questions, would you you get the right answers? This question is a bit out-of-scope of our little meeting
* Some discussion about picking a region: small discussion about where people can and can’t apply--Ottawa, Chicago, Boston, New York, and others have all funded projects based elsewhere geographically

=== Alphabetically sorting chapters ===
Already in the system as a feature request

=== Project Updates ===
Looking at a project it’s basically what the project wrote originally
* Under the funded description, sets a date that the project has been funded, then you can type in a description for the funded project (Dean function that none of us have ever heard of)
* Philosophy moving forward will be to allow all the trustees to do thing, the permissions system seems to be make things more difficult than they need to be

== Final thoughts ==
If there are features that are frustrating or would like to discuss: post to the global list but be gentle because this is all a volunteer effort

Working Group: Awesome Foundation Website

2016-03-08T22:39:06Z

Dough: Fixed formatting of giant wall o'text

== Website Background ==
The website - [http://awesomefoundation.org/ awesomefoundation.org] - tool for the management of Awesome Foundation projects
* Website is paid for by IHAS (Institute for Higher Awesome Studies), originally a Wordpress blog. Now built as Rails app running on Heroku with a PostgreSQL backend
* Been stripping away things from the site, now focusing on the core of project management (stripped out blog, global blog, these were things that nobody used)
* Every chapter gets its own page, that page highlights the projects that chapter has funded
* Inbound collection side will collect and organize applications
* Trustees log in, review applications, choose the winner, winner then reported on site
* Allows chapters to have email forwarding (something@awesomefoundation.org)

Things chapters do that the site does not do:
* Register/host their own domain name
* Have their own branding or functionality
* Some chapters have rolled their own application flow, not many but a few
* Maintain their own blog
* The main awesomefoundation.org will get your RSS feed

Other web infrastructure: the Wiki
* Closed to account creation because of spammers
* Email [wiki@awesomefoundation.org to create an account
* Is this the right tool for the job? Propose one if you can think of one
* Has a lot of logos, collateral, t-shirt designs

We can go a couple of different ways:
* Talk about new features, collect requirements and scope them later for GitHub issues
* Broader question about what the website does, are there functions that exist but nobody uses, or were there but pulled out

== Discussion Questions: ==
Is Jesse content to continue guiding the design of the web team? Yes, site is paid for by IHAS, optimized to be cheap to run, code is open source

How can people contribute?
* Contributing to the web site: do the work and submit a pull request that describes the change to be reviewed, optimized, checked for internationalization, that sort of thing. Stuff like Rails security updates are usually done without going through the process
* There is a staging environment to test pull requests
* Process went through recently with a new piece of functionality allows deans to hide specific applications from the list, can be overridden if need be (will be open to other trustees later, after deans try it out first)
* So far 39 applications have been hidden, so it’s working
* Sidebar: why hide vs delete? Delete removes the application completely, so deleting them erases the institutional memory of a chapter)
* Sidebar sidebar: general philosophy is that features that are added should
** Not hinder the way that chapters currently do things
** Add new features that are as broadly applicable as possible (there are as many processes as there are chapters, would like to be as agnostic as possible)
* There are probably things that are dean-only that should be opened a little more

== Discussion based on outstanding feature requests ==
Ideas for website in Cale’s discussion for the $2 million press release project:
# Last month at a glance
# Easier finding/viewing past funded projects from the public-facing side either by chapter or across chapters
# Identify winners in “finalist view”
# Modify standard questions (or add new ones)
# Alphabetically sort countries
# Project updates
# Is there a way to which information about the chapter that people applied to, because right now the application doesn’t tell you anything about where you're applying

=== Updating application with information about chapter ===
Discussion on how it might work, what the text should be, could be a configurable option

=== Finding past-funded projects ===
* Would be great to be able to sort/filter, see all projects
* On the list of tasks - issue #197
* If we had a prioritized list of things for something like a hackathon

=== Finalist view change ===
* In finalist view, find a way to identify the winner in the list (something like a star or background change)
* Would like to have ability to configure month or month/date view on the chapter list
* Idea to name features and tweaks based on the person/chapter who originated it

=== Modifying standard questions ===
Compiled a list of 14 questions that other chapters have, some of them are in common. Some people also combine questions into a single question because they only get three custom questions:
# How did you hear about us?
# What makes your project unique?
# What makes [CITY/AREA] more awesome?
# How will you measure success?
# What inspired you to come up with this project?
# How much covers salaries/stipends?
# Will the public be able to participate in this?
# What is your favorite movie quote?
# Would you like to join our mailing list? (Unless you're Portland and then you ask it in a passive-aggressive way)
# Can we publicize your project even if it doesn’t win?
# What is the estimated number of people served by your project?
# Whom would you recommend to apply and what’s their contact information?
# Tell us about your audience?
# What is the shortest, clearest way to describe your project?
# What is the drop-dead date on your project (when will the funds no longer be useful)?

These questions have always been problematic, should have been more flexible from the get-go. Main question is how flexible should the questions be?
* The three foundational questions are from the original Boston chapter
* Two ways to go about it:
## Seed a new chapter with the three main questions and allow them to go nuts with the extra questions -- but how do we migrate the data? ## Also to handle internationalization for the questions--we already have a problem with the extra questions being in a single language

Going forward:
* Add multiple additional questions and allow that to be configured on a chapter-by-chapter basis (not a big change but would allow
* Question about whether the questions should all be hard-coded but internationalization would be helpful
* If we did have everything configurable, would it be a nightmare for some chapters if they just asked all the questions
* Sidebar about the NABC method--if you ask the right questions, would you you get the right answers? This question is a bit out-of-scope of our little meeting
* Some discussion about picking a region: small discussion about where people can and can’t apply--Ottawa, Chicago, Boston, New York, and others have all funded projects based elsewhere geographically

=== Alphabetically sorting chapters ===
Already in the system as a feature request

=== Project Updates ===
Looking at a project it’s basically what the project wrote originally
* Under the funded description, sets a date that the project has been funded, then you can type in a description for the funded project (Dean function that none of us have ever heard of)
* Philosophy moving forward will be to allow all the trustees to do thing, the permissions system seems to be make things more difficult than they need to be

== Final thoughts ==
If there are features that are frustrating or would like to discuss: post to the global list but be gentle because this is all a volunteer effort

Working Group: Awesome Foundation Website

2016-03-08T22:32:01Z

Dough: Convert quote into sublist

== Website Background ==
The website - [http://awesomefoundation.org/ awesomefoundation.org] - tool for the management of Awesome Foundation projects
* Website is paid for by IHAS (Institute for Higher Awesome Studies), originally a Wordpress blog. Now built as Rails app running on Heroku with a PostgreSQL backend
* Been stripping away things from the site, now focusing on the core of project management (stripped out blog, global blog, these were things that nobody used)
* Every chapter gets its own page, that page highlights the projects that chapter has funded
* Inbound collection side will collect and organize applications
* Trustees log in, review applications, choose the winner, winner then reported on site
* Allows chapters to have email forwarding (something@awesomefoundation.org)

Things chapters do that the site does not do:
* Register/host their own domain name
* Have their own branding or functionality
* Some chapters have rolled their own application flow, not many but a few
* Maintain their own blog
* The main awesomefoundation.org will get your RSS feed

Other web infrastructure: the Wiki
* Closed to account creation because of spammers
* Email [wiki@awesomefoundation.org to create an account
* Is this the right tool for the job? Propose one if you can think of one
* Has a lot of logos, collateral, t-shirt designs

We can go a couple of different ways:
* Talk about new features, collect requirements and scope them later for GitHub issues
* Broader question about what the website does, are there functions that exist but nobody uses, or were there but pulled out

== Discussion Questions: ==
Is Jesse content to continue guiding the design of the web team? Yes, site is paid for by IHAS, optimized to be cheap to run, code is open source

How can people contribute?
* Contributing to the web site: do the work and submit a pull request that describes the change to be reviewed, optimized, checked for internationalization, that sort of thing. Stuff like Rails security updates are usually done without going through the process
* There is a staging environment to test pull requests
* Process went through recently with a new piece of functionality allows deans to hide specific applications from the list, can be overridden if need be (will be open to other trustees later, after deans try it out first)
* So far 39 applications have been hidden, so it’s working
* Sidebar: why hide vs delete? Delete removes the application completely, so deleting them erases the institutional memory of a chapter)
* Sidebar sidebar: general philosophy is that features that are added should
** Not hinder the way that chapters currently do things
** Add new features that are as broadly applicable as possible (there are as many processes as there are chapters, would like to be as agnostic as possible)
* There are probably things that are dean-only that should be opened a little more

== Discussion based on outstanding feature requests ==
Ideas for website in Cale’s discussion for the $2 million press release project:
Last month at a glance
Easier finding/viewing past funded projects from the public-facing side either by chapter or across chapters
Identify winners in “finalist view”
Modify standard questions (or add new ones)
Alphabetically sort countries
Project updates
Is there a way to which information about the chapter that people applied to, because right now the application doesn’t tell you anything
Finding past-funded projects
Would be great to be able to sort/filter, see all projects
On the list of tasks - issue #197
If we had a prioritized list of things for something like a hackathon
Finalist view change
In finalist view, find a way to identify the winner in the list (something like a star or background change)
Would like to have ability to configure month or month/date view on the chapter list
Idea to name features and tweaks based on the person/chapter who originated it

Modifying standard questions
Compiled a list of 14 questions that other chapters have, some of them are in common. Some people also combine questions into a single question because they only get three custom question:
How did you hear about us?
What makes your project unique?
What makes [CITY/AREA] more awesome?
How will you measure success?
What inspired you to come up with this project?
How much covers salaries/stipends?
Will the public be able to participate in this?
What is your movie quote?
Would you like to join our mailing list?
Can we publicize your project even if it doesn’t win?
What is the estimated number of people served by your project?
Whom would you recommend to apply and what’s their contact information?
Tell us about your audience?
What is the shortest, clearest way to describe your project?
What is the drop-dead date on your project (when will the funds no longer be useful)?
These questions have always been problematic, should have been more flexible from the get-go. Main question is how flexible should the questions be?
The three foundational questions are from the original Boston chapter
Two ways to go about it:
Seed a new chapter with the three main questions and allow them to go nuts with the extra questions -- but how do we migrate the data? Also to handle internationalization for the questions--we already have a problem with the extra questions being in a single language
Add multiple additional questions and allow that to be configured on a chapter-by-chapter basis (not a big change but would allow
Question about whether the questions should all be hard-coded but internationalization would be helpful
If we did have everything configurable, would it be a nightmare for some chapters if they just asked all the questions
Sidebar about the NABC method--if you ask the right questions, would you you get the right answers? This question is a bit out-of-scope of our little meeting
Some discussion about picking a region: small discussion about where people can and can’t apply--Ottawa, Chicago, Boston, New York, and others have all funded projects based elsewhere geographically
Alphabetically sorting questions
Already in the system
Project Updates
Looking at a project it’s basically what the project wrote originally
Under the funded description, sets a date that the project has been funded, then you can type in a description for the funded project (Dean function that none of us have ever heard of)
Philosophy moving forward will be to allow all the trustees to do thing, the permissions system seems to be make things more difficult than they need to be

Going forward
If there are features that are frustrating or would like to discuss: post to the global list but be gentle because this is all a volunteer effort

Working Group: Awesome Foundation Website

2016-03-08T22:30:20Z

Dough: Initial dump of notes

== Website Background ==
The website - [http://awesomefoundation.org/ awesomefoundation.org] - tool for the management of Awesome Foundation projects
* Website is paid for by IHAS (Institute for Higher Awesome Studies), originally a Wordpress blog. Now built as Rails app running on Heroku with a PostgreSQL backend
* Been stripping away things from the site, now focusing on the core of project management (stripped out blog, global blog, these were things that nobody used)
* Every chapter gets its own page, that page highlights the projects that chapter has funded
* Inbound collection side will collect and organize applications
* Trustees log in, review applications, choose the winner, winner then reported on site
* Allows chapters to have email forwarding (something@awesomefoundation.org)

Things chapters do that the site does not do:
* Register/host their own domain name
* Have their own branding or functionality
* Some chapters have rolled their own application flow, not many but a few
* Maintain their own blog
* The main awesomefoundation.org will get your RSS feed

Other web infrastructure: the Wiki
* Closed to account creation because of spammers
* Email [wiki@awesomefoundation.org to create an account
* Is this the right tool for the job? Propose one if you can think of one
* Has a lot of logos, collateral, t-shirt designs

We can go a couple of different ways:
* Talk about new features, collect requirements and scope them later for GitHub issues
* Broader question about what the website does, are there functions that exist but nobody uses, or were there but pulled out

== Discussion Questions: ==
Is Jesse content to continue guiding the design of the web team? Yes, site is paid for by IHAS, optimized to be cheap to run, code is open source

How can people contribute?
* Contributing to the web site: do the work and submit a pull request that describes the change to be reviewed, optimized, checked for internationalization, that sort of thing. Stuff like Rails security updates are usually done without going through the process
* There is a staging environment to test pull requests
* Process went through recently with a new piece of functionality allows deans to hide specific applications from the list, can be overridden if need be (will be open to other trustees later, after deans try it out first)
* So far 39 applications have been hidden, so it’s working
* Sidebar: why hide vs delete? Delete removes the application completely, so deleting them erases the institutional memory of a chapter)
* Sidebar sidebar: general philosophy is that features that are added should
* Not hinder the way that chapters currently do things
* Add new features that are as broadly applicable as possible (there are as many processes as there are chapters, would like to be as agnostic as possible)
* There are probably things that are dean-only that should be opened a little more

== Discussion based on outstanding feature requests ==
Ideas for website in Cale’s discussion for the $2 million press release project:
Last month at a glance
Easier finding/viewing past funded projects from the public-facing side either by chapter or across chapters
Identify winners in “finalist view”
Modify standard questions (or add new ones)
Alphabetically sort countries
Project updates
Is there a way to which information about the chapter that people applied to, because right now the application doesn’t tell you anything
Finding past-funded projects
Would be great to be able to sort/filter, see all projects
On the list of tasks - issue #197
If we had a prioritized list of things for something like a hackathon
Finalist view change
In finalist view, find a way to identify the winner in the list (something like a star or background change)
Would like to have ability to configure month or month/date view on the chapter list
Idea to name features and tweaks based on the person/chapter who originated it

Modifying standard questions
Compiled a list of 14 questions that other chapters have, some of them are in common. Some people also combine questions into a single question because they only get three custom question:
How did you hear about us?
What makes your project unique?
What makes [CITY/AREA] more awesome?
How will you measure success?
What inspired you to come up with this project?
How much covers salaries/stipends?
Will the public be able to participate in this?
What is your movie quote?
Would you like to join our mailing list?
Can we publicize your project even if it doesn’t win?
What is the estimated number of people served by your project?
Whom would you recommend to apply and what’s their contact information?
Tell us about your audience?
What is the shortest, clearest way to describe your project?
What is the drop-dead date on your project (when will the funds no longer be useful)?
These questions have always been problematic, should have been more flexible from the get-go. Main question is how flexible should the questions be?
The three foundational questions are from the original Boston chapter
Two ways to go about it:
Seed a new chapter with the three main questions and allow them to go nuts with the extra questions -- but how do we migrate the data? Also to handle internationalization for the questions--we already have a problem with the extra questions being in a single language
Add multiple additional questions and allow that to be configured on a chapter-by-chapter basis (not a big change but would allow
Question about whether the questions should all be hard-coded but internationalization would be helpful
If we did have everything configurable, would it be a nightmare for some chapters if they just asked all the questions
Sidebar about the NABC method--if you ask the right questions, would you you get the right answers? This question is a bit out-of-scope of our little meeting
Some discussion about picking a region: small discussion about where people can and can’t apply--Ottawa, Chicago, Boston, New York, and others have all funded projects based elsewhere geographically
Alphabetically sorting questions
Already in the system
Project Updates
Looking at a project it’s basically what the project wrote originally
Under the funded description, sets a date that the project has been funded, then you can type in a description for the funded project (Dean function that none of us have ever heard of)
Philosophy moving forward will be to allow all the trustees to do thing, the permissions system seems to be make things more difficult than they need to be

Going forward
If there are features that are frustrating or would like to discuss: post to the global list but be gentle because this is all a volunteer effort

Category:Summit 2016

2016-03-08T22:20:33Z

Dough: Added Sunday sessions

The 2016 Summit was held in Seattle, Washington.

== Saturday Sessions ==

* [[Taking Awesome Beyond North America]]
* [[Getting more applications 2016]]

== Sunday Sessions ==
* [[Working Group: How to host Awesome Summit]]
* [[Working Group: Awesome Foundation Website]]

Category:Summit 2016

2016-03-06T09:09:33Z

Dough: /* Saturday Sessions */

The 2016 Summit was held in Seattle, Washington.

== Saturday Sessions ==

* [[Taking Awesome Beyond North America]]
* [[Getting more applications 2016]]

Getting more applications 2016

2016-03-06T09:08:10Z

Dough: Original draft of notes from meeting

== Submission variability ==
Started off with a custom question on the application form from Seattle chapter: Who else would you suggest apply for the grant?

Some chapters have noticed a “sine wave of quality in submissions” - at the lowest point, all of them have potential, but they’re not the greatest applications. Possible solutions:
* Question: why would you think one of the trustees think this idea was awesome?
* How do we help bad presentations?
* [https://nielschrist.wordpress.com/2012/07/13/the-nabc-method-standford-research-institute-sri/ ONABC pitch tool], which teaches you how to get a grant

== Picking grants to find ==
Don’t split grants, bad things happen when people are coming in thinking it's $1000 and it only ends up being $500
Idea for giving out grant money: Bright Pink Envelopes from Amazon!

Question: do you fund grant where it's a portion of a $10K range? Not so much, if people target the grant at something specific, it seems something better
The difference between a $300 event and a $1300 event is repeatability - sometimes the money will be required to just go forward

== Different places to solicit applications ==
Alternative gathering of pitches
Live application solicitation at a Farmer’s Market or maker faire
Ordering drinks in a bar and having people come in, people had a hard time following up on the ideas

Question: what do chapters do to maintain relationship with previous winners
25th Pitch Night in Boston - bring projects back

Pitch party
Ottawa’s third birthday party had an amazing story about one winner turning over the prize to another applicant, which resulted in some fun media coverage

Is this worthy vs is this awesome? Ideally it’s both

On the waves of applications that go through--as word-of-mouth spreads through a group, like attracts like, so we do get waves of things
How does one expand that group?
Making tactical grants can come into play: do you make a grant with a group with the hopes of gaining more traction with them?

== Roles for trustees ==
Residency program - Chicago chapter is looking to get more geographic representation by bringing in people from different groups to be champions of awesome, mix up the debate, vote but don’t contribute money
Media student representative as unpaid internship to handle media queries and process
PR person - how do other chapters do it?

Debating about how to help applicants reapply--how to suggest different approaches, rephrasing what's going on

Question about the number of applicants that a chapter gets
Seattle goes from 30 applications to 3 finalists
Ottawa gets more exposure when they do media - radio ads work well
Chicago talked about doing a sample application -> here’s a good one and bad one

== Advertising and merchandise ==
Advertising - billboards (Portland has had some success with partnering with [http://thejoyteam.org/ The Joy Team]), rain.works
Liverpool chapter distributed pink envelopes with “open me” (very ‘Alice in Wonderland’) - containing 5 pounds and a letter about what the Awesome Foundation is - distributed throughout town and asked people to tweet what they did with the money: press and media attention
Trustees: pitch ideas to each other to create and plug marketing ideas

Marketing pitches: given that we want money to go to pitches, is it weird to spend money on advertising?
It’s OK to take a month off and take that money to be more proactive
T-shirt sales aren’t huge, but people tend to buy
Dropbox full of files for all sorts of ads - vertical banner with Awesome branding, “sponsored by” gets a lot of foot traffic
(Add link to Awesome Wiki, too)
Graphic design - asked students to have new logo and branding campaign

Advertising at sporting events with flyers - created a small little park on Parking Day
Ottawa had somebody pack in flyers in the take-home pizza boxes from a restaurant
Stack of flyers in an Uber or Lyft car
Incubator sessions of ideas / implementations on YouTube - create an idea but no time to implement them
How does one get more into maker spaces? It’s hard to organize an event, but if one can piggyback onto an existing one (there are “so many”)
Identify your target network and think about how to reach them
Focus a grant on another existing event like Parking Day - Bicycle Festival
Chicago was really successful with one group of puppeteers, so much so that “We had to put a year-long moratorium on puppeteering projects”

The idea of the “hustler trustees” - identify all the local media contacts and send to them. DC does a newsletter that’s about things that are not just about Awesome but other quirky winners as well.

Category:Summit 2016

2016-03-06T08:49:01Z

Dough: /* Saturday Sessions */

== Saturday Sessions ==

* [[Taking Awesome Beyond North America]]
* [[Getting more applications 2016]]