2010-07-26 Web Design technology status call

Committee: 
Web Design
Meeting
Date: 
Mon, 07/26/2010 - 00:00
Location: 
Agenda: 

Agenda:

 

1. Subteam status reports - first and third Mondays - any urgent items?

* Office status (Josh)

* Google Analytics and Theming (Doug)

* Social Networking (Doug-acting)

* Content (Georgette)

* Business model (Ann)

2. Review last meeting's minutes for action items

3. Technology status reports - second and fourth Mondays

-- Current site

Any outstanding issues?


-- Drupal 6 (Walt)

• Source code control system (prereq for going live)
• Progress since last call
• What still needs doing
• Kipp's work orders - status
• Plan for final testing and migration, training and communications

-- ebase / CRM (Walt -acting)

4. Set goals for next couple of weeks

5. Meeting schedule: weekly calls until launch?
Next meeting: phone or office?

6. Parking lot (for later discussion):

Groups audience: 
Attendees: 

Walt, Bill, Josh, Ann

Minutes: 

1. Subteam status reports - first and third Mondays - any urgent items?

• Office status (Josh)

  • Josh to send me mockups of reports. Will give dream version ... may want tender type too but not a show stopper. Have to balance credit card transactions each day. Walt - what about entering front end stuff in Ubercart too? Would that make processing easier? Time is lost getting stuff into Quickbooks (manual reentry of orders now).
  • Kevin will finish mockups of other pages.

* Google Analytics and Theming (Doug)

* Social Networking (Doug-acting)

* Content (Georgette)

* Business model (Ann)

2. Review last meeting's minutes for action items

Timeline for migration - Walt didn't get system rebuilt yet.

3. Technology status reports - second and fourth Mondays

-- Current site

Any outstanding issues?

-- Drupal 6 (Walt)

  • • Source code control system (prereq for going live)
o Walt has account on Github (free for our level of usage, modest charge otherwise)
  • • Progress since last call
  • • What still needs doing (doesn't function quite right, doesn't look quite right)
o Not using any of nynjcustom in D6! However, may have to use if for pricing on catalog pages (member and list prices, checkout process for hiding click for shipping and handling) -- Bill or Kipp. We are eliminating 10% registered user discount.
o Discount module - still not fixed. (There are 2 discount modules in D6, both broken.) Walt to assign to Kipp. (Do it so it works with Bill's views. List Price and Price fields - discount should appear in Price field.)
o Theming for login/register page (tabs in weird colors) - also on some other pages for anonymous user only (can't find images - url built with double nynjtc.org - Bill looking at it)
o IE not working in some cases (store checkout) - need to stress test in D6 as it may be fixed there.
o Additional pages that need theming - register/login page (buttons at top), donate page (make it look like D5) - Walt to assign to Kipp
  • • Kipp's work orders - status
o Waiting for better specs from Josh/Kevin
  • • Plan for final testing and migration, training and communications

o Rebuild this week then reimport saved views --
 Copy /files
 Replace db with D5 db
 Run update (several hours)
 Bill imports views
 Test if we are back to where we are now; document anything we have to fix up at this point.
 Tiny nits Walt knows about - modules new on D6 that need initialization after reload.
o Set up a call to filter the views and determine which to include in the D6 system
o Stress test -- for staff to test, it should be at beta level ... use test credit card and ignore the error message
o Create announcement materials (Georgette)

-- ebase / CRM (Walt -acting)

4. Set goals for next couple of weeks

5. Meeting schedule: weekly calls until launch? Start general call 15 minutes early.
Next meeting: phone or office?

6. Parking lot (for later discussion):
Bill asks: "Do we need to have our status calls in the middle of the day? It breaks up the day too much." -- re-evaluate after launch.