Re: [pacr] Proposing name change to PACR

On Mon, Feb 11, 2013 at 9:20 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:

Hi Neil,

You raise an interesting point. One difficulty though is that once the charter has been announced, the name cannot be changed. In order to change the name (or the IPR mode) you have to start a new TC.

What we can change easily is the short description that goes with the TC name. It appears in the TC list, under the name on the TC web page, etc. Right now it reads:

Public Administration Cloud Requirements (PACR)
>> Developing cloud computing operational requirements for public administrations to inform procurement, auditable assurance and conformance testing, and acquisition criteria <<

We can replace that short description easily. I'm copying Carol on the email as she may have thoughts on what would be more compelling.

Best,

/chet

On Mon, Feb 11, 2013 at 9:08 AM, Neil McEvoy <neil.mcevoy@ifossfoundation.org> wrote:

Hi folks

There hasn't been a good sign up for the PACR group thus far, and I feel one of the primary issues is the name of the group itself.

PACR isn't a very helpful term and given the somewhat dry nature of the focus area is further tying one hand behind our back, so instead we would ideally need a name that is immediately self-describing and catchy. This is really important to 'brand' marketing as demonstrated by the success of TOSCA or CAMP for example.

So a couple of ideas could be:

- Government Cloud Computing
- Cloud Provider Compliance

The latter is to reflect what at one point was becoming a more generic focus on compliance vs the public sector - I wouldn't mind either way, each one would work for me as it specifies an exact and clear focus for the group which is key, but in general I am not fixed on these and am open to any other ideas. The main thing is to change away from PACR which I feel is hurting our primary objective of attracting members, confirmed by the low adoption rate.

Kind regards,

--
Neil McEvoy
VP Business Development
iFOSSF.org
Skype:neil.mcevoy1

--

/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

pacr message