| [higgins-dev] FW: Notes for Higgins dev call - May 27, 2010 |
|
FW: Notes for Higgins dev call - May 27, 2010 Attendees •
John Bradley •
Mike McIntosh - Azigo •
Mary Ruddy - Meristic •
Paul Trevithick - Azigo •
Hank Mauldin - Cisco LOGISTICS: • Time: noon Eastern (16:00 UTC) U.S. • Dial-in: 1-201-793-9022 passcode
7990866# AGENDA 1) [Paul] Higgins 1.1 release planning •
Project plan [1] Is this aligned with project metadata? •
Higgins 1.1 release milestone plan [2] - walk through
each solution and discuss •
New Higgins Overview 2010 [3] •
[Paul] We’re getting back into the routine of the
Higgins calls and getting 1.1 out there. A lot of work has gone into1.1
quietly and into 2.0. Will get 1.1 out and then continue with 2.0. Since it
has been a long time since we have done a release we are a little rusty. There
is a lot of documenting and testing to do. •
[Paul] The first thing we ought to do is decide what we
want to do about milestone 1.1M8. We could change the date to today, take a few
things off and declare victory. All code has been contributed. There were a
bunch of remaining tasks in bugzilla that we were intending to complete for
1.1. If we go through the 1.1M8 tasks, some are done, some are not. We need
to review all of these. •
[Paul] Look at http://wiki.eclipse.org/Higgins_1.1M8
- we’ll go through these line by line. •
[Paul] Mary do you know where the item “Higgins
website converts bugs.php to new look and feel” needs to be done? •
[Mary] Yes, I can do that if it has been assigned back
to me •
[Paul] Have updated some of these. Will finish the rest
off line. •
[Paul] Next is [2] Mary, I assume we are not ready to
schedule a release review. •
[Mary] Need to figure out what we need to do to
schedule a release review •
[Paul] Solution wiki pages need to be updated. For each
build are supposed to have downloads tables for each solution. Need to update
the wiki and downloads pages and make it auto build. Traditionally for the
iPhone selector, Marcus has been very good about this. On the iPhone selector
there are two versions, maybe we should drop the version that requires jail
break on the phone. •
[Mike] Agreed. •
[John] I volunteered to the IMI TC how we could add
the new iPhone invocation to the IMI spec. •
[Paul] I’ll reach out to Markus and ask him to
update this solution. I could rough out the new tables. •
[Mike] I’m a little concerned about how much work
there is and how much it could derail the developers. So I will ask Irena to
work on this. So it will not be done overnight. I’m hoping that after
she does the first one, and you verify it, then she can do the rest. •
[Paul] If she can just do what Markus does, that would
be good. There are developer conventions in the Higgins “How to get
involved” developer team page. There is guidance on how we do things. •
[Paul] July date… •
[Mike] Should leave the date there until we learn that
we can’t? Probably need to get all of this done before the release
review. •
[Mary] Yes, we need to get all of this done before the
release review. •
[Mike] Would Markus potentially be the person to
support the android phone? •
[Paul] There is a lot of interest in that. I will send
emails asking people to work on this. •
[Paul] After it is done, we can walk though the build
instructions to see if it works. •
[Mike] That is at least a week’s worth of work. •
[Paul] We should keep card sync as experimental. •
[Paul] I believe that the other services haven’t
been changed, so there won’t be much work to verify it. •
[Paul] Need to update the project meta data. •
[Mary] Need to make sure that only approved components
are used for builds. •
[Paul] As a first step, we will update all the
components pages. •
[Paul] For ecosystem reasons I was hoping we could
create energy for Catalyst. •
[Mary] It is the week of July 26. •
[Paul] If July is really September, that would be bad. •
[Mike] Doing this before Catalyst would be great. •
[Mary] The theme of this year’s Catalyst Interop
is Open Identity for Business. It will feature the US GSA profiles for IMI Information
Cards, OpenID and SAML. The focus is on business enablement rather than just
talking about protocols. We are featuring a healthcare scenario. •
[Paul] We can show the AIR and iPhone selectors. What
about the Android and Cloud selectors? •
[John] The government demo participants are just for
IMI compliant stuff. Need to get invocation into IMI and also cloud
characteristic. •
[Mary] How soon can you get the new invocation into
IMI? •
[John] Mike is working on it. It could take 12+
months. •
[Paul] So for Catalyst it is mostly the AIR selector.
We have a potential to demonstrate the Higgins and Azigo card selectors and
CardPress. When can we have an RP to test against? •
[John] We will probably start with the RSA RP’s.
Pam needs to make some changes to her font end software for accepting meta
data. •
[Mike] When I create a new issue, I can’t assign
it. It just goes to the component owners. Sometimes I want it to go to Irena.
(Will address off line.) •
[Mike] Are we meeting every week now? •
[Mary] Yes. •
[Paul] Bye. [1] http://www.eclipse.org/higgins/projectplan.php [2] http://wiki.eclipse.org/Higgins_1.1 [3]
https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/doc/org.eclipse.higgins.doc/Higgins-Overview-2010.pdf |