Alan Coopersmith wrote:
Unfortunately, a lot of people pass around "ARC won't let you do _____"
without actually asking the ARC.
The ARC's only real involvement with any of this "branding" and/or
"licensing" stuff is to ensure that the branding information is not
intermingled with the architectural artifacts. That is, don't make
a [marketing, license, code] name part of an interface specification:
Our product is known as "iPlanet foo", and it is being
released under the XXX license. The product is installed
into /opt/iPlanet/..., its library will be called
libiPlanetFoo.so, the APIs are all of the form
iPlanetFooSomething() and we put a blurb about the license
into every one of our 250 manpages.
Oops - the Marketing people just decided to rename the
product to be "JES foo" and release it under the CDDL.
This is a bad idea because the old names, which are probably
Committed APIs, can not change without breaking already
deployed customer apps. In the same manner, the licensing
change is an implementation detail and not an architectural
one. The specification on the man page can be (and often is)
met by several different libraries, each having its own
license: (mysql has a GPL and a proprietary version, the
posix/SUS interfaces can be found with GPL (redhat), CDDL
(OpenSolaris) and proprietary (Sun Solaris10) implementations,
etc. As a close to home example, consider the man pages for
the things in OS.o that are in the closed bundle, the ones
that are being cleanroom re-implemented as part of the code
emancipation effort...
-John
_______________________________________________
opensolaris-discuss mailing list
[email protected]
