AwesomeWiki - User contributions [en]

Website improvements

2012-07-22T18:25:41Z

Gregmarra:

{{TOC right}}

== Action Items ==

* [jesse] Move issues from Asana to Github
* [jesse] Add license stuff to code
* [jesse] README checked into the codebase with instructions
* [jesse] Github wiki page with philosophy
* [jesse] Send out the Awesome Web Team googlegroup
* [everyone] Sign up for Awesome Web Team googlegroup
* [everyone] Thank Jesse for rocking so much at leading this effort

== Notes ==

History of the website:
* Knight Grant enables hiring a firm to build new site
* Christina and Jesse wrote an RFP
* thoughtbot won the contract

=== Open Source ===

Goal has always been to publish code open source. We'll probably GPL license it, with IHAS as the rightsholder.

=== Tools ===

Bug Tracking Options
* Github issues
* Asana
* Pivotal Tracker
* Better Means

We'll start with Github issues and see when it starts to break down. Fewer tools better.

=== Philosophy ===

* Focus is on people and projects.
* Let chapters keep their autonomy.
* We're not trying to build a blogging engine.

General Process:
* Please jump straight in if you're making some small tweaks!
* Do some pre-planning on the list before you jump in to do anything huge
* People should make changes and test against their own heroku apps
* Send pull requests once your feature is ready
* The main staging app won't be used by everyone, just to test pre-prod push

=== Priorities ===

This is a highly incomplete list, and wasn't worth discussing in depth in person.

Some things to work on:
* All Project List - Aggregate funded projects across all chapters
* Funded Description - Don't just re-use the description field for the project, need a separate "for the web" description
* Project info / metadata

* All for *.xml, *.csv, *.rss etc endings to pages to make it easier to consume data

[[category:Sunday]]
[[category:Operations]]
[[category:Tools]]

Website improvements

2012-07-22T18:25:27Z

Gregmarra:

{{TOC right}}

= Web Working Group =

== Action Items ==

* [jesse] Move issues from Asana to Github
* [jesse] Add license stuff to code
* [jesse] README checked into the codebase with instructions
* [jesse] Github wiki page with philosophy
* [jesse] Send out the Awesome Web Team googlegroup
* [everyone] Sign up for Awesome Web Team googlegroup
* [everyone] Thank Jesse for rocking so much at leading this effort

== Notes ==

History of the website:
* Knight Grant enables hiring a firm to build new site
* Christina and Jesse wrote an RFP
* thoughtbot won the contract

=== Open Source ===

Goal has always been to publish code open source. We'll probably GPL license it, with IHAS as the rightsholder.

=== Tools ===

Bug Tracking Options
* Github issues
* Asana
* Pivotal Tracker
* Better Means

We'll start with Github issues and see when it starts to break down. Fewer tools better.

=== Philosophy ===

* Focus is on people and projects.
* Let chapters keep their autonomy.
* We're not trying to build a blogging engine.

General Process:
* Please jump straight in if you're making some small tweaks!
* Do some pre-planning on the list before you jump in to do anything huge
* People should make changes and test against their own heroku apps
* Send pull requests once your feature is ready
* The main staging app won't be used by everyone, just to test pre-prod push

=== Priorities ===

This is a highly incomplete list, and wasn't worth discussing in depth in person.

Some things to work on:
* All Project List - Aggregate funded projects across all chapters
* Funded Description - Don't just re-use the description field for the project, need a separate "for the web" description
* Project info / metadata

* All for *.xml, *.csv, *.rss etc endings to pages to make it easier to consume data

[[category:Sunday]]
[[category:Operations]]
[[category:Tools]]

Trustee engagement

2012-07-21T20:57:45Z

Gregmarra: /* Notes from Greg */

{{TOC right}}

How do we keep our trustees excited and engaged?

== Notes from Greg ==

Breaking this into major themes I see.

=== General Protips ===

* Meeting with grant winners engages trustees and connects them to the projects they're funding.
* Regular structure with people signed on to it makes people more likely to be able to attend.
* Food collects money in $300 chunks to make operations roll smoother, given their virtual distributed nature

=== On Group Size ===

* Boston has 26 members, so about 10-14 show up each time and vote on two grants.
* Halifax has 30 members, and does three rounds (first round prune, finalist selection, judging a live event) with 10 people, so everyone plays a role somewhere in the funnel
* Bigger org makes closeness in a big group harder. You become a bit more of a blob and a bit less of a "team"

=== On Group Harmony ===

* In SF, forming personal relationships between the trustees has helped sustain things
* In Pittsburgh, meetings are very inefficient, because they're basically social events. Wine, beer, and food slow down the voting, in a good way :) No virtual call ins allowed
* Food is virtual, so people don't know each other irl, but still has lively discussions.

=== On New Blood ===

* Boston let about 10 people in at once. It may have "saved the chapter"
* New York had a big turnover at once, as the original trustees got too busy or too famous. Bringing in new blood changed the culture and established new norms
* Set norms with the active people, then invite more people to 'soft replace' the flakier people
* More people spreads responsibility, gets you more money to utilize
* Guest / Honorary trustees (like the mayor!) are a good source of fresh excitement
* New people give busy people the opp to back out gracefully since they're not letting people down

=== On Ideological Splits ===

* Major split seems to be between "silent awesome" and "go for famo"
* Detroit once reconvened to overturn a grant because one trustee decided the selected project didn't set the right tone for the group. Don't be afraid to speak up after decisions are made. Be diplomatic and sensitive when communicating like this.

[[category:Saturday]]
[[category:Operations]]

Trustee engagement

2012-07-21T20:40:54Z

Gregmarra: /* Notes from Greg */

{{TOC right}}

How do we keep our trustees excited and engaged?

== Notes from Greg ==

- Meeting with grant winners engages trustees and connects them to the projects they're funding.
- Boston has 26 members, so about 10-14 show up each time and vote on two grants.
- Halifax has 30 members, and does three rounds (first round prune, finalist selection, judging a live event) with 10 people, so everyone plays a role somewhere in the funnel.
- In SF, forming personal relationships between the trustees has helped sustain things.
- In Pittsburgh, meetings are very inefficient, because they're basically social events. Wine, beer, and food slow down the voting, in a good way :) No virtual call ins allowed.
-

[[category:Saturday]]
[[category:Operations]]

Trustee engagement

2012-07-21T20:38:35Z

Gregmarra:

{{TOC right}}

How do we keep our trustees excited and engaged?

== Notes from Greg ==

asdf

[[category:Saturday]]
[[category:Operations]]