User:Ryan52/old todo

o hai

Because I don't like trac. I probably don't like any project management program for that matter. Using this because I loose TODO files on my system too easily. :p

features wanted

list of features wanted, most from a discussion with kc8pxy (some will be taken care of by him/his coders), others need my help.

• settings page (admin password, everything in the defaults table, metadata too..)
• 01:17 <kc8pxy> volunteer certification trancking
  • 01:17 <Ryan52> aka contact_types? :)
  • 01:18 <kc8pxy> btu i don't want unilateral designation.
  • 01:18 <kc8pxy> i want to have 2 or 3 people to "vote" them competent.

todo list - a bunch of crap that nobody cares about

saturday todo list

• cleanup teh data that was deadbeat during the coveredness time. it doesn't have teh field set called covered. (fixed in code)
  • add a migration to "UPDATE gizmo_events SET covered = 'f' WHERE covered IS NULL AND donation_id IS NOT NULL"?
• DELETE FROM gizmo_events WHERE donation_id IS NULL AND sale_id IS NULL AND disbursement_id IS NULL AND recycling_id IS NULL;
• deadbeat discounts weren't setting occured_at -- fixed, but need to clean up data again...
  • edit and save these donations (might work, might not):
    • 127598
    • 127608
    • 127609
    • 127818
    • 127908
    • 128080
• should it bitch and complain if you try to add 3 uncovered CRTs, even though they are coverable and you have not reached the limit? what if the person is fully covered and you try to add any uncovered coverables? it currently only error checks if they try to cover more than you should, but it doesn't check if you aren't covering enough...it can easily. should it?

i'm working on

• vhost based routes for separating fgdb and library, and having a setup page. I'm working on this at a glaciers pace, but I'm still working on it. (integrated with settings page, sort of)
• library
• get ticgit ready, and start adding stuff to it
• finish sorting trac tickets, and move them to RT or ticgit

next release

• reports over time:
  • conditions
    • add support for conditions integration
    • add OR support to conditions ... this will be invasive, probably
• switch to rspec
  • fix existing tests how they are
  • learn to use rspec
  • start writing new tests

library

• finish library stuff
  • Lookup books from library of congress or similar
  • Check out books to people
  • Track checkout history
  • Print labels
  • Inventory list (so we can check to see what's missing, etc.)
  • Looking up all overdue books
  • (this may not be a complete list)

things left for git

things that matter

• trac
• cruise control (useless since all of the tests are broken)

things that dont

• gitweb on devo (currently have it on my vps...)
• make the git repos publicly accessible from somewhere other than git.ryan52.info (alternate method is to just make {git,other-dev}.freegeek.org a CNAME to my vps :D)
  • should we also push to github? currently my scripts do pulling, but I guess pushing could be added..
• rewrite the commit email script -- it sucks (I can live with it now)
• figure out somewhere for the devel data to live that is faster than the horrible freegeek dsl (heh. I *do* have enough bandwith on my vps...guess I miscalculated or somethin)

should do soonish

• make it work with rails 2.2.2
• interface for adding contracts
• a way to disable contracts
• "power user" multiple systems per line item

for a rainy day

• add notes via web ui
• speed up the regex in the vhosting stuff wrt printme, so that it caches results or somethin.
• coveredness without contracts is broken (in the js) -- no big deal
• figure out a more convenient way of upgrading to a new sprint
• covered condition (extra)
  • so we can see either. we don't need side by side numbers at this point, but who knows???
• update the documentation (meh, not *that* important)
• security fixing
  • CSRF (use rails' protect_from_forgery and verify methods)
    • Look at this: [1] looks really kewl!
  • check for SQL injection, we won't have to worry about this in most places since we use active record, but the reports where we use SQL directly should be checked.
  • Rails Security Guide
• look closer at the XSS stuff (safe erb) -- I got a lot of em
  • the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
• remove cruft from that ajax helper thing
• get rid of duplicated data in code
  • conditions stuff is all over the place
  • permissions for various controllers are split between the sidebar and the controller itself
• fgss generic regexps
  • 18:44 < aSmig> this should match everything but 31: ([0]{5,}|123456789|^.{1,4}$|^[^0-9]*$)
    • false positives still exist ... figure it out
• move the vendor/plugins to their own submodules...maybe I shoulda done this first, since it's gonna get even more messy with the git bug...anyway, too late for that, whatever. I'll work it out :)
  • update them

skedjulnator

integrating skedjulnator into fgdb.rb

• switch to git (I hope Richard won't mind..)
• port it to rails 2.1
• make it not suck ("optimize queries")
• make it integrate with the "normal" contacts table
• port remaining 5 tickets to ticgit (I hope Richard won't mind..)

what I did today

Moved to ChangeLog