1) Note Taker Volunteer

Tom agreed to take the notes.  

2) Agenda Review

Item 5 was added to the agenda

3) Administrator's Manual review process/thoughts

CO said the process is going okay, unless key staff members are out of the office.  Sometimes we may need to rearrange the round-robin schedule.  IL will send feedback to Sharon in CO by next Monday noon.  Toni reported to Darci that both the schedule and the spending for the PAM are about on schedule.
 
Decision:  stay the course, with minor modifications as needed.     

4) Development activities
    (RFP, vendor selection, schedule, etc)

    a) User's Manual Update:  TX has created a list of things they would like to have updated.  Someone in Texas has really tried to test all the instructions contained in the current user’s manual, and noted all the problems. This list of issues and potential problems has not yet been shared with the other states.  Toni has indicated that she would be available to do the updated user’s manual.  Probably less than 40 hours of work for the update.  Four types of editorial changes:  changing Oregon-specific information to info appropriate for a different state; typos; procedures that are now incorrect; editorial changes that are just wording things differently.
 
Decisions: 

• We need to document all of the suggested changes that will affect the multi-state master document. 
• Toni is our first choice to update the master copy of the manual. 
• Texas will take the lead on creating a list of itemized changes to the master copy. 
• Mid-February is our target date for having a list of itemized changes to send to Toni. 
• Add this item to the agenda for our next meeting.    
  

    b) Cloning/Upgrading automation scripts: 

            A short discussion occurred regarding the need/process/timeline of upgrading Plone. Plone 3.0 probably will be released in April 2007, with another major release.  It will focus on the user interface; therefore, it may make our Plinkit user’s manual woefully out of date.  Version 2.5 is current, and we are running version 2.1.  The Plone community is on a six-month schedule for major releases of new versions of Plone.  There are some strategic advantages to being one major release behind the current version of Plone.  The Plone community supports the two most recent major versions of the software.  If we are running something older, the community probably would simply suggest that we upgrade to the current version.  

We need a semi-formal RFP process.  We want to have it address our needs but not be too cumbersome for potential responders.  Ask potential vendors to provide a list of references and previous similar projects.  Articulate the deliverables and the timeline for delivering them.
  
Decisions: 

• Develop an RFP and review process for this item before we tackle the larger issue of recurring events.  Darci will come up with an initial draft by 1/22.
• We will use the email list to discuss and hone the RFP. 
• We will strive to have the RFP ready by Friday, Feb. 2. 
  

    c) Recurring Events Product for Plone 2.1.x and 2.5:  

When it comes to RFPs, the rules and regulations of BCR apply, because they are the fiscal agent for Plinkit.  Ellen Fox at BCR may be a good resource person for this project.
 
Decisions: 

• Wait until the cloning/upgrading automation scripts process is underway before tackling this issue. 
• We may want to develop a six-month plan for upgrading the version of Plone we are using for Plinkit. 
• Sharon will contact Ellen about the RFP process.        

5) Content for Plinkit.org, the Plinkit Project Website: The website will be designed primarily for staff members from the partner states, especially the resource section, which requires a user to logon.  We will use the issue tracker in this area, too.  We also will include informal but articulated thoughts about key issues regarding the Plinkit project.  We will want to highlight libraries from each state that are successful and satisfied users of Plinkit.  Maybe we should include some before and after screen shots of a Plinkit library’s website.  We also could include some testimonials from Plinkit libraries.  People should feel free to contribute to the resource section to share training or marketing materials, etc..   This would be a great place, for example, to put a 6-month planning document/section.

Decisions: 

• Include a section that highlights the Plinkit libraries in each state, including testimonials.   
• People should feel free to add to the Blog but before publishing (making it public), should email the Project Coordinators for a quick approval. A more formal process for publishing content can be developed as needed.

6) Next Meeting Date

Friday, Feb. 2, 2007 beginning at 1:00 p.m. PST, 2:00 MST, and 3:00 CST.  Invite the Technical Committee members to participate in this meeting, too.