√Customize invite email subject/body (everybody check at meeting)
√Invite the group (Amy)
√(requires explanation, but works) Peer pattern relationships (John)
√(something - John)Logo - words/picture (make card of potential images)
√(started)Front page text - how to get involved (Tree, others?), and contribute to pattern writing, points to help
√Help card (Amy)
seems obscure;
link to screencast? (none yet)
explain or link to explanation of ???
√Sidebar - navigational links: patterns (link or list)
how is it being organized?
√(started)draw from riseup (John)
Intentions and next steps from https://we.riseup.net/pattern_language
√link from front: http://grouppatterns.wagn.org/wagn/software_for_this_project
√other important site dev info (EtherPad link, next mtg items), and:
√Start a card for where/what we want re documentation
√Pattern template:
√What about description sub-items? In practice they are interwoven. So...
√Use help text to say that Description covers Context, Instructions, Variations, Cautions & Caveats
√John will get some info from Ethan & Lewis on some tech questions (navbar across top, cost of finding references to nonexistent patterns).
√Tree will register & pay for grouppatternlanguage.org.
√Tree will email list of the whole group so far to John A and Amy
√John & Amy will review list, suggest folks to potentially invite early, and we'll decide about that next week.
√John will get Tree the technical info needed to get the new domain pointed to the wiki.
√Tech support: John is inviting from the list we generated until we have two-three techies who are willing to support people when we do the 'launch'. Raines and Brandon yes, still asking others. Tech meeting scheduling | admin
√Documentation
John K has posted initial draft — How to write a pattern. Needs more polishing.
John A made some edits/comments.
Tree will too, others welcome as well.
√John & Tree will edit *invite+*message
√IRC for live chat - about project in general, John will add to invite email
√Tree & John will edit pattern names for brevity/clarity
√John & Tree will edit text at top of brainstorm list of potential patterns to explain it was a brainstorm list, green/red, etc.
√Email lists - Tree will decide and set up, and write and send email announcing launch (including that they will get invite to site over next few days if they said they wanted to help write; and feel free to sign up for an account if you don't get such an invitation)
√Tree to look at finances to see about paying Wagn for hosting. Done, Tree decided to give Grass Commons $120 to cover hosting for July-Dec. 2009.
√Tree will create page about mailing lists and link from appropriate places
√John will use inclusions for template/What we mean by pattern on How to write a pattern
√Make clear how individuals can change their settings, preferably both from Help box and from "My Card" links.
√Revise News feature. (Box somewhere on homepage with brief update, linked to longer card elsewhere.)
√John will email discussion list to get events page going.
√Tree will use Sue's grid to follow up contact with people who were on Crabgrass and have not migrated to Wagn, were invited to Wagn and have not yet signed on, etc.
√Tree will send surveys to people on Wagn who never received one.
√Add RSS feed from email list(s) to our site.
√John will put a space for Stories on user cards, and have them show up on Pattern cards and on a Stories page.
√John A emailed list to organize show & tell
√20100210 reported to the NCDD Facebook group about our Berkeley session using a link to Tree's report - brandon
√John reloaded the photos that were missing from patterns.
√John got CII to set up the donations page so that it automatically tracks which CII donations are for our project. So now it's really easy for folks to donate to us online.
√Fix the Name section on How to write a pattern.
√Rework menu so that it takes less space vertically. - Tree & John, May 2010
.