close fullscreen

Financial check-in (5)

Hosting and consulting (8)

  • pricing?
  • NEXT STEPS:
    • sell to people and learn - Ethan: academics/foundations
  • Justin - ideas on audience  (social media gurus + foundations )
    • foundations - grants for 3rd party?  x-win scenario
    • specific markets - with templates - eg realtors

Communication (5)

  • √(yes) incl http://wagn.org/wagn/Blog_entries_by_date in sidebar under Wiki on Wheels?
  • rework front card
  • http://wagn.org/wagn/Wagn_0.10_and_beyond
    • break out into Wagn spokes


Release process / tracking (5)

  • Current Release - where is it?
  • Justin doesn't see ticket stuff in sidebar. Make him Developer? Or, could:
    • Create Wagneer role and give it to him (and others)
    • add Wagneer Menu card; move Ticket links there
  • Pivotal Tracker - try for a release
  • Justin seeking clarity on feedback routes
  • OUTCOME: blog objectives for 1.0  (explain the holdup :-)
  • PLAN  dev team use tickets & pivotal, point non-devs to: Wagn+discussion add archive card & link


Hooze Requiem

  • audience? Bronwyn, Art?, Charles?
  • invite to call


Minis

  • United Way
  • RCC
  • back-ups


Development Planning

Fortnight clean-up / bugs - priority clarity? (given new hosting/consulting emphasis) (10)

  • Priority now is end-user experience
  • Specific issues (Ethan & Lew will decide what to do this week):
    • use attachment fu for uploads
    •  
      • sizing - on image card itself - Wagn picks a reasonable size to display
      • inclusions |size:
        • icon
        • small
        • medium
        • large
    • Permissions
      • allow authorized users to see cards (mostly ok for now)
      • don't show cards wo permissions in line view
    • Renaming? (Phoebe - allow renaming in more contexts )
    • first user = "InvitationRequest+*tform" - be aware when setting up Wagns
    • "context gotta include position" (frequent exception email)
    • Error Handling: /wagn/Bugs+unassigned#Error%20handling ?
  • Ethan had to go; E&L will finish prioritizing

 

Mini design review


√images (see above)

√interpret Wagn links in Phrase and PlainText (web links & inclusions already interpreted) - add note to update documentation that used them to escape

√progress bar or wheel for slow loads - where? how does it affect bottom-right alerts (if it doesn't go there)?

√ funny characters - whitelist? links from card key should solve a lot without doing that handle breaking characters in card names