2009-01-28 Wiki Strategy Meeting Notes

Owned by David Walker (Unlicensed)
Last updated: Mar 04, 2009 by Curtis BrayVersion comment
2 min read

2009-01-28 Wiki Strategy Meeting Notes

Attendees

  • Kirk Alexander
  • Curtis Bray
  • Brian Donnelly
  • Charlie Turner
  • David Walker

Overview of SmartSite's current wiki capabilities

  • There are two wikis used by the SmartSite community.
    • Confluence is used by the project members.  The global Sakai project also uses Confluence, hosted at Berkeley; it's slow.
    • SmartSite includes a simple wiki.  It's good for straight collaboration on text, but does not offer the editing and formatting capabilities of Confluence.
  • SmartSite has the ability link to Confluence, as it can to any web site.
  • SmartSite currently shares common user names and passwords with Confluence (although not SSO, as SmartSite is DistAuth and Confluence is CAS).  Next week, though, SmartSite will introduce SmartSite-only user names and passwords for non-UCD participants; those users will not be able to authenticate to Confluence.

Overview of Confluence at UCD

  • Confluence has been running at UCD since 2005.  Its initial purpose was to support internal documentation, but it now has about 80 spaces.
  • Performance is OK, but it may be hard to keep up in the future.  They observed that the global CAS wiki (hosted on a Confluence server) is "glacial."
  • There's been discussion of possible next steps:
    • Shibboleth
    • Provide SLAs to departments using Confluence
    • UCD currently has a unlimited user license

Current relationship between SmartSite and Confluence

  • SmartSite and Confluence can link to each other via URLs.
  • They currently share common user names and passwords via Mothra. That will no longer be the case next week, however, when SmartSite introduces the ability for SmartSite users to create (SmartSite-only) guest accounts.
  • SmartSite doesn't really have a common access management capability; Confluence does.
  • There's no straightforward way to share content between SmartSite and Confluence.
    • The Sakai community is moving to JSR 170 based repositories.  Brian will see what plans Atlassian may have along those lines.

Next Steps

  • We agreed that there is value in continuing this discussion.
  • David will schedule a second meeting to discuss what integration we'd like to see between SmartSite and Confluence.