SV: [plcs] Groups - Input to meeting #51

[Tor Arne <tai@sfk.mil.no>]

Reference is made to:

    Action item 50/3: Correct and regenerate Task DEX for review.
Schedule webex to review changes 


The reason for my input in meeting 50 was that I felt and still feel that
the process has not been as inclusive as I expected. A more inclusive
process would have assisted a higher probability of a positive vote. The
closed process is not what I expect in the TC. Some of the TC members have
earlier expressed concerns about the TOG work being too closed. This pass at
solving issues has not let itself to contributions from resources that could
have participated. It could now be argued that the issues that were
discussed in detailed to find a suitable resolution relay on a singular
minds perception and interpretation for the implementation of the
resolution. This approach put a lot on the shoulders of the single resource.

Given the contractual constraints of the current work it is may view that
the TC recognize that the progress is as far as the available effort
allowed.
The TC should establish a baseline and urge the members to seek funding to
secure immediate continuation.


I prefer to defer the formal meeting #51 until we have achieved the
necessary consensus and have a document to accept.


Best regards

Tor Arne 



-----Opprinnelig melding-----
Fra: Mason, Howard (UK) [mailto:Howard.Mason@baesystems.com] 
Sendt: 12. mars 2010 12:16
Til: tjt@lsc.co.uk; plcs@lists.oasis-open.org
Emne: RE: [plcs] Groups - Input to meeting #51

There are a number of clear steps required to release the Task DEX as an
OASIS Committee Specification.

1) Consensus on the approach to the outstanding issues. 
2) Generation of the final document
3) Acceptance as Committee Draft
4) Accept for public review

As we said at the last meeting, and as noted by Tim, there is little
point in proceeding to the second and later steps until those who
provided comments are satisified with the approach to resolution.

Once this initial step is completed, we have a choice of either (a)
proceeding to a vote on the acceptance of the Committee Draft on trust
that the agreed changes are made, or (b) we could schedule a later
meeting to take the vote after the final document is produced.

There is a further issue with (b) since scheduling meetings in rapid
sequence can adversely affect our list of voting members, since
non-attendance at two meetings in a row causes the loss of voting
status.  Converesly, it allows those attending to regain voting status.

Therefore, unless we can be sure that we are in a state to take the
votes today as in (a), I propose to choose option (b) and defer the
formal meeting #51 until we have achieved the necessary consensus and
have a document to accept - hopefully within the next week or so.  The
call scheduled for this afternoon can be used for technical
consensus-building.

What is your preference?






Howard Mason
Corporate IT Office
Tel: +44 1252 383129
Mob: +44 780 171 3340
Eml: howard.mason@baesystems.com
BAE Systems plc
Registered Office: 6 Carlton Gardens, London, SW1Y 5AD, UK
Registered in England & Wales No: 1470151 

-----Original Message-----
From: tjt@lsc.co.uk [mailto:tjt@lsc.co.uk] 
Sent: 12 March 2010 04:19
To: plcs@lists.oasis-open.org
Subject: [plcs] Groups - Input to meeting #51 (TJT DEX D003 Summary 12
Mar 2010.zip) uploaded

                    *** WARNING ***

  This message has originated outside your organisation,
  either from an external partner or the Global Internet. 
      Keep this in mind if you answer this message.


PPT Summary of Task DEX Issues for discussion at meeting #51 This
provides a brief of both BCR1 & BCR2 Issues & status; most of the BCR2
points are from the BCR2 disposition spreadsheet.

Note the proposed disposition for BCR2 were posted by Chris several days
ago (Wed 10/03/2010). See Task Set DEX Ballot Issues BCR2_25Feb2010.xls
in the documents area.

- we have begun work on this and would propose the following approach to
progress the Task Set Dex to Public Review Draft status;

- review the spreadsheet of the R2 Ballot with our proposed dispositions
(noting that according to OASIS rules, the comments should be on the
changes and (I presume)not new observations or enhancements).

- agree on their disposition if possible before the call (i.e. with ESL
&
Jotne)

- assuming agreement we will go ahead with the ballot on Friday, else we
shall need to send around a postponement

- due to features of the release and publication tools & the effort to
create a ballot package, we did not feel that this was the best use of
resources prior to agreement on the disposition actions, therefore, we
are not planning to generate another Committee Draft release  for
Friday; we can review the progress since the February 25th meeting using
DEXlib.

- the discussion on Friday 12th should be about the disposition of the
comments & the agreed changes to be in place, such that producing the
Public Review Draft is approved.


 -- Mr. Tim Turner

The document named Input to meeting #51 (TJT DEX D003 Summary 12 Mar
2010.zip) has been submitted by Mr. Tim Turner to the OASIS Product Life
Cycle Support (PLCS) TC document repository.

Document Description:
PPT Summary of Task DEX Issues for discussion at meeting #51

This provides a brief of both BCR1 & BCR2 Issues & status; most
of the BCR2 points are from the BCR2 disposition spreadsheet.

Note the proposed disposition for BCR2 were posted here by Chris several
days ago (Wed 10/03/2010). See Task Set DEX Ballot Issues
BCR2_25Feb2010.xls in the documents area.

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=36822

Download Document:  
http://www.oasis-open.org/committees/download.php/36822/TJT%20DEX%20D003
%20Summary%2012%20Mar%202010.zip


PLEASE NOTE:  If the above links do not work for you, your email
application may be breaking the link into two pieces.  You may be able
to copy and paste the entire link address into the address field of your
web browser.

-OASIS Open Administration

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


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