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.
Difference between revisions of "Aperi SNIA Production Ready Task Force Workgroup"
(→Upcoming meetings:) |
|||
| Line 23: | Line 23: | ||
== Upcoming meetings: == | == Upcoming meetings: == | ||
</FONT> | </FONT> | ||
| − | '''Next meeting: | + | '''Next meeting: Friday, June 20, 2008. |
<FONT COLOR=maroon> | <FONT COLOR=maroon> | ||
Revision as of 13:18, 17 June 2008
| Dial-in number:
Toll Free: 877-421-0030 ; International: 770-615-1247 ; Passcode: 111587 |
| Default schedule:
- Every Two Weeks, Friday 1-2pm PT/4-5pm ET (temporarily suspended until SNIA meeting) The Agenda will be posted prior to the next call. |
Contents
Upcoming meetings:
Next meeting: Friday, June 20, 2008.
Agenda
- Prioritise the list
- Think of ways that Aperi can help SNIA Production Ready Task Force with these issues. For example:
- Use Aperi to help drive momentum on HDR
- Use Aperi to test CIM implementations
Key Documents Under Discussion
Minutes from previous meetings:
2008/05/09
- Participants
- Dave Wolfe
- Al Heitman
- Martine Wedlake
-
- Notes
- The slides have not been completed yet; so nothing to go over. Martine will send out slides to folks in email prior to presenting them to SNIA. Martine still working on scheduling time with SNIA PRTF.
- We decided to temporarily suspend the meetings until we have the walk-through with SNIA with the set of feedback/comebacks from that meeting.
2008/04/25
- Participants
- Duane Baldwin
- Dave Wolfe
- Al Heitman
- Craig Laverone
- Martine Wedlake
-
- Notes
- We went through the last of the items with a lot of attention spent on where Aperi can help the host based profiles and help increase SMI-S adoption by providing re-usable components that use SMI-S for other products which want to leverage SMI-S.
- Next steps are for Martine to contact the chairs of the SNIA Production Ready Task Force and ask them how they'd like us to proceed with the material; e.g., simple power point, white paper, meeting, etc.
2008/03/14
- We added a few items to the list of problems and categorized them into three rough categories: Specification/SMI-S Issues, Technology Issues and Implementation/Adoption Issues.
- Next Steps:
- Continue to add items to the list and categorized them. We need broader input than we have had -- only a handful of people have participated in the workgroup to date, and we really want to try to represent a complete view of Aperi membership. Please send me (martinew@us.ibm.com) your ideas to add, or edit the wiki.
- Prioritise the list.
- Figure out where Aperi can help. For example, providing HDR support in Aperi can help drive momentum in industry, or providing client support can help test providers, etc.
2008/02/29
- We went over the initial list of items to understand what has already been captured.
- The team will now think up new items to add to the list and send them to Martine.
- In our next meeting, we'll start to determine categories of items to group the issues into.