First commit for git repository after installing abtt on new abtt vm …

…of superpickle.

.svn/entries

@@ -0,0 +1,203 @@
+9
+
+dir
+274
+svn+ssh://pickle.andrew.cmu.edu/svn/abtech/trunk
+svn+ssh://pickle.andrew.cmu.edu/svn/abtech
+
+
+
+2009-09-01T01:51:56.523011Z
+274
+mreiss
+
+
+svn:special svn:externals svn:needs-lock
+
+
+
+
+
+
+
+
+
+
+
+03765842-7118-0410-bc89-acf00678854e
+
+test
+dir
+
+app
+dir
+
+log
+dir
+
+Rakefile
+file
+
+
+
+
+2009-09-04T19:37:33.000000Z
+17f2f134da4cd31ea095d5868ca89e86
+2006-07-16T21:37:37.913648Z
+3
+saagarp
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+307
+
+READMEbackup
+file
+
+
+
+
+2009-09-04T19:37:33.000000Z
+c07a66de7f02d18ba959f12d32bb300f
+2009-06-01T05:52:06.143813Z
+225
+mreiss
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+187
+
+components
+dir
+
+db
+dir
+
+vendor
+dir
+
+tmp
+dir
+
+script
+dir
+
+config
+dir
+
+doc
+dir
+
+TODO
+file
+
+
+
+
+2009-09-04T19:37:33.000000Z
+866b0a119e5a98f5ed4768a3bdf20bc2
+2008-09-18T19:08:14.667088Z
+169
+saagarp
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+2815
+
+lib
+dir
+
+design
+dir
+
+TODOproduction
+file
+
+
+
+
+2009-09-04T19:37:33.000000Z
+9f2fc91b4dd6c23fc550941523b3cfc0
+2006-08-29T03:06:44.445423Z
+24
+saagarp
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+106
+
+public
+dir
+

.svn/format

@@ -0,0 +1 @@
+9

.svn/text-base/READMEbackup.svn-base

@@ -0,0 +1,2 @@
+mreiss on 6/1/09
+Pickle now has a cron job to dump the tracker's full sql db twice a day. This is clearly not a scalable solution. But hopefully it might keep us safe for a little while.

.svn/text-base/Rakefile.svn-base

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'

.svn/text-base/TODO.svn-base

@@ -0,0 +1,89 @@
+abtt todos:
+
+html email processing: 7151
+year abstraction sucks
+UI
+-- better location/equipment selector
+-- better filters
+
+develop features:
+-- email_forms
+
+trash useless parts
+-- bills
+
+
+fix event edit after using "new event"
+fix quickrecord
+escape all url_fors
+:escape => false  on url_for
+
+Unrelatedly, the view_dates page doesn't properly order sub-events by date.  For example, look at
+https://abtt.hackish.org/event/view_dates/6.  You should probably fix this, Saagar.
+
+Finance
+- allow account/unpaid to take a date in the form of 10/11/06 when creating a paid invoice
+
+events page
+- 'create new' should only be visible to some people. 
+- we should think about what statuses we want on the page 
+  - i think i'm going to do this part with colors like two similar alternating
+    colors for normal events and some different colors for different statuses.
+    for example, cancelled events might be greyed out, required action events
+    might be red......what else might we want to pull out?
+  - is it possible that we might want to restrict viewing of cancelled events?
+    or perhaps of statuses in general?
+
+members
+- 'listing members' needs to be a different title
+- show and destroy unnecessary here too. destroy can be an option under edit.
+  - click on line to edit? (i kindof like this idea, can you tell?)
+- in kerbid, maybe we should truncate the @andrew.cmu.edu? 
+  - when we have @abtech support, just leave it at @abtech
+- created_at and updated_at are probably unnecessary.
+- is nickname necessary?
+- probably roles should not be on this chart, or even displayed publically at
+  all.
+
+
+organizations
+- 'listing organizations' change title
+- show and destroy unnecessary, destroy under edit, click line to edit, etc
+- is pagination necessary?
+  - if we deem it so, make sure the next page button is in the same place
+    every time.
+
+calendar
+- i think maybe calendar and event view should be integrated with each other.
+  - or if we integrated it with events, we could have one month with info along
+    the side
+- i don't think the 'how to tweak the generated ics file' info is really
+  important. if people are like me they will just generate the whole file and
+  smile a lot.
+
+code reuse between event/record and event/quickrecord
+attachments from emails
+
+fix tabs in code (4-space everywhere)
+fix poor initial code (global variables, redirects)
+-- views
+-- models
+-- helpers
+use of rails functions rather than input fields
+
+make edit self on members list work
+
+delete filter
+clean up css [planner.css]
+make event views (and everything) use Time, not DateTime
+
+       http://compserv-wiki.andrew.cmu.edu/noauth/isam/PubcookieSetup
+
+-- migrate abtt
+tracker stuff:
+   rainsite support?
+fix dates
+delete quickfilter
+edit invoice quickfill
+edit years
+call/strike details (to techroom, none, etc)

.svn/text-base/TODOproduction.svn-base

@@ -0,0 +1,6 @@
+cron job to backup database
+
+ruby gems:
+  rails
+  icalendar (patch with conversions.rb from doc/)
+  rmail

READMEbackup

@@ -0,0 +1,2 @@
+mreiss on 6/1/09
+Pickle now has a cron job to dump the tracker's full sql db twice a day. This is clearly not a scalable solution. But hopefully it might keep us safe for a little while.

Rakefile

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'