Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
01.26.2007 F2F Agenda
Revision as of 18:50, 23 January 2007 by Unnamed Poltroon (Talk) (→Agenda for build issues meeting)
Agenda for Higgins face-to-face meeting in Provo, Utah, January (23), 24-26, 2007.
Location Novell's office. 1800 South Novell Place, Provo, UT 84606, (801) 861-7000
The event will start Wednesday January 24th at 1:00 and end Friday, January 26th at mid day.
Hotel Several of us are staying at the Conference Center in Provo map.
There are also a few hotels within walking distance (may have to deal with snow though) The markers are off. From left to right,
- The La Quinta is across the street (west) and has a visible swimming pool.
- The Fairfield has a blue roof
- The Hampton is next to (east) of the Fairfield
- The Sleep Inn is next to (northeast) of the Hampton
Weather Dress warm. It may be cold.
Pre-meetings (build issues) Jan 23-24
- Working build clean-up meetings.
- Tuesday, January 23rd 1:00 pm - 6:00 pm Building H 5th floor
- Wednesday, January 24th 9:00 am - 12:00 pm Building H 1st floor
- Novell team will escort from lobby. If late call 801 380 8760
Expected Attendees
- Dale Olds
- Jim Sermersheim
- Mary Ruddy
- Mike McIntosh
- Paul Trevithick
- Tom Doman
- Tony Nadalin
- Duane Buss
- Daniel Sanders
- Nataraj Nagaratnam
- George Stanchev
Agenda for build issues meeting
Notes are in bold
- Define developer's experiences (use cases). Something like:
- Getting code from CVS:
- Using Eclipse
- anon and committer psf files (one per component) must be kept up to date.
- would be good to have the ability to upload files to the wiki, but nothing easy in place yet.
- Using other CVS tools
- Document URL's to each project/component
- Using Eclipse
- Build steps
- General build requirements
- Able to manage from within eclipse without dual editing build files
- Able to build from the command line
- Should be no absolute class names
- Shouldn't require eclipse-specific jar files (only stated dependencies)
- Should build when eclipse is not installed
- What targets are required?
- jar for any consumable component
- war file for WS deployable components
- debug versus binary
- javadoc
- eclipse plugin target
- this probably requires ecplise to be deployed -- hopefully this can just be a target that is selectable
- Build prerequisites
- Gathering dependencies
- Setting up environment (incl. env variables)
- Building in Eclipse
- Using Eclipse build
- Using ant inside eclipse
- Building from the console
- General build requirements
- Getting code from CVS:
- Standards for consistent developer builds
- Do we need to support all the use cases above?
- Instructions for getting code
- Instructions and/or scripts for build prerequisites
- Instructions on building
- Is the output the same as the nightly build? (Jar file naming, Jar file versioning, Javadoc copyright)
- yes
- Project Packaging and Terminology
- Packages versus Projects
- Should each different package be it's own project, or should a project contain multiple related package?
- i.e. Why are there multiple IdAS projects?
- projects are based on architecture
- plugins have to their own projects
- unit tests should be their own project'
- Should each different package be it's own project, or should a project contain multiple related package?
- Packages versus Projects
- Dependencies
- Delivery/Distribution (how do people get them?)
- Put them in CVS
- The hope is that we can integrate this into the standardized build system. Hopefully we can build eclipse projects for the dependencies, and refer to those.
- Put them in CVS
- Placement for builds
- see above
- Do we require additional Eclipse plugins?
- see above
- Delivery/Distribution (how do people get them?)
- Review Nightly build needs
- Jar file naming
- This is a side-effect of the way we name our eclipse projects
- We could either change our eclipse UI project names to be short names, or look for some kind of eclipse setting to let us control the jar file names
- Proposal is to name like higgins<component>.jar
- Side topic is re-alignment in cvs (higgins versus trust framework)
- Jar file versioning
- filename should have version numbers
- revision version # only updates when an update breaks an older application
- Dale wants to reflect any change in the name
- review eclipse guidelines for this
- revision version # only updates when an update breaks an older application
- filename should have version numbers
- War file delivery
- War file includes dependencies
- Mike needs to walk thru the steps to list dependencies, will list the dependencies. Mary will then run them through IPZilla
- War file includes dependencies
- Review Javadoc copyright
- We should seek guidance from eclipse
- Jar file naming
- Delivery of released deliveries.
- What's the criteria for calling something a "release"
- Generally tied to milestones
- Component owner updates release number
- We don't have a release yet
- What's the criteria for calling something a "release"
- Requirements for package-managed builds
- Eclipse update manager
- RPMs
- JPackage
Main Meeting Jan 24-26
Expected Attendees
- Abhi Shelat (IBM)
- Dale Olds (Novell)
- Daniel Sanders (Novell)
- Duane Buss (Novell)
- Jim Sermersheim (Novell)
- Igor Tsinman (Parity)
- Mary Ruddy (SocialPhysics, Parity)
- Maxim Kopeyka (Parity)
- Mike McIntosh (IBM)
- Nataraj Nagaratnam (IBM)
- Paul Trevithick (SocialPhysics, Parity)
- Pete Rowley (Red Hat)
- Tom Doman (Novell)
- Tony Nadalin (IBM)
- George Stanchev (SERENA)
- <add your name>
Wednesday Agenda
Noon: Development Processes & Stds [30 min]
- Review/Summarize results of "Build Day" [Jim]
- Component Owner responsibilities [Paul]
- maintain automatic (nightly) builds
- maintain all columns in your "row" here: Components (javadoc, psfs, etc)
- maintain "to-do" list for each component
- guarantee quality though unit tests and other quality assurance techniques
- Moving all Higgins interfaces/APIs back to JVM 1.4 [Tony]
HBX: I-Card/Identity Selector [Abhi 30 min]
- Additional local folks may join us for this segment
- Demo ????
- Discussion of threat model to running the card selector in the browser itself
1pm: Privacy/Data Policies [Duane,Tony, Mary Rundle 2 hrs]
- Develop the Higgins' roadmap in this area
- RP Security Policy
- Is the goal Higgins policy = [MSFT CardSpace policy + Idemix]? More than this?
- Relationship to other efforts (e.g. Liberty/CARML)?
- User's data privacy policy --not sure what the term for this is
- e.g. Mary Rundle's ideas (from Berkman Center) based on international data protection law
- Identity Provider policy --not sure what the term for this is
- Relationship to Liberty/AAPML
- Icons for User Data Protection Policies [Mary Rundle 60 minutes]
3pm-5pm IdAS [Jim: 4-5 hours continuing Thursday morning]
- org.eclipse.higgins.idas.model refactoring (2 hours)
- We're adding the APIs in 171295. Is there anything else we need them for (getMetadataModel)?
- Should the interfaces in the model package be used to produce instances of context data (digital subjects, attributes, filters, modification lists, etc.)?
- Adding matching rules to the model
- This overlaps some of the Data Model discussions below
- Attributes should list the comparators they support 171312
- Comparators should specify the assertion value required
- IFilter refactoring (1 hour)
- Update operation refactoring 167978 (1 hour)
- Topics likely to be deferred (1 hour)
Thursday
9AM: Continuation of IdAS Discussion (see above) [2+ hours]
11AM: Data Model & Related Topics [Paul 60 min]
- Valery's Display Data Proposal and discussion
- Motivation for "in-context" metadata vs. "external" metadata
- Semantics of display metadata
- Relaxing the OWL-DL constraint
- Allow us to define our own kinds of Classes (e.g. for LDAP AUX classes, etc.)
- Allow us to better "type" attribute data values (e.g. phone number masks (xxx)-xxx-xxxx) using XML Schema (I think)
- "Well known Contexts"
- Paul's unusual and possibly misguided ideas about how some kinds of identifiers (e.g. email, telephone numbers) should be modeled
- IdentitySchemas.org update
Noon: Lunch
1pm: Registry Issues [Jim, Tom: 2 hours]
- General Registry thoughs msg01249
- IdAS and CP needs
- Configuration
- "Usable" Context Ref URI
- Other Registry needs?
- Stackable CP's 171294
3pm: OSIS and Interoperability [Paul 30 min]
- presentation of Interoperability Space
- Discussion of Higgins interop demo schedule
3:30pm: ISS Client UI [Dale 30 min]
- Bootstrapping option [Dale]
- Eclipse RCP vs. ??
- Platform/tool/runtime issues [Paul]
- Potential for collaboration with Ian Brown (developer of the Safari selector) [Paul]
4pm: OpenID Context Provider [Dale, Tom, Jim 30 min]
- Implementation options (alternative use cases we could support)
- Call in segment with Dave Recordon on West Coast?
4:30: SAML Context Provider [Dale, Tom, Jim 30 min]
- Interest in creating this?
- Help from OpenSSO project
- Resources?
Friday
9AM: Higgins' and other Communities [Mary 60 min]
- A discussion whose proposed outcome is a wiki page characterizing the Higgins project's relationships with other communities.
- See draft here: Related Communities
IP update [Mary 20 min]
Principles of Identity Paper update [?? 10 min]
Milestone 0.7 Progress/Review [Paul 15 min]
- Step through each component and get an update (even if the update is "stuck in IPzilla process")