Present:

Steve Loranz

Karen Young

John Billings

Dorian Breuer

Next Meeting Dates:

• Monday, Feb 6, 9PM-10PM @ ILGP conference call number/code - Phone Conference call meeting for web team - ILGP Plone Administrator's policies initial meeting [(401) 694-1602, Code 525589#]
• Tuesday, Feb 21, 9PM @ ILGP conference call number/code - Phone Conference call meeting for web team - updates and progress reports meeting [(401) 694-1602, Code 525589#]
• Sunday, Mar 5, 10AM - 1PM @ CAG office - Webteam in person 'sprint' meeting to strategize on web work and collabrate on website work. 
• Tuesday, Mar 14, 9PM @ ILGP conference call number/code - Phone Conference call meeting for web team - updates and progress reports meeting [(401) 694-1602, Code 525589#]

1. Discussed Goals of the Web/IS&T team (John, I read your notes! Thanks)
1. Operational stability
2. Self Service
3. Flexibility
4. - IT Services
   (polls, surveys)(fax calling)
5. Low cost - Money/Staff
6. Small and low budget as possible
2. General Approach: work on projects in parallel.
1. It was agreed in principle that a 'parrallel' approach to completing different tasks for the website should be used. The big example discussed was a big structural proposal for work by Steve L. to impliment a comprehensive 'authentication engine' behind the site on the one hand while also working on shorter term and important projects such as development of an on-line comprehensive web database and other shorter-term projects that need completing.
3. Proposed projects for the website:
1. Authentication system/engine
1. Steve proposed a comprehensive authentication that had the elements summarized (sketched) below:
1. Join  the ILGP web form - linked to paypal/payment system, sends info to the LDAP or authentication database
2. Authentication team (someone from Web team, memberhsip steward?, Exe?) approves member as 'joined'
3. Once approved, Member given access to various levels of site: basic user (submit comments, read various areas of site), local/committee user (access to committee or local or candidate area of website, various rights, some posting rights), reviewer for site (access to publish in various parts of the site), Admin (variou srights around site), full admin (root access to server/Zope interface...)
4. Levels of access above  basic would necessatite the user to fill out another form - the website account form
5. The LDAP woudl automatically assign the correct level of access for users based on pre-defined settings for various 'groups' as somewhat detailed above in #3.
2. System would take alot of resources to develop and would require the help of other programmers to help develop while less skilled admins could take some of the administrative burden off of Steve and other developers
3. While this system is being developed, the current web account web form located here: http://ilgp.org/groups/information-services-technology/forms/newAccount/