User:Ryan52/todo

From FreekiWiki
< User:Ryan52
Revision as of 15:49, 15 May 2010 by Ryan52 (talk | contribs) (→‎queue: more info)
Jump to navigation Jump to search

how I want to handle things

  • handle all small tasks as they come in.
  • aim for release every two weeks, with the queues outlined below
  • try to stay on track with the expected release dates and catch up if get behind
  • eliminate ASS/fgdiag/etc todo lists so can focus on fgdb.rb

not fgdb

  • User:Ryan52/maintenance
  • ASS
    • #18193 set up oahu as secondary dns?
    • #18267 RT Bug with creating tickets with images.
    • #16697 RT requires multiple logins
    • #17664 make diskless xterm default font size bigger
    • #17554 update https/imaps certificate before june
  • hard drive tester
    • #17398 Problems with HDD tester script
    • #12893 HD testing script DMA errors
  • keyboard tester
    • #15784 Newfangled keyboard tester addition request/issues
    • #16161 additional function keys (F13 - F16) as well as the volume/eject keys to (volume up/down/mute keys)
    • #16162 Macs: the equal (=) sign on the number pad never shows up as working
    • #16164 screenshots of each layout and the settings screen

queue

the old shit release - May 14

  • #15885 fix up coveredness tracking
    • trying to accomplish:
      • the sales/transactions/etc screens should preseed the covered value from the system id
      • #15846 Make FG-PDX automatically uncovered
    • plan:
      • change the checkbox to a dropdown
      • code after entering a system that (synchronously, not async) connects to get the systems covered value if it exists, presets it in the widget, and disables the widget
      • add to the systems contract fixing page to fix the covered value too
      • show the covered widget everywhere (adding sales)
      • on recyclings entry, when fg-pdx is choosen, disable the covered widget and set it to false
      • make sure that editing old sales before coveredness works correctly
        • did not work with #227115 at least
          • situation is: edit a line item with nil covered value, but isn't coverable...widget is disabled and stays on nil, sooo, it doesn't accept the line item. should just special case it to set it to no in this case.
        • works fine on transactions where the line item is coverable like #227114
      • make sure false for things that aren't coverable
      • add the cleanup code mentioned on #15846

queue + 1

the library release - May 7th?

queue + 2

the unimportantish release - May 21st?

  • #18266 default the individual report and logging staff hours forms
  • #17932 tricky to log 0 hours when the schedule expects hours
  • use store credit like things for gift certificates
  • #14985 privilege to role mapping for database users
    • User:Ryan52/roles
    • ack "(requires_(role|staff)|is_staff|has_role)" app/
    • #16933 privileges for tech support role
    • #15050 people with TECH_SUPPORT role should imply the CONTACT_MANAGER
    • #17210 store or at least store admin should imply contact manager
  • link to old system IDs on the systems page as well
  • get fgdb.rb able to be set up by new freegeeks and new coders
    • #15523 fgdb can't be set up from scratch atm (broken devel data)
    • #14227 Fix docs on how to install FGdb
  • cashier code enhancements
    • #16671 ask for cashier code on destroy
      • want to redo destroy in fgdb anyway
    • #16672 permissions verification should be done on the ajax forms against cashier code
    • #16673 eleminate cashier_created_by?
    • #15498 should not recheck the same cashier code
    • #18046 cashier code on disbursements?

queue + 3

the cool toy release - June 4th?

  • handle expired store credits in a smart way
  • #17255 overtime report
  • #17031 integrate meeting-minder functionality into skedjulnator
  • Replace SOAP usage with [1]

queue + 4

what's left release - June 18th?

  • #14861 swap computers (tech support)
  • I WANT A TEST SUITE
  • db cleanups
    • gizmo_types.effective_on has a silly default
    • workers.contact_id needs to be unique
    • users.contact_id needs to be unique
    • flatten contact_method_types (add a category)
    • created_at should be NOT NULL
  • changes to the contact widget
    • need to think this through.
    • should take these tickets into account:
      • #13061 auto search for contacts when creating a contact
      • #14840 contact search kinda sucks
      • #14827 FGDB: force search on create
      • #14828 FGDB feature request #2
      • #15034 add show more button on contact search
  • fix up form_has_not_been_edited
    • #15921 form_has_not_been_edited isn't called on edit links, I think
    • #15922 form_has_not_been_edited shouldn't be called on destroy
  • #16108 gizmo_types with same name and different effective date ranges should act sanely in reports

junk

  • #17796 database - Committed Hours & PTO
  • go through remaining trac tickets:
  • old TODO list
  • my crazy ideas that will just make fgdb.rb that much more awesome
    • #16514 create a plugin that will improve partial updates (by freezing attributes)
    • #16513 create a plugin which will make records associated by has_many (optionally?) saved when the parent record is saved
      • looks like it's already in rails itself... :autosave
        • need to test though. and why did none of the sites that I found in the process of figuring this out show it?
  • release utilities
    • the log rotate script breaks auto-update: tee: /var/www/fgdb.rb/log/auto-update.log: Permission denied
    • get continuation to work with multiple branches
    • get continuation running with test-migrate
    • the auto-update script is connected to my home dir (because of the devel checkout), but it shouldn't be.
    • I want all changes on a release_X.X.X branch (after the initial branch) to get their own tag. this would involve running ./script/mini-release (new script?) when making a direct change, and this would affect the output of ./script/version. mini-release would also close the ticket(s) (by pushing the tag, I guess). also, this would mean that pushes on release_X.X.X branches wouldn't close the tickets. this would also affect the changelog workflow probably.
  • I wonder, could we have root mail go to an RT queue.

laptop todo