Minutes of the April 01, 2005 SV-BC Ballot Resolution Committee 0 Day 1 0 Month 4 0 Year 5 a Matt Maidment - Intel a Brad Pierce - Synopsys a Karen Pieper - Synopsys a Dan Jacobi - Intel a Dave Rich - Mentor Graphics a Rishiyur Nikhil - Bluespec a Cliff Cummings - Sunburst Design a Steven Sharp - Cadence a Don Mills - LCDM Engineering a Logie Ramachandran - Synopsys a Gord Vreugdenhil - Mentor Graphics - Francoise Martinolle- Cadence - Kathy McKinley - Cadence - Doug Warmke - Mentor Graphics - Tom Fitzpatrick - Mentor Graphics - Mark Hartoog - Synopsys - Surrendra Dudani - Synopsys - Greg Jaxon - Synopsys - Jonathan Bradford - Micronas - Stuart Sutherland - Sutherland HDL Agenda: +Review IEEE patent policy http://standards.ieee.org/board/pat/pat-slideset.ppt Reviewed. +Issue Resolution Process Karen provided the details of the process to resolve ballot issues: Schedule is very important. Absolute deadline to resolve issues is April 19th. Champions meet April 11th, this is the effective date when issues should be resolved . All issues are to be entered into the svdb. Committees to mark issues as resolved when appropriate. Resolved issues go to the champions as well as Stu for editing. They are then sent back to the committees for review and closure. Johny recommends the following order for resolving issues Small amount of time on low-hanging fruit Negative-high Positive-high Negative-medium Positive-medium etc. Committee must address all negative ballot comments. Committee decided only LRM changes go to svdb. All issues are to be tracked in spreadsheet. The disposition column is free form text explaining direction taken. Karen did not know the purpose of the WG Resolution field. She took the AI to check with Johny. The concept of decreasing consensus was explained as the outcome of the committee making a change that could cause more negative votes in the re-ballot. Committee agreed it is important to make changes that don't threaten consensus. [Post Meeting Note from Karen: "I have just traded mail with Johny asking about voting rights for the current ballot resolution process in the committees. Johny has determined that we are now acting as a Ballot Resolution Committee, and not as the technical committees. As a result, all of the voting priviledges need to be reset. I.e. anyone who shows up for the first 3 meetings can vote. After than, one needs to attend 2 consecutive meetings to gain voting rights, and 2 of the preceding 3 to retain them."] +Future Meeting Schedule Tentative: By Phone, Wednesday April 6th, 8am-10am April 4th Meeting: high priority issues first Easy issues need to get knocked down immediately as well + Issue Resolution For issues 205 & 207 Karen propsed that these issues be resolved with the response: "The committe read and considered this feedback. While it has merit, the committee believes it is not feasible to implement at this time." Cliff Seconds. No opposed. No abstain. Motion passes. AI: Cliff to review Item 266 and report status at April 4th meeting. AI: Steven & Brad will review and propose solution for issue 1 at the April 4th meeting. AI: Steven will review and propose solution for issue 6 at the April 4th meeting. AI: Gord to propose solution to issue 29 AI: Karen to provide Gord with SVDB account AI: Brad to assign issue 29 to Gord AI: Steven to propose solution to issue 35 at the April 4th meeting AI: Brad to propose solution to issue 91 at the April 4th meeting AI: Dave to propose solution to issue 216 at the April 4th meeting Issue 223 Brad moves to accept proposal as amended below: Change Section 22.2: local_parameter_declaration ::= localparam data_type_or_implicit list_of_param_assignments | localparam type list_of_type_assignments ; // from A.2.1.1 A.2.1.1 Module parameter declarations local_parameter_declaration ::= localparam data_type_or_implicit list_of_param_assignments | localparam type list_of_type_assignments; Cliff seconds. No opposed. No abstain. Motion passes. AI: Matt enter issue 223 into SVDB Issue 256 Brad moves that "Proposed change rejected due to other ballot issue (223) that has resolved this issue." Danny seconds. No opposed. No abstain. Motion passes. Issue 269 Brad moves to accept proposal. Cliff seconds. No opposed. Abstain: Steven (did not have a chance to fully review) Motion passes. AI: Brad enter issue 269 into SVDB Issue 273(304) AI: Matt bring up Issue 273 for re-vote Monday. Issue 274 Brad moves to accept proposal. Karen seconds. No opposed. Abstain: Steven (did not have a chance to fully review) Motion passes. 275/226: Issue 278 AI: Matt add issue 278 to April 4th agenda Issue 280 Steven moves to resolve as: "This is rejected as it will conflict with backward compatibility with 1364 which is a requirement of SV." Cliff seconds. No opposed. No abstain. Motion passes. Issue 285 AI: Karen to get more information for issue 285 Issue 234 AI: Matt add issue 234 to April 4th agenda Issue 243 AI: Gord bring new wording and clarification of issue 243 to April 4th meeting AI: Matt add issue 243 to April 4th agenda Issue 244 AI: Matt add issue 244 to April 4th agenda Problematic case occurs when highconn of interface port is a hierarchical reference to interface or to a modport of a hierarchical reference to an interface. Issue 245 Cliff moves to accept modified wording: Any instantiation whose port actuals refer to an arrayed interface shall itself be treated as an arrayed instantiation when considering the elaboration flow. Steven seconds No opposed. No abstain. Motion passes. AI: Matt Add Issue 245 to SVDB Issue 246 Discuss on April 4 AI: Matt add issue 246 to April 4 agenda AI: Gord to provide example for issue 246 Issue 247 AI: Matt add issue 247 to April 4 agenda Issue 248 AI: Matt add issue 248 to April 4 agenda Issue 227 It is equivalent to SVDB item 324 AI: Matt add issue 227 to April 4 agenda Issue 264 Pending Issue 265 AI: Cliff to make proposals for issues 264 & 265 Issue 231 Dave moves to accept proposal. Brad seconds. No Opposed. No Abstain. Motion passes. Issue 242 Dave moves Packages must not contain any processes, therefore wire declarations with implicit continuous assignments are not allowed. Cliff seconds. No opposed. No abstain. Motion passes. Issue 249 Dave moves to remove task keyword. Brad seconds. No oppposed. No Abstain. Motion passes. AI: Dave add issue 249 to SVDB. Issue 224 Issue 277 is duplicate. Issue 277 is in masterdata worksheet and includes a full proposal. AI: Matt add issue 224/277 to April 4 agenda Next Meeting: Monday, April 4 9:30am-5:00pm Pacific Action Items Pending 04/01/05 Karen Ask Johny for the purpose of the 'WG Resolution' column 04/01/05 Cliff to review Item 266 and report status at April 4 meeting. 04/01/05 Steven & Brad will review and propose solution for issue 1 at the April 4 meeting. 04/01/05 Steven will review and propose solution for issue 6 at the April 4 meeting. 04/01/05 Gord to propose solution to issue 29 04/01/05 Karen to provide Gord with SVDB account 04/01/05 Brad to assign issue 29 to Gord 04/01/05 Steven to propose solution to issue 35 at the April 4th meeting 04/01/05 Brad to propose solution to issue 91 at the April 4th meeting 04/01/05 Dave to propose solution to issue 216 at the April 4th meeting 04/01/05 Matt enter issue 223 into SVDB 04/01/05 Brad enter issue 269 into SVDB 04/01/05 Matt bring up Issue 273 for re-vote Monday. 04/01/05 Matt add issue 278 to April 4th agenda 04/01/05 Karen to get more information for issue 285 04/01/05 Matt add issue 234 to April 4th agenda 04/01/05 Gord bring new wording and clarification of issue 243 to April 4th meeting 04/01/05 Matt add issue 243 to April 4th agenda 04/01/05 Matt add issue 244 to April 4th agenda 04/01/05 Matt Add Issue 245 to SVDB 04/01/05 Matt add issue 246 to April 4 agenda 04/01/05 Gord to provide example for issue 246 04/01/05 Matt add issue 247 to April 4 agenda 04/01/05 Matt add issue 248 to April 4 agenda 04/01/05 Matt add issue 227 to April 4 agenda 04/01/05 Dave add issue 249 to SVDB. 04/01/05 Matt add issue 224/277 to April 4 agendaReceived on Sun Apr 3 23:06:28 2005
This archive was generated by hypermail 2.1.8 : Sun Apr 03 2005 - 23:06:32 PDT