Re: [odf-adoption] Re: [odf-camp] Re: ODF Interoperability Camp Follow-up

[robert_weir@us.ibm.com]

Thomas Zander <zander@kde.org> wrote on 11/02/2007
01:56:59 PM:
 
> Maybe I'm misunderstanding the goals and purpose of this workgroup,
 but can 
> you explain why coordination and sharing test cases etc requires IP
rules to 
> be in place?  Its not like this workgroup produces documents...
> 
> Or, let me ask it the other way around; what advantage is there for
advancing 
> ODF interoperability to use a mailinglist that only a select few people
can 
> write to, with the added restriction that they have to agree to a
rather long 
> agreement first?
> 

I think it is very likely that documents would be
produced, which could range from implementation guides, interoperability
guides, profiles, etc.  Even a test suite is a creative work that
has IP implications.

That said, I agree that having more people rather
than fewer people is better.  And that reduced complexity/organization
is better than a lot of hoops and paperwork.  But I question whether
joining OASIS is really a significant hurdle, either procedurally or financially?
 Look what we did with the Accessibility Subcommittee.  We have
a large number of subject member experts from all over the globe, from
large corporations, individuals  as well as smaller non-profits and
advocacy groups.  They are producing useful documents like their recent
Accessibility Guidelines (http://opendocument.xml.org/node/841)
Somehow they managed to navigate the OASIS membership procedures.

It seems to me that the inconvenience of joining OASIS
is a far less than the inconvenience of attending the workshop in Barcelona,
but we filled the room there with interested people.  I even had to
deny one company the ability to demo their ODF interoperability for lack
of time in the schedule.  

So I'm not convinced that OASIS membership is an unreasonable
barrier to participation, even for FOSS projects.  Of course, we're
debating this all among OASIS members.  Maybe it would help if we
talked to someone who actually isn't an OASIS member and get their perspective...

> I would personally aim for wide participation with loads of volunteers
doing 
> tests and lots of ODF-implementers working together.  Putting
up allsorts of 
> barriers like you all suggest means you will only hear a select few
> companies / people.  And that will just give you a false sense
of security.

The point would be to not have this be a barrier.
 Is it paperwork?  Yes?  Is it rules for participation and
IP?  Yes.  Does it prevent someone from walking in and becoming
a member in 30 seconds?  Yes.  But pointing back to the Accessibility
Subcommittee, once the membership paperwork is done, and you are a member,
the day-to-day operation of the interoperability work goes on.  It
is mailing lists, meetings, document repositories and workshops.