1 / 5

Building a Model for Sharing Proprietary Software

Explore the innovative approach of creating a safe haven for sharing proprietary software through the Source Code Parlor Collection. Learn about the benefits, risks, and the essential role of licensing agreements in preserving software heritage. Join the discussion on access, limitations, and storage methods for this unique archival initiative.

sybill-brooks
Download Presentation

Building a Model for Sharing Proprietary Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building a Model for Sharing Proprietary Software Amy Stevenson Archives Manager Microsoft Corporation amyste@microsoft.com (425) 705-9313

  2. The Software Company Archives • Resource/priority limitations • Can’t save everything • Usage drives preservation • Barriers to access • How would a researcher get access to Microsoft retail software today? • What about source code?

  3. The Source Code Parlor Collection Benefits • Creates a safe haven for sharing • Allows for consistent preservation • Better Research • Positive PR Risks • Legal • Financial • Negative PR

  4. The Answer? The License! • Or in other words, the donor agreement form. • Volunteer/multidisciplinary effort within Microsoft. • Goal? An archival agreement whose terms protect both the archiving organization and the donating organization.

  5. Issues/Discussion? • How should the archive be used? • Who should be able to access the software within it? • What limitations will exist on the use of the material? • In what form will the software be stored? • How broadly accessible should it be?

More Related