User:Ryan52/todo
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
- get $28.50 back from pizza
- get a mousepad
- User:Ryan52/maintenance
- freegeek-extras
- ASS
- disktest
- #19172 Reading SMART device error log for HDD testers
- keyboard tester
library (queue + 1)
- #14514 finish library stuff
queue + 2
- make store people happy with store credits
- replace ID's with checksums
- make a search for store credits, not gizmo returns, and associate store credits with contacts, so they can be searched for
- add to the store credit validation to compare contacts, and to warn if they are different, and to error if the checksum is invalid
- see doc/checksum.rb
- #19121 search by contribution
- #19088 turn covered on for sales
- fix up the worker type editing interface
- fix dedupping
- click on a date or worker_type in old records should put it into the form
- make it ajax
- check that I didn't break anything with the fix for #18319
- fix odd bug with leaving a NULL in the end date in the middle that richard reproduced. steps:
- set them to be "nother" from point A to C.
- set them to be "collective" from point C to point D.
- add in an inactive that goes from point B to point C, between the two.
- reports for taxes and workers comp
- #17796 database - Committed Hours & PTO
- #18537 add results of battery test to printme
- #18316 graphic reports are resource hogs
- #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
- #17231 "current" system ids
- get fgdb.rb able to be set up by new freegeeks and new coders
- cashier code enhancements
queue + 3
- 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
- #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
- fix up form_has_not_been_edited
- #16108 gizmo_types with same name and different effective date ranges should act sanely in reports
junk
- 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?
- looks like it's already in rails itself... :autosave
- release utilities
- 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.
- use multiple working copies from the production checkout: http://kerneltrap.org/mailarchive/git/2007/10/11/335637
- or just create a dbadmin user on arik
- benefit of possibility of having a key connected to devo.
- update Committing to FGdb after that.
- 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
- fix scrolling with touchpad
- install fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/206511
- then remove the exit 0 in /etc/acpi/lid.sh so that xscreensaver can work on lid close