As you can see, your call for consent as OASIS Standard has closed and passed. Congratulations on reaching this milestone.Â
Project Admin will now publish and announce PROMCODE V1.0 OASIS Standard to the world. JIRA ticket https://issues.oasis-open.org/browse/TCADMIN-4169 has beenÂopened to manage this task. plase feel free to follow it, ask questions there, etc.Â
We'll let you know when the standard is published. And again, congratulations!Â
/chet
Call for consent of OSLC PROMCODE Version 1.0 as an OASIS Standard has closed.
--
---------- Forwarded message ---------
From: <tc_admin@oasis-open.org>
Date: Fri, Mar 11, 2022 at 7:04 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent of OSLC PROMCODE Version 1.0 as an OASIS Standard"
To: <chet.ensign@oasis-open.org>
From: <tc_admin@oasis-open.org>
Date: Fri, Mar 11, 2022 at 7:04 PM
Subject: Email sent to voters re: [voting] Groups - Ballot closed: "Call for consent of OSLC PROMCODE Version 1.0 as an OASIS Standard"
To: <chet.ensign@oasis-open.org>
Call for consent of OSLC PROMCODE Version 1.0 as an OASIS Standard has closed.
|
Ballot Title: Call for consent of OSLC PROMCODE Version 1.0 as an OASIS Standard Question OSLC PROMCODE V1.0 has been presented to the membership by the OASIS OSLC PROMCODE) TC [1] as a candidate for OASIS Standard. Do you consent or object to its approval as an OASIS Standard? Voting Results 12 of 186 eligible companies cast their vote before the deadline. - Consent received 12 Votes - Object received 0 Votes The ballot received 0 comments. Description Managing software delivery can be highly challenging due to the diversity of the development processes, methods, tools and platforms used by different organizations participating in a project. Manual work done in order to exchange proprietary management data is inefficient, error-prone and inflexible. OSLC PROMCODE Version 1.0 is designed to address the need for systematic sharing of project management information within and between organizations. Note that Committee Specification 03 was produced to correct non-material changes discovered during the 60-day public review. This was done in accordance with the procedures outlined in section 2.8.2 of the TC Process (https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/#OSpublicRev). The list of changes can be seen in https://lists.oasis-open.org/archives/oslc-promcode/202202/msg00002.html and in the red-lined copies at https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab-DIFF.pdf, https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec-DIFF.pdf, and https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes-DIFF.pdf. The TC received 3 Statements of Use from IBM, Fujitsu, and NEC [2]. This is a call to the Organizational Members of OASIS to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however your consent is assumed unless you register an objection [3]. To register an objection, you must: 1. Indicate your objection on this ballot, and 2. Provide a reason for your objection and/or a proposed remedy to the TC. You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list [3]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent. URIs: The prose specification document and related files are available here: Part 1: Specification HTML https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec.html https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-spec.pdf Part 2: Vocabulary HTML https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.html https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.pdf Part 3: Constraints HTML https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.html https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.pdf Vocabulary terms https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-vocab.ttl Constraints https://docs.oasis-open.org/oslc-promcode/promcode/v1.0/cs03/promcode-shapes.ttl --- Additional information --- [1] OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC https://www.oasis-open.org/committees/oslc-promcode/ [2] Statements of use - IBM: https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00004.html - Fujitsu: https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00003.html - NEC: https://lists.oasis-open.org/archives/oslc-promcode-comment/202111/msg00001.html [3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent OSLC PROMCODE TC comment mailing list: oslc-promcode-comment@lists.oasis-open.org (You must be subscribed to send to this list. To subscribe, see https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=oslc-promcode.) TC main mailing list: oslc-promcode@lists.oasis-open.org View Results Group: OASIS organizational voting Date Opened: Friday, 25 February 2022 @ 12:00 pm UTC Date Closed: Friday, 11 March 2022 @ 11:59 pm UTC This email has been sent to 264 members of OASIS Open. Here is a list of members who were notified:
Referenced Items
|
ChetÂEnsignChief Technical Community Steward OASIS Open | Â | Â | Â |
|