
Just happened to run across this page on the internet by accident. If you look at the copyrights (bottom of page) it's clear they are using a bunch of Boost libs. http://betavscan.mcafeeasap.com/beta/docs/readme/Readme.html Not sure if we should add them without permission -- but it is one of those cases where the info is in the public domain... Jeff

"Jeff Garland" <jeff@crystalclearsoftware.com> writes:
Just happened to run across this page on the internet by accident. If you look at the copyrights (bottom of page) it's clear they are using a bunch of Boost libs.
http://betavscan.mcafeeasap.com/beta/docs/readme/Readme.html
Not sure if we should add them without permission -- but it is one of those cases where the info is in the public domain...
I think we can go ahead with it. -- Dave Abrahams Boost Consulting www.boost-consulting.com

"David Abrahams" <dave@boost-consulting.com> wrote in message news:u4qbuqnc8.fsf@boost-consulting.com...
"Jeff Garland" <jeff@crystalclearsoftware.com> writes:
Just happened to run across this page on the internet by accident. If you look at the copyrights (bottom of page) it's clear they are using a bunch of Boost libs.
http://betavscan.mcafeeasap.com/beta/docs/readme/Readme.html
Not sure if we should add them without permission -- but it is one of those cases where the info is in the public domain...
I think we can go ahead with it.
I also think it is OK because it clearly was intended for public consumption. --Beman

Just happened to run across this page on the internet by accident. If you look at the copyrights (bottom of page) it's clear they are using a bunch of Boost libs.
http://betavscan.mcafeeasap.com/beta/docs/readme/Readme.html
Not sure if we should add them without permission -- but it is one of those cases where the info is in the public domain...
I agree, I don't see why we can't make use of that. John.

It is polite to ask, and perhaps politeness is wiser than legal basis. If an email is not answered, it could be surmised that they don't care; otherwise, their preferences should be obvious. <http://www.adobe.com/aboutadobe/pressroom/prcontacts.jsp> Aaron W. LaFramboise

"Aaron W. LaFramboise" <aaronrabiddog51@aaronwl.com> writes:
It is polite to ask, and perhaps politeness is wiser than legal basis. If an email is not answered, it could be surmised that they don't care; otherwise, their preferences should be obvious.
1. Adobe and McAfee are not related, are they? 2. It's not worth anyone else's time to ask, IMO. Are you volunteering your own time? 3. I'd just say "go ahead," but I know how these things work in companies. The question to the PR department triggers a discussion with the legal department and they both decide it would be safer for the company if their use of open source software were not publicized. The job of PR and legal is to limit the company's exposure to risk, so once something shows up on their radar it becomes something for the company to worry about. On the other hand, if the question never arrives, it never becomes a problem. Let's not make a big production out of this. -- Dave Abrahams Boost Consulting www.boost-consulting.com

David Abrahams wrote:
3. I'd just say "go ahead," but I know how these things work in companies. The question to the PR department triggers a discussion with the legal department and they both decide it would be safer for the company if their use of open source software were not publicized.
Which questions the whole idea of "Who's using Boost". Your goal should be to provide a testimonies of those who are *proud* users of Boost - only then you can publish the list and call it "Boost success stories". If you want to publish the info even *knowing* that this might not be intended from the point of view of any not-so-proud user, then your list stops to be a list of "success stories" anymore and becomes a nitpick list, which can be titled "Boost shame stories". Sorry, but I think you should slow down and reflect. Just my 0.05 Euro, feel free to ignore. -- Maciej Sobczak http://www.msobczak.com

Maciej Sobczak <prog@msobczak.com> writes:
David Abrahams wrote:
3. I'd just say "go ahead," but I know how these things work in companies. The question to the PR department triggers a discussion with the legal department and they both decide it would be safer for the company if their use of open source software were not publicized.
Which questions the whole idea of "Who's using Boost".
Your goal should be to provide a testimonies of those who are *proud* users of Boost - only then you can publish the list and call it "Boost success stories".
If you want to publish the info even *knowing* that this might not be intended from the point of view of any not-so-proud user, then your list stops to be a list of "success stories" anymore and becomes a nitpick list, which can be titled "Boost shame stories".
Sorry, but I think you should slow down and reflect.
I spent some time thinking about your points. I think the whole question of pride or shame is a red herring. If PR and legal get together and decide that they don't want it widely known that the company is relying on open-source software, it means nothing about whether the company as a whole is proud of their use. In the worst case, just going through this authorization process causes the company to stop using open source altogether, because while they aren't required to reproduce the BSL in their literature, that isn't true of some other licenses. All that said, anyone with serious reservations about this is welcome to go through the approval process with any company they like. If you receive a negative response and the respondent is aware of the other publicly available information I would be happy to have the entry pulled from the list. We have enough people directly reporting their use of Boost that it won't matter very much. -- Dave Abrahams Boost Consulting www.boost-consulting.com

To Whom It May Concern: I am writing to you on behalf of Boost, a community organization that provides free peer-reviewed portable C++ source libraries. Boost is publishing a list of companies and institutions that are using boost, entitled "Who's Using Boost?," available here <http://freespace.virgin.net/boost.regex/who/html/index.html>. Note that the list is a work-in-progress, and that the final URL of the list may differ. It has come to the organization's attention, by way of inference, that McAfee, Inc.'s VirusScan product uses Boost, based on the copyright information available here <http://betavscan.mcafeeasap.com/beta/docs/readme/Readme.html>. Thus, McAfee has been nominated for inclusion within the above-mentioned list. If you have any preferences, concerns, or special requests regarding this matter, please contact me directly by email. For general information on Boost, please see the Boost website at <http://www.boost.org>. Sincerely, Aaron W. LaFramboise
participants (6)
-
Aaron W. LaFramboise
-
Beman Dawes
-
David Abrahams
-
Jeff Garland
-
John Maddock
-
Maciej Sobczak