Sort out LispUsers

[masinter]

Broken, won't load, not useful, buggy, cant open docs in tedit, odd copyright etc

[masinter]

Make a table for recording results that is convenient to share

for each package in LlispUsers and Library at random (look for TEDIT files)

• Can you read the sources?
• Can you read the TEDIT file?
• Can you compile it in a vanilla lisp.sysout?
• can you get it to run and build some examples
• your evaluation of whether it is useful or interesting (for prioritization)
• raise issues if things break reproducibly or even fix simple problems
• is it demo-able? can you make a short (max 5 minute) demo showing it in action

[masinter]

For now, I made a Google Spreadsheet
https://docs.google.com/spreadsheets/d/1pn4UcS-9CgMLi_qeGZlOGGEusAKsNDKxz1XhLwQCgKw/edit?usp=sharing

[masinter]

Packages that are hoplelessly broken or useless and uninteresting, git mv to obsolete/lispusers

[nbriggs]

Useless and uninteresting to who?

[masinter]

insert "obviously": duplicates of things already incorporated elsewhere (library? sources?)
if it's really trash then git rm it and ask for 2 reviews

[masinter]

need to do the same for library -- no documentation for BIGBITMAP for example.
#348

[masinter]

You might think this is "too much" metadata, but it seems like it might be useful to consider this issue ("Sort out LispUsers") might benefit from a formal approach. Is this the kind of project that would appeal to SPN members?

The Software Preservation Network (SPN) Metadata Working Group is pleased to release the Software Metadata Recommended Format (SMRF) Guide. SMRF aims to provide an adaptable framework to describe a range of software types to support discovery, access, and reuse in libraries, museums, archives, and repositories.

You can find a link to the SMRF Guide on the SPN website: https://www.softwarepreservationnetwork.org/smrf-guide/

[skaisler1]

Larry: I think this might be useful for users looking for packages. It would also broaden the exposure of Interlisp and, perhaps, reinforce the idea of its powerful development environment. Questions: How would we encode the metadata - using XML? Would the metadata be embedded in a separate database/file? This would take some effort as each Lispuser packages would need to be inspected. Would we also want to define our own metadata fields and assign values? We would need to coordinate with SPN as to where the metadata would be stored assuming they already have a repository/database. Steve K.

…

On 02/12/2022 3:02 PM Larry Masinter ***@***.***> wrote: You might think this is "too much" metadata, but it seems like it might be useful to consider this issue ("Sort out LispUsers") might benefit from a formal approach. Is this the kind of project that would appeal to SPN members? > > > The Software Preservation Network (SPN) Metadata Working Group is pleased to release the Software Metadata Recommended Format (SMRF) Guide. SMRF aims to provide an adaptable framework to describe a range of software types to support discovery, access, and reuse in libraries, museums, archives, and repositories. > > You can find a link to the SMRF Guide on the SPN website: https://www.softwarepreservationnetwork.org/smrf-guide/ > > > — Reply to this email directly, view it on GitHub #7 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AJMVT2Y6XPIHTK6ARW4ISC3U224HBANCNFSM4P2T47VA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you were assigned.Message ID: ***@***.***>

[masinter]

I don't think they have a repository/database per se. Would we use Zotero? The CHM is working with Microsoft and another company to build their repository of online assets.

I'm thinking we have metadata fields in our "lispusers" repository that don't fit into their categories exactly and we might also lead the way. When they talk about "software" in an archive they're thinking of compiled, delivered software, not source code or libraries.

[skaisler1]

Larry: Here are two possibilities: 1. Encode in XML within each Lispuser package as a comment field the metadata for that package. 1. Using DECLARE etc, create a Record Structure that holds the metadata fo each Lispuser package (sort of like the FileMap) which is located in the Lispuser Package so, ot it is "self-describing". 2. In Zotero, build an Excel spreadsheet wi the first column the name of the Lispuser package and the remaining columns having the metadata from manual plus metadata that we define. Key Question: What metadata in that manual makes sense for source programs, then augment it with data we already have. Steve K.

…

On 02/15/2022 12:52 PM Larry Masinter ***@***.***> wrote: I don't think they have a repository/database per se. Would we use Zotero? The CHM is working with Microsoft and another company to build their repository of online assets. I'm thinking we have metadata fields in our "lispusers" repository that don't fit into their categories exactly and we might also lead the way. When they talk about "software" in an archive they're thinking of compiled, delivered software, not source code or libraries. — Reply to this email directly, view it on GitHub #7 (comment) , or unsubscribe https://github.com/notifications/unsubscribe-auth/AJMVT2ZZWBMBZ2HCQCZRIGTU3KHGRANCNFSM4P2T47VA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you were assigned.Message ID: ***@***.***>