2008-12-15+check-in+notes*trash

Accounting

  • loan repayment
  • deferred salaries
  • invoices
  • grant costing
  • public support test

Sales

  • FoCo bikes
  • United Way
  • this week
  • Women's Resource Center

Release


Decks


RCC Wagn

  • HTML cards
  • what to say if anything in announcement other than "it's ready, go!" (that's good enough)
  • Imagining us having a focus on some Wagn-y thing at any given time that we're trying to put out there.
    • Tagging as first Wagn-ish thing? (Sessions they've seen, on the new wiki they're at the same level as the mockup, and we don't need them for two+ months. Like the idea of people having experience with something else before.) No big push for now at least, let people settle in.

 

okay to rename taglist to tags? yes

 

Mini Design Review

 

Pressing Design Questions: (coders await)

  • Users in open-edit wagns

          o Now:
                + when you create an account request, it creates the user extension (let's call that account for now)
          o allow user card without account extension
                + how do you add the extension later?
                      # fill in email/password in Options tab and click Save
                            * cue text: something like, "add your email address and a password to turn this into your account card"
                      # remove manual approval - low-hanging fruit for spam protection
                      # remove "Request an Account" - InvReq creatable by Admin
                      # global permissions - add create account (to allow non-manual)
                + people will create Basic card with their name, and right now we have no way to copy content to appropriate +card when it gets made into a User card.
          o other people than us have Admin/Superuser privs on Wagns we host, and could open up HTML, Script, Rubycards for anyone to edit. Can this cause problems outside of the content of the Wagn itself?
                + HTML - no problem
                + Script - if there's no scripts in directory, safe (and can be turned off in wagn.rb)
                + Ruby - denial of service easy (can be turned off in wagn.rb)

  • _user in inclusions but not links
  • View/Edit/etc. always visible - easy? Ethan will handle rcc-planning email on this

try it

 

wagneers

intro

videos

features

syntax

weekly calls

ideas

 

twitter

mailing list

 

developers

roadmap

next release

tickets

pack API

REST API

one-pager

 

github

mailing list

 

wagn.org

recent

todo