OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call


Fantastic Mikio. Thank you all very much and we'll get this moving forward. 

/chet


On Fri, Feb 21, 2014 at 10:16 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:
This is resending the following e-mail due to transmission error
(I fixed two e-mail addresses of Kamimura-san and Kishinoue-san).
Mikio
Sent: Saturday, February 22, 2014 12:09 AM
Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
 
Hi Chet, Sean, and all:
 
Today, the PROMCODE consortium had a regular steering committee meeting, and
decided the name of TC as Sean suggested:
OASIS OSLC Lifecycle Integration for Project Management of
Contracted Delivery (OSLC PROMCODE) TC
 
Chet, please find the revised charter attached.
If you have any concerns, please let me know.
 
Regards,
Mikio
Sent: Friday, February 21, 2014 4:47 AM
Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
 

Aoyama-san:

I also prefer the second choice.

In talking to Chet on a separate thread, he reminded me that there is also an explanatory sentence that shows up in the list of TCs and on the TC webpage. Examples, see:
https://www.oasis-open.org/committees/
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=oslc-core

This gives a way for us to still get "Software Supply Chains" in front of people wondering what the TC is about.

Best regards,


Sean Kennedy  
IBM
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
   


Inactive hide details for Chet Ensign ---2014/02/20 02:33:52 PM---Thanks Mikio. I'll watch for your update. /chetChet Ensign ---2014/02/20 02:33:52 PM---Thanks Mikio. I'll watch for your update. /chet

From: Chet Ensign <chet.ensign@oasis-open.org>
To: Mikio Aoyama <mikio.aoyama@nifty.com>,
Cc: Sean Kennedy/Toronto/IBM@IBMCA, Carol Geyer <carol.geyer@oasis-open.org>, Dave Ings/Toronto/IBM@IBMCA, jikeitou-std-contact@ml.css.fujitsu.com, k-matsunaga@da.jp.nec.com, Tsutomu Kamimura <kamimura@us.ibm.com>, n-kishinoue@ax.jp.nec.com, oasis-charter-discuss@lists.oasis-open.org, Robin Cover <robin@oasis-open.org>, Yabuta Kazuo <yabuta.kazuo@jp.fujitsu.com>, よしだひろゆき <yuki.yoshida@jp.fujitsu.com>
Date: 2014/02/20 02:33 PM
Subject: Re: [oasis-charter-discuss] Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call




Thanks Mikio. I'll watch for your update.

/chet


On Thu, Feb 20, 2014 at 12:03 PM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:
    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,
    Mikio
    From: Sean Kennedy 
    Sent: Friday, February 21, 2014 1:41 AM
    To: Chet Ensign 
    Cc: Carol Geyer ; Dave Ings ; jikeitou-std-contact@ml.css.fujitsu.com ; k-matsunaga@da.jp.nec.com ; Tsutomu Kamimura ; Mikio Aoyama ; n-kishinoue@ax.jp.nec.com ; oasis-charter-discuss@lists.oasis-open.org ; Robin Cover ; Yabuta Kazuo ; よしだひろゆき 
    Subject: Re: We have encountered a problem on our side - WAS: Re: [oasis-charter-discuss] Re: Notes from the PROMCODE convener call
     

    Hi 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  
IBM
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
   


    Inactive hide details for Chet Ensign ---2014/02/20 11:14:52 AM---Mikio, Sean and all - We have run into a technical limitationChet 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: 




    --

    /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


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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]