![]() How to make the Software Stories more narrative?.How to facilitate the creation of a Story by an external party?. ![]() How to integrate the creation of a Software Story into the existing SWHAP Guide?.The Software Stories initiative is in a prototyping phase, and creating a new story was the occasion to further define the tools and processes around it and to clarify desired evolution for the Software Stories platform.Īmong others, the following questions were addressed: With this mission at hand, she has tested the full process with the Amaya software. In May 2023, Mathilde Fichen assumed the responsibility of conducting a survey among Inria alumni and testing the SWHAP process for Inria contributors. The second addition to the Inria Collection Story was the Le Lisp SWH Software Story, which was created with the assistance of the late Christian Jullien and Jérôme Chailloux. Elisabetta has also launched the Inria collection with the first Inria story with Claude Gomez, portraying the Scilab Software Story. In 2022, Elisabetta Morri joined this journey and contributed the Magama Lisp story in collaboration with Carlo Montangero to the Pisa collection. In the collection we had the following stories: When Software Heritage launched the Software Stories collection, it was available with the Pisa collection, originating from Pisa University and contributed by Carlo Montangero and Guido Scatena. The project leverages information available on Wikidata to present the history of significant historical software projects in an accessible and interactive way. In 2021, Software Heritage launched the Software Stories interface, in collaboration with the Science Stories team and the University of Pisa, with UNESCO’s support. The Software Stories: the presentation layer To accomplish this endeavor, the Software Heritage Acquisition Process (SWHAP), established in 2019, was designed as a four step protocol: It requires a careful methodology to collect and reconstruct the innovative creation of its authors. ![]() Recovering legacy source code, where the human readable knowledge is kept, is a delicate task. ![]() It ensures that the knowledge, creativity, and groundbreaking ideas encapsulated within these lines of code remain accessible for future generations. The preservation of this software is not just a matter of nostalgia it’s a commitment to our collective digital heritage. Software source code is the result of a significant part of the intellectual creative efforts of humankind over the last decades, and is becoming an important part of our cultural heritage. These software artifacts are often hard to find and require human care and curation. Within this mission, there is a category of software which had a profound impact on the evolution of technology and the way we live, work, and innovate. Software Heritage’s mission is to collect, preserve and share all software source code. We are delighted to present a new Landmark Legacy Software Story to Inria’s stories collection: the story of the web browser and editor Amaya. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |