• ViC Milestone 1 Release

  last modified May 3, 2007 by myddrin

The Virtual Collaboratory Project is porting its software to the Open Plans stack.  We made our first software release on 5/1, and here are the directions for installing it on an existing Open Plans instance or via a .deb for Dapper Drake.



From Tarball

These are short and sweet, and I'll clarify as people pose questions.


  • Download the tarball
  • Unpack the tarball and copy the subdirectories into your Open Plans Product directory
  • Restart Zope
  • In your open plans instance go to the portal_quickinstaller and install the ViC product



From .deb


  • Download the .deb
  • From a terminal run "sudo dpkg -i python-vicplone_0.1-i386.deb"
  • Zope, Plone , Open Plans, etc will be install to /opt/vic
  • Follow the directions in /opt/vic/results.txt to start zope.

Common Directions

  • Make sure your MailHost is properly configured, the ViC sends several emails that require use action.  If you can't get the emails
  • goto http://127.0.0.1:8080/vic
  • To create a new user click "Join" and fill out the form.
  • You will be sent an email asking you to confirm your email address, check your email and follow the directions.
  • Once the confirmation is sent, the default setup requires that the user be approved.  Since there is no email associated with the admin user, this is a little complicated, but gets easier once you give a user the Manager role for the ViC.
  • To do this, you will need to login as admin.  In the ZMI for the vic, look for portal_confimations, and "Edit" the last confirmation in the list.
  • This should be the approval for the user you just created.  Approve the user.
  • The email you provided for the user should get a welcome message
  • Now, still logged into the ZMI as admin, click on the vic instance and then the security tab.  Click on the local roles link and assign your new user to the Manager local role for the vic instance. 
  • From that point on, requests to approve users will be sent to this user.
  • There are several options that you can modify in the config.py file
    Constant Name
    Effect On ViC
     Values
    SITE_WIDE_PROJECT
    Sets the name of the project to which all users automatically belong
    Any String
    ALLOW_OPEN_POLICY
    If true, projects can have an open membership policy.  This means that users can join and leave the group without approval from a project admin
    Boolean
    DISPLAY_MEMBERS
    The membership type options that are available when creating a new project
    A tuple of uples of the form ( ("value", "text description"), ) .  The "value" must by the portal_type name of a valid membership type.
    DEFAULT_MEMBERSHIP
    The portal_type name of the membership type to choose by default.
    Any valid membership type
    MEMBER_WORKFLOW
    Determines if membership requires approval, or if like the open plans site, membership is open to any and all.
    Any valid workflow name, the vic ships with vic_requestmembership_workflow and vic_member_workflow

  • After changing any of the above values, you must re-install the ViC product in portal_quickinstaller