Hi Sean and Chet:I personally prefer:2. OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC PROMCODE) TC (97 chars)
since PROMCODE is an abbreviation of “Project Management of Contracted Delivery”.I will come back to you tomorrow.Regards,MikioFrom: Sean KennedySent: Friday, February 21, 2014 1:41 AMTo: Chet EnsignSubject: Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener callHi Chet,
I'm checking with the Steering Committee about dropping the "OSLC Lifecycle Integration" words as this is something that they wanted all affiliated TCs to have.
(It's surprising that the vendor couldn't simply instruct you to update the database schema to increase that limit ... *shrug*)
For now, I've got a pair of suggestions that keep those words by dropping others:
1. OASIS OSLC Lifecycle Integration for Project Management of Software Supply Chains (OSLC-PROMCODE) TC (100 chars)
2. OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLC-PROMCODE) TC (97 chars)
Best regards,
Sean Kennedy OSLC Community Development Leader for IBM Rational Operations Coordinator for the OSLC Steering Committee Phone: +1-905-413-4385 8200 Warden Ave Fax: +1-905-413-4850 Markham, Ontario L6G 1C7 Email: seanpk@ca.ibm.com D1/R0A/8200/MKM LinkedIn: http://www.linkedin.com/in/seanpk Canada
OSLC: Lifecycle integration inspired by the web http://open-services.net Eclipse Lyo: Enabling tool integration with OSLC http://eclipse.org/lyo There is nothing more powerful than an idea whose time has come. -- Victor Hugo Chet Ensign ---2014/02/20 11:14:52 AM---Mikio, Sean and all - We have run into a technical limitation in our system that requires me to
From: Chet Ensign <chet.ensign@oasis-open.org>
To: Mikio Aoyama <mikio.aoyama@nifty.com>,
Cc: Tsutomu Kamimura <kamimura@us.ibm.com>, Yabuta Kazuo <yabuta.kazuo@jp.fujitsu.com>, n-kishinoue@ax.jp.nec.com, よしだひろゆき <yuki.yoshida@jp.fujitsu.com>, Dave Ings/Toronto/IBM@IBMCA, jikeitou-std-contact@ml.css.fujitsu.com, k-matsunaga@da.jp.nec.com, Sean Kennedy/Toronto/IBM@IBMCA, Carol Geyer <carol.geyer@oasis-open.org>, Robin Cover <robin@oasis-open.org>, oasis-charter-discuss@lists.oasis-open.org
Date: 2014/02/20 11:14 AM
Subject: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
Mikio, Sean and all -
We have run into a technical limitation in our system that requires me to ask for a change to the PROMCODE charter.
We just learned, in setting up the website for the TC, that we are restricted to a 100 character limit to the name of the TC. We have checked with the vendor of our software and we’re told that this is a hard limit in the system and cannot be changed.
Unfortunately, we now find that the name as we all agreed to it is 23 characters over the 100 limit and will have to be shortened. (Specifically, OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery for Software Supply C^^hain (OSLC PROMCODE) TC)
The decision on the name is up to all of you of course. We worked to see what options we could come up with and here are two suggestions we can offer:
- OASIS OSLC Project Management of Contracted Delivery for Software Supply Chain (PROMCODE) TC (92 characters)
- OASIS Project Management of Contracted Delivery for Software Supply Chain (OSLC PROMCODE) TC (91 characters)
Please note that we need to keep “OASIS” at the start of the name and “TC” at the end. We don’t absolutely need to have the parenthetical abbreviation included. You can also abbreviate some of the words if you like (e.g. ‘PM’ instead of ‘Project Management’). We didn't want to make any assumptions on what abbreviations might or might not work for you.
Again, please accept my apologies for hitting this problem at this late stage of the process. We have simply never hit this limit before and it took us by surprise.
If you would let us know what name you all decide to use, we’ll proceed with getting everything set up for the Call for Participation.
Best regards,
/chet
On Wed, Feb 19, 2014 at 3:40 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:Hi Chet and folks:
Thank you for accepting the revised charter.
Attached please find a plain text format of the charter.
I hope this complies your request.
Best Regards,
Mikio
From: Chet Ensign
Sent: Wednesday, February 19, 2014 7:16 AM
To: Mikio Aoyama
Cc: Tsutomu Kamimura ; Yabuta Kazuo ; n-kishinoue@ax.jp.nec.com ; よしだひろゆき ; Dave Ings ; jikeitou-std-contact@ml.css.fujitsu.com ; k-matsunaga@da.jp.nec.com ; Sean Kennedy ; Carol Geyer ; Robin Cover ; oasis-charter-discuss@lists.oasis-open.org
Subject: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
Mikio, this looks fine. Can you do one last thing for me? Accept all your changes so that the form of the document is final, then save it as a plain text file (not a .doc format file) and send that to me as the final, formal submission. I will then get that loaded to the TC web site and prepare the call for participation.
Thanks very much,
/chet
On Tue, Feb 18, 2014 at 11:49 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:Hi Chet and PROMCODE team:
Thank you for your follow-up minutes on the agenda for OASIS OSLC-PROMCODE TC.
Attached please find the revised “final version” of TC charter which reflects two comments.
I hope this version meets all the requirements to PROMCODE TC.
Best Regards,
Mikio
From: Chet Ensign
Sent: Saturday, February 15, 2014 12:00 AM
To: Mikio Aoyama ; Tsutomu Kamimura ; Yabuta Kazuo ; n-kishinoue@ax.jp.nec.com ; よしだひろゆき ; Dave Ings ; jikeitou-std-contact@ml.css.fujitsu.com ; k-matsunaga@da.jp.nec.com ; Sean Kennedy ; Carol Geyer ; Robin Cover
Cc: oasis-charter-discuss@lists.oasis-open.org
Subject: Notes from the PROMCODE convener call
Proposers of the PROMCODE Technical Committee,
Following the close of the call for comment period on your proposed charter, the convener call was held yesterday, 14 February 2014, 10:00 am JST, 13 February 2014, 8:00 pm US EDT. Dr. Mikio Aoyama, the convener, Sean Kennedy from the OSLC Member Section and Chet Ensign from OASIS were in attendance.
We noted that two comments were received on the draft charter: a request that a link to the existing PROMCODE specification that will be contributed be provided in the charter and a recommendation to change the proposed TC name to align with the pattern being used by the other TCs affiliated with the OSLC Member Section. Dr. Aoyama said that the proposers will make these changes. He has provided a comment resolution log for these comments to OASIS.
We reviewed the next steps for starting the Technical Committee and the upcoming schedule:
- Submission of the final version of the charter: no later than Wednesday, 19 February, 2014
- OASIS issues the Call for Participation: no later than Sunday, 23 February, 2014
- OASIS issues a reminder of the upcoming deadline to join the TC and be eligible for voting rights at the first meeting: Monday, 10 March, 2014
- OASIS issues the call for nominations for chair: Monday, 10 March, 2014
- Last day to join the TC in time to have voting rights at the first meeting: Tuesday, 18 March, 2014
- OASIS issues the list of members eligible to vote at the first meeting: Wednesday, 19 March, 2014
- First meeting of the TC: Tuesday, 25 March 2014
We reviewed the resources that will be available to the TC when the Call for Participation is issued: the internal and public web pages, the email listserv, the roster, calendar and document repository. I covered the additional capabilities that the TC can request after the initial meeting: a wiki, JIRA project and SVN version control repository.
We discussed steps that OASIS will take to publicize the TC and solicit additional participants. Sean mentioned that the Member Section has been running webcasts on OSLC work and that PROMCODE will be included in an upcoming one on the 19th of February. We discussed that it would be useful if the Call for Participation were available at that time.
We then closed the meeting. Please let me know if you have any questions about any of the above or about the upcoming steps.
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open