Re: Directory for open-source software
I'll register once you have a Web server certificate that is signed by someone other than "Snake Oil, CA"! Best, Richard Bondi www.cryptovb.com At 12:30 PM 12/9/2000 -0400, Steve Mallett wrote: >Hello all, > >I know this list is for discussion of licenses, but with some work the subject >of this email (my site) may help eliminate some unecessary traffic on this >list. For instance, questions like "Is such & such open-source??" > >I'd like to ask for the list member's thoughts on my website concept: >Open-Source Directory (OSD). > >Over the last three months I've created a website whose mission is to >provide a resource for endusers and developers to verify that a package, >consisting of software together with its accompanying license is an >open-source distribution. > >It is/will be a directory of stable open-source software that will list >product's meta-data based on ESR's Trove specs for such data. For >instance, its >**license**, authors, history of changes, binary/source download address, bug >reporting contacts, dependencies etc.. > >We're at www.opensourcedirectory.org We are still testing, but are >near to doing some announcements. We look a lot like Sourceforge since we use >their GPL'd code. Their software map has a basis with the Trove specs. To >what >degree I'm not a party to. > >Getting into the long storyI started this after emailing ESR to see if a >directory of open-source software was of use. He said yes and so here I am >...with some of his helpful input. (Any screw-ups are totally mine.) > >I have had some discussions over the last few months with some folks in the >community, but let's just say that SourceForge has listed OSD on their page of >folks who use SF code. After some explantion of OSD's scope & function >(non-developement) everything got smoothed out. Also I had some discussion >regarding OSD vs. Freshmeat & LinuxApps. That person came to >agree that we were not redundant since both of these entities focus on Linux >where OSD is indifferent to what platform the pkgs are written for. So far >these are the two major off-hand comments we've had to clear up. > >Now, we're not totally done. However; we are ready to do the actual job of >listing product meta-data. Before trying to attract developers of stable >products to list, and while putting on the finishing touches, I'd greatly >appreciate any comments, questions, concerns, assistance..anything from >members >of this list. > >Thank you in advance, >Steve Mallett, >http://www.OpenSourceDirectory.org >[EMAIL PROTECTED]
Proof of small OSI FAQ
Dear all, I've got a small open source/OSI FAQ on a site for cryptography for visual basic programmers, to explain the open source license (Ricoh) that comes with some code. If anyone can see anything incorrect or misleading in the FAQ, do let me know so I can correct it. Much appreciated! The FAQ is at: http://www.cryptovb.com/books/bondi/license_faq/license_faq.html Best, Richard Bondi = __ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
Small OSI FAQ needs proof-reading
Dear All, As part of my book "Cryptography for Visual Basic," I released code under a Ricoh license. Because of questions I've received about it from readers, I've created a small FAQ. It would be a great help if some members of this list could read over the FAQ to make sure it correctly describes open source licenses. The faq is located at: http://www.cryptovb.com/books/bondi/license_faq/license_faq.html Some background: the code is called WCCO, for "Wiley CryptoAPI COM Objects." The Ricoh license was renamed the Wiley Open Source license. My book was published by Wiley. Thank you very much, Richard Bondi
Two license questions
Dear All, My book will be my publisher's first to include open source licensed code. (The book is "Cryptography for Visual Basic: A Programmer's Guide to the Microsoft CryptoAPI", and includes open source COM wrappers for the CryptoAPI.) Can someone help me with the following questions please? 1) I think this belongs on an FAQ at www.opensource.org: if I use one of the approved licenses, can I rename it? I'm going to use the Ricoh license for my book's code; can I call it the Wiley Open Source Public License everywhere? 2) My publisher is very confused about whether they should replace their standard CD software statement with the Ricoh license, or put both on the page facing the CD. Do they contradict each other because the Wiley statement says "All rights reserved"? What confuses me is that the Ricoh license's Exhibit says "All Rights Reserved:" doesn't it actually grant a ton of rights?!! Here's the old Wiley statement: CUSTOMER NOTE: IF THIS BOOK IS ACCOMPANIED BY SOFTWARE, PLEASE READ THE FOLLOWING BEFORE OPENING THE PACKAGE.This software contains files to help you utilize the models described in the accompanying book. By opening the package, you are agreeing to be bound by the following agreement: This software product is protected by copyright and all rights are reserved by the author, John Wiley & Sons, Inc., or their licensors. You are licensed to use this software as described in the software and the accompanying book. Copying the software for any other purpose may be a violation of the U.S. Copyright Law.This software product is sold as is without warranty of any kind, either express or implied, including but not limited to the implied warranty of merchantability and fitness for a particular purpose. Neither Wiley nor its dealers or distributors assumes any liability for any alleged or actual damages arising from the use of or the inability to use this software. (Some states do not allow the exclusion of implied warranties, so the exclusion may not apply to you.) TIA for your help! Richard Bondi
