Bill Sommerfeld wrote:
How do we get a commitment that a particular URL is stable enough to embed in a binary which may get copied billions of times and which may not be updated for a decade or two?
There's been a discussion on gatekeeper about this. Embedding links to a community-editable site into shipping product is clearly a bug, but having said that it is already out there in the wild, so we will be providing redirects to make sure that the existing links don't break. The same also applies to the license links that are in every Solaris source file.
We need to provide a mechanism so this doesn't happen again in the future, one suggestion is to provide a location where teams can upload such static content and have it published on oso, for example for ZFS it might be http://static.opensolaris.org/zfs. We could investigate using the existing repository services on OSO to manage the content, so updates would be via the normal 'hg push' mechanism. That would allow teams to use the existing repository access control mechanisms to control who is allowed to update the content.
-- Alan Burlison -- _______________________________________________ website-discuss mailing list [email protected]
