On Tue, 10 Apr 2007, John Plocher wrote:
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:
To be honest John, I would think that having reference to a particular license in the man page could be a good thing, because as we get more and more software there is the issue of dual license, compatibility, etc...
For those that dual license, that could be a PITA, since that would mean they would need different man pages for each use, but for other folks that license under a single license I don't see it as being bad. My $0.02.
This is a bad idea because the old names, which are probably Committed APIs, can not change without breaking already deployed customer apps.
Good example, but in the open source world, that issue is less, because marketing is often not a consideration for the software.
If you think about a developer looking at OpenSolaris and saying, "I want to enhance feature blah-blah, and can tell quickly what the license is by looking at the man page...that would be helpful. The sources are the ultimate decision though, the man page could be wrong.
-- Alan DuBoff - Solaris x86 IHV/OEM Group _______________________________________________ opensolaris-discuss mailing list [email protected]
