All,
Ivar did a nice job echoing the concerns that were going through
my mind when I had responded earlier. But thinking through this
some more, I am coming to the conclusion that we must figure out a
way to allow participating companies to have an explicit
representative on the Specification Teams that they can change at
will. Because it actually is an absolute requirement, and not for
the reasons that Richard outlined. This is not about the
investment that these companies are making in the code or in the
process. It is about the intellectual property that they are
contributing.
We want to establish a specification process that clearly provides
royalty free licenses to as many patents as possible which apply
to these specifications. They way that is going to happen is via
corporate participation in the Specification Projects, because it
is companies that own large patent portfolios. The IP rules will
say that if a company has a representative on the Specification
Team that any patents they have which read on the specification
must be licensed to all downstream implementations on a royalty
free basis. This means that these representatives must be
formally representing their employer. This also means that if for
whatever reason their employer needs to change their
representative on the Specification Project they must be
allowed to do so. Any other approach means that a change in on
person's involvement in a Specification Project could imply a
significant loss of patent rights to the whole community.
I could imagine allowing someone who leaves their employer to
remain on the Specification Project as an individual, or as a
representative of another participating member company. But that
individual's original employer must have the ability to appoint an
alternate representative.
Does anyone see a hole in this logic?
On 2018-05-25 1:02 PM, Ivar Grimstad wrote:
Hi,
I think we should tread carefully here so we don't become a
corporate club where you have to pay to play, which is exactly
what critical voices in the community have warned against.
I can understand the reasoning behind the wish for a
company to being able to replace a committer on a project. But
at the same time, if a corporation is allowed to do that it
should probably apply to individual committers as well. E.g.
someone that wants to resign from the project for some reason
and give the reigns over to someone else. By doing so, we are
going against the Open Source Rules of Engagement defined by
the EDP ( https://www.eclipse.org/projects/dev_process/development_process.php#2_1_Open_Source_Rules_of_Engagement).
So be prepared for a storm! This will not be well received by
our critics...
Ivar
|