Error!

Spaces has been migrated to the cloud. Please go to https://ucla-confluence.atlassian.net to update your space/s.

IT Services has migrated the content of spaces.ais.ucla.edu to Atlassian Confluence Cloud. Please visit https://ucla-confluence.atlassian.net to update your space/s. Spaces.ais.ucla.edu is now in read-only mode.
Child pages
  • SignetWorkGroupCall20081024

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

Signet Work Group Call Oct 10th 2008

Meeting Notes

  • At start of call about 15-20 people
  • Next steps for Signet until end of year
    • hooks and plugin are pretty much done
    • they were going to begin webservice part now
    • do as much as they can until they can't do anything anymore
    • integrate with co manage? ppl want this?
    • ppl feel that without a co manage wrapper signet is not useful
    • Tom said if Signet code base is needed it might be reused
    • Not sure who but someone said that they will still work part time on Signet even after funding and all support won't be gone
    • some sort of integrated interface?
  • Grouper integration with Signet
    • haven't really thought it throughly besides structure of code
  • Signet with ldap
    • with ldap you have to query for data and modify data for it to work
    • want a yes/no answer back like grouper
  • What happens when funding stops
    • not sure yet
    • everything will remain/internet2 will continue to host it
    • Need people to commit and project might continue
  • action items
    • webservice interface
    • integrate eddy
    • hooks/plugin example
    • alberts use case
  • No labels