Discussion Committee B
Minutes for the phone meeting of 31 August 2006

Update RE face-to-face meeting

brief review of workof 'encryption keys' subcommittee
Working to categorize issues:
(1) ambiguities
(2) usage cases where current language would impact, but not intended to be impacted
(3) use case where current language would impact, problems - to convince

'Scope' subcommittee
The subcommittee has identified language in the GPL3 draft on which technical use cases would be useful.
Will circulate something before the face-to-face meeting.

Avoiding depedence on US copyright law - this was intended.

APIs which were defined sharply - so that free versions could be written

When combining various pieces of software, when is a new 'whole' created?

Discussion of example of performance tool designed to test performance of a proprietary database. Considering cases where tool packaged with database or shipped separately. Extension of the DB or separate tool?

Have you made a new work that includes my part?

Goal of GPL is to relax from maximum copyright.

When do two pieces of become one?

"complex data communication or control flow"

finished API, well-documented, used in a responsible, operating at an arms length
v.
undocumented calls, control blocks are written into by programs that shouldn't, etc.

"intimate" may have been closer to the intended meaning than "complex".
intimate is intended to contrast with arms length.

Next Meeting:
The meeting on 12 September 2006 will focus on encryption keys/protected-boot/technical restrictions and will be chaired by McCoy Smith.