ant elder wrote:
On 9/27/07, Simon Laws <[EMAIL PROTECTED]> wrote:

<snip>

5 - On ongoing OSOA work. Assuming that there is ongoing work and that the

mode of operation is unchanged, maybe we wait until it reaches OASIS.



Thats the one i was mainly thinking about.

"wait until it reaches OASIS" is one option but it doesn't seem ideal as it
means it could take quite some time before Tuscany can implement some of the
new features.

The other end of the spectrum is to say we fine with the OSOA way of "OSOA
provides means for providing feedback and means for joining as a supporter
for access to some non-public materials", that doesn't seem ideal to me
either as it doesn't seem right for an Apache project to be implementing
something where only a select group have access to the design docs.

I don't know the answer, I think the main thing is we've shown we understand
the issue, have reached some consensus, and are clear about whats happening.
I'd be more comfortable with Tuscany only implementing OSOA things when
there's a draft published publicly, but even that isn't perfect as it takes
sometime for drafts to get published publicly (lets hope there's an example
of this imminently).

What do others think?

I think the current wording of the resolution provides the right
framework for making this decision as and when specific OSOA items
come up for consideration.  It says the Tuscany PMC should be charged
with the creation....of software....based on the standards defined by
the OASIS OpenCSA group....

This lays down a general principle and doesn't say whether or not some
particular OSOA work item is or isn't in scope for Tuscany.  I think
it's reasonable that this be left to the PMC to decide, and I'd expect
them to take into account the importance of the OSOA work item to the
Tuscany community, the openness of the OSOA work process and
published specs, and how closely the OSOA item is connected to the
OASIS OpenCSA specs that provide the technical foundation for what
Tuscany does.

  Simon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to