Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "May 20-21 Seattle F2F Agenda"
(→12:30 - 1:00) |
|||
| Line 69: | Line 69: | ||
=== 12:00 - 12:30 Lunch === | === 12:00 - 12:30 Lunch === | ||
| − | === | + | === 1:13-1:30 === |
* XRI-based identifiers? | * XRI-based identifiers? | ||
* Accessc Control prep? | * Accessc Control prep? | ||
Revision as of 16:13, 20 May 2008
Higgins face-to-face meeting in Seattle, Washington, May 20-21, 2008.
Logistics
- Location:
- Time: The event will start Tuesday at 9:00 AM and end Wednesday at noon.
- Action Items are indicated by the presence of "(AI)" on a line and the owner of the action item is in bold.
- (AI) Jim will turn the action items into bugzilla entries as appropriate
Expected Attendees
- Jim Sermersheim - Novell
- Paul Trevithick - Parity (by phone on Tuesday, in person on Wed morning)
- Drummond Reed - Cordance/Parity
- Michael McIntosh - IBM
Attending by phone
- Bruce Rich
- Paul Trevithick (tuesday)
Participant Passcode: 685641
US toll free: 877-421-0038
US: 770-615-1254
Attending on IRC
- Tom Doman
Tuesday
We will track at least the agenda on the #Higgins IRC channel. If you wish to call in for an agenda item, please let us know on the #higgins IRC channel
9:30-10:00 Welcome, Introductions, Agenda [Mike, Jim]
- Introductions
- Eclipse ground rules
- Agenda bashing
10:45 - 11:15
- M1 Status
- Complete -- release is tagged complete
- Two components were failing the build.
- Duane fixed the failure introduced by vkokhan
- (AI) Brian will have Peter review these
- Higgins_1.1M2 Planning
- 20080613 is target date
- [1] is the project plan page
- How should we deal with the seemingly snowballing effect we get with simply pushing unaddressed items from release to release?
- Maybe make a milestone called "backlog" or something. That way we can keep bugs associated with a release to a reasonable number, and more well prioritized.
- (AI) Brian will create this release tag
- (AI) All People should put all their bugs into that backlog that aren't tied to a specific release
- Maybe make a milestone called "backlog" or something. That way we can keep bugs associated with a release to a reasonable number, and more well prioritized.
- Automated Testing Process Planning
- Eclipse has some test reporting tools
- Eclipse also has servers available for testing
- Need to set up at least one example of a project that does nightly testing
- (AI) Mike volunteers to help with this, but needs guidance.
- (AI) Paul will find out how other eclipse projects do this (starting with Bjorn)
- Where do the test projects reside?
- Mike proposes they should go under test (peer to plugins)
- (AI) All People should move their test projects over there
- Mike proposes they should go under test (peer to plugins)
- (AI) Mike volunteers to help with this, but needs guidance.
11:25 - 11:35 Development Processes
- Mike suggested we need more doc about our development processes
- unit tests --the .test projects should be in the "test" folder in SVN (not where they currently are)
- who gets notified when a nightly build fails? (where is this documented as to how this is changed)
- starting to use the voting mechanisms in Bugzilla to prioritize
- Here's all the doc we have now: Higgins Committers and Contributors
11:35 - 12:00 SAML2
12:00 - 12:30 Lunch
1:13-1:30
- XRI-based identifiers?
- Accessc Control prep?
1:00 - 2:00
- Access Control
- Interested in discussing: (Jim, Mike, Bruce, Paul, Drummond, David Kuer-McLaren, Tom, Duane)
- AuthZ as Entities
2:00 - ?
- IdAS backlog is at IdAS Backlog
- IdAS Model as Entities
- SAML 2.0 IdP (Markus and Paul?)
- i-Card Extensibility (including PIN based protection)
- IdAS: Complex values as Entities
- IdAS Changing metadata to attributes
- Coming up with global identifiers for all idas elements