2025 Annual Report
7 views
Skip to first unread message
Paolo Amoroso
Dec 10, 2025, 3:29:28 PM (6 days ago) Dec 10
to Medley Interlisp core
In today's external meeting we outlined the process for writing the 2025 annual report. We will identify the main themes and goals of this year's work and use them as a guide to draft the report, explaining why we did the work and what we were trying to accomplish. The report will also say something about the first five years of the project.
To kickstart the process I went over the report outline and picked these themes and goals, in no particular order. This list is only a start and likely incomplete or not completely accurate.
- create new learning resources and documentation for complete newcomers
- enhance Medley Online to support new users and learners, both in museum/event settings and for self learning
- support modern text input features such as arrow keys
- overhaul font encoding to interoperate with Unicode and support modern fonts
- enhance output generation with HTML support and improved PDF handling
- make it possible to run historical Interlisp applications on modern Medley
- engage with the community on new social media channels as well as other venues
- collaborate with history of computing institutions to present Medley to their audiences
- restructure the bibliography to make it more suited to research and enhance its consultation and presentation
- present the Medley project at academic events to share our lessons learned with similar projects
- expand the team
I also opened an issue with a list of tasks for releasing the report.
Paolo Amoroso
Dec 11, 2025, 4:37:13 AM (5 days ago) Dec 11
to Medley Interlisp core
I copied the outline to a new document to hold the draft of the report, then copied to it Ryan's and my themes and goals:
Feel free to directly edit the draft, if you need edit access just let me know.
Larry Masinter
Dec 13, 2025, 8:12:44 PM (3 days ago) Dec 13
to Paolo Amoroso, Medley Interlisp core
GitHub Copilot Chat Assistant — summary for Interlisp/medley (calendar year 2025)
Quick notes about coverage
- The GitHub API responses used to build this summary are paginated. There are 228 issues and 197 pull requests that match created:2025-01-01..2025-12-31; the tool returns up to 100 results per query. The item list I inspected was therefore incomplete — I saw many representative items but not every single issue/PR. If you want a complete tabulation (counts by state/label/author, CSV, or the full item text), I can fetch the remaining pages and produce that output.
- You can view the live full search results in GitHub:
- Issues: https://github.com/search?q=is:issue+repo:Interlisp/medley+created:2025-01-01..2025-12-31&sort=created&order=asc
- PRs: https://github.com/search?q=is:pr+repo:Interlisp/medley+created:2025-01-01..2025-12-31&sort=created&order=asc
High-level totals (from the search metadata)
- Issues created in 2025 (calendar year): 228
- Pull requests created in 2025 (calendar year): 197
(Again: these totals come from the repository search metadata; my inspected sample was limited to the API page size.)
Top themes and hotspots (observed across issues and PRs)
1. TEdit (text editor)
- Many bug reports and feature discussions: caret/selection/line positioning, find & substitute, function-key and Meta/arrow-key handling, window-splitting UI, page layout / page numbers, character looks and large fonts.
- Large refactor / feature PRs: a new TEdit key-binding architecture and improved initial window-region heuristics (example: PR #2070 — merged).
- Representative issues: #1950, #1952, #1953, #1962, #1985, #2055, #2075, #2062.
2. Loadup scripts, build, and maiko integration
- Ongoing work to make loadups restartable, robust on different systems (WSL, macOS), and to fix ordering/copying of generated sysouts.
- Several substantive PRs revamping loadup scripts and fixing build/workflow issues (big merged PRs and follow-ups).
- Representative issues/PRs: issues #1954, #1959, #1986, #1993, #2061; major PRs #2111 (extensive loadup revamp, merged), #2160 (fix ordering), and supporting PRs (#1958 draft → replaced).
3. Fonts, BDF -> display fonts, encoding (XCCS/Unicode/MCCS)
- Many bug reports and development items around READ-BDF, BDF-to-displayfont conversion, kerning/width, PostScript embedding, and a longer-running effort to cleanly map XCCS ↔ Unicode ↔ internal Medley codes (MCCS).
- PRs adding BDF handling, fixes for Monaco BDF, fixes for kerning/width, and design discussions about permanent character-set extension.
- Representative issues/PRs: #2107, #2108, #2109, #2115, #2120 (design discussion), PRs #2015, #2108, #2127.
4. Character encoding / Unicode / XCCS
- Discussion and work on XCCS-to-Unicode mappings and on how Medley should treat unmapped codes; utilities for mapping and consistent behavior when round-tripping Unicode.
- Representative issues: #1971, #2025, #2120.
5. HCFILES and files.interlisp.org (documentation / generated PDFs)
- Problems with HCFILES runs (GitHub Actions), blank/incorrect PDFs, index generation, and files.interlisp.org content; multiple fixes and improvements to the HCFILES workflow plus scripts to reliably produce the website outputs.
- Representative issues/PRs: #2067, #2072, #2139; PRs #2156 and related fixes.
6. Online Medley / keyboard / input integration
- Issues around Medley Online (noVNC) and keyboard mapping (arrow keys, Meta combos); specific problems with typing parentheses under keyboard swap options on online.interlisp.org.
- Representative issues: #1976, #1985, #2054, #2059.
7. Documentation, website, and outreach
- Requests to improve interlisp.org links, add landing pages for bibliography entries, make manuals available in repo; reorganizing lispusers/ docs and MAN/HC generation.
- Representative issues/PRs: #2017, #2019, #2104, #2102.
8. Miscellaneous module work and housekeeping
- Many smaller issues and PRs: PSEUDOHOSTS behavior, LOAD/FILESLOAD quirks, module reorganizations (moving files to lispusers/talk, adding missing files to fuller database), fixes for EDITCALLERS, JSON-GET, DINFO, etc.
- Examples: #1961 (script typo), #2151/#2154/#2156 (pseudohosts and files), PRs #2140 (JSON-GET array indexing), #2146 (DINFO cycle handling).
Notable merged PR highlights (representative examples)
- PR #1957 — "Shakedown of field menu items" (merged 2025-01-15) — fixes and improvements to MB.ADD and related field handling (addresses several field-related issues).
- PR #1997 — "lispusers DOCUMENT cleaned up and working with current Tedit" — fixes Document module errors.
- PR #2015 — "READ-BDF create FONTDESCRIPTOR and write DISPLAYFONT files" — substantial BDF/font work (merged).
- PR #2070 — "TEDIT: New architecture for key bindings, plus better suggestions for initial window regions" (merged 2025-03-31) — major TEdit architecture change.
- PR #2111 — "Extensive loadup scripts revamp" (merged 2025-04-26) — major rework of loadup tooling and workflow.
- PR #2119 — "Rmk88 split screen updates and color, eliminate reliance on STREAMHINT" (merged 2025-07-03) — split-screen and internal cleanup in TEdit.
- Multiple incremental PRs fixing build/HCFILES/site generation and platform issues (see PRs #2074, #2156, #2160, #2163).
Active contributors visible in the sample
- Frequent contributors: rmkaplan, fghalasz, MattHeffron, pamoroso, nbriggs, masinter, and others — contributors appear across code, docs, scripts, and font/encoding work.
Suggested next steps I can do for you
- Fetch the remaining pages (complete list of all 228 issues and all 197 PRs) and produce:
- a full CSV or spreadsheet with number, title, state, labels, assignee, created/closed dates, PR merge status
- counts by label, counts open vs closed, top contributors by number of PRs/issues
- timeline (monthly counts) for issues/PRs in 2025
- more-detailed summaries of selected areas (e.g., all TEdit items, all loadup/build items)
- Produce a brief "release-notes style" summary listing the most important fixes/merges and unresolved items to include in a 2025 project report.
Which of the above would you like next? (I can fetch the rest of the pages and produce a complete CSV or a detailed breakdown.)
Quick notes about coverage
- The GitHub API responses used to build this summary are paginated. There are 228 issues and 197 pull requests that match created:2025-01-01..2025-12-31; the tool returns up to 100 results per query. The item list I inspected was therefore incomplete — I saw many representative items but not every single issue/PR. If you want a complete tabulation (counts by state/label/author, CSV, or the full item text), I can fetch the remaining pages and produce that output.
- You can view the live full search results in GitHub:
- Issues: https://github.com/search?q=is:issue+repo:Interlisp/medley+created:2025-01-01..2025-12-31&sort=created&order=asc
- PRs: https://github.com/search?q=is:pr+repo:Interlisp/medley+created:2025-01-01..2025-12-31&sort=created&order=asc
High-level totals (from the search metadata)
- Issues created in 2025 (calendar year): 228
- Pull requests created in 2025 (calendar year): 197
(Again: these totals come from the repository search metadata; my inspected sample was limited to the API page size.)
Top themes and hotspots (observed across issues and PRs)
1. TEdit (text editor)
- Many bug reports and feature discussions: caret/selection/line positioning, find & substitute, function-key and Meta/arrow-key handling, window-splitting UI, page layout / page numbers, character looks and large fonts.
- Large refactor / feature PRs: a new TEdit key-binding architecture and improved initial window-region heuristics (example: PR #2070 — merged).
- Representative issues: #1950, #1952, #1953, #1962, #1985, #2055, #2075, #2062.
2. Loadup scripts, build, and maiko integration
- Ongoing work to make loadups restartable, robust on different systems (WSL, macOS), and to fix ordering/copying of generated sysouts.
- Several substantive PRs revamping loadup scripts and fixing build/workflow issues (big merged PRs and follow-ups).
- Representative issues/PRs: issues #1954, #1959, #1986, #1993, #2061; major PRs #2111 (extensive loadup revamp, merged), #2160 (fix ordering), and supporting PRs (#1958 draft → replaced).
3. Fonts, BDF -> display fonts, encoding (XCCS/Unicode/MCCS)
- Many bug reports and development items around READ-BDF, BDF-to-displayfont conversion, kerning/width, PostScript embedding, and a longer-running effort to cleanly map XCCS ↔ Unicode ↔ internal Medley codes (MCCS).
- PRs adding BDF handling, fixes for Monaco BDF, fixes for kerning/width, and design discussions about permanent character-set extension.
- Representative issues/PRs: #2107, #2108, #2109, #2115, #2120 (design discussion), PRs #2015, #2108, #2127.
4. Character encoding / Unicode / XCCS
- Discussion and work on XCCS-to-Unicode mappings and on how Medley should treat unmapped codes; utilities for mapping and consistent behavior when round-tripping Unicode.
- Representative issues: #1971, #2025, #2120.
5. HCFILES and files.interlisp.org (documentation / generated PDFs)
- Problems with HCFILES runs (GitHub Actions), blank/incorrect PDFs, index generation, and files.interlisp.org content; multiple fixes and improvements to the HCFILES workflow plus scripts to reliably produce the website outputs.
- Representative issues/PRs: #2067, #2072, #2139; PRs #2156 and related fixes.
6. Online Medley / keyboard / input integration
- Issues around Medley Online (noVNC) and keyboard mapping (arrow keys, Meta combos); specific problems with typing parentheses under keyboard swap options on online.interlisp.org.
- Representative issues: #1976, #1985, #2054, #2059.
7. Documentation, website, and outreach
- Requests to improve interlisp.org links, add landing pages for bibliography entries, make manuals available in repo; reorganizing lispusers/ docs and MAN/HC generation.
- Representative issues/PRs: #2017, #2019, #2104, #2102.
8. Miscellaneous module work and housekeeping
- Many smaller issues and PRs: PSEUDOHOSTS behavior, LOAD/FILESLOAD quirks, module reorganizations (moving files to lispusers/talk, adding missing files to fuller database), fixes for EDITCALLERS, JSON-GET, DINFO, etc.
- Examples: #1961 (script typo), #2151/#2154/#2156 (pseudohosts and files), PRs #2140 (JSON-GET array indexing), #2146 (DINFO cycle handling).
Notable merged PR highlights (representative examples)
- PR #1957 — "Shakedown of field menu items" (merged 2025-01-15) — fixes and improvements to MB.ADD and related field handling (addresses several field-related issues).
- PR #1997 — "lispusers DOCUMENT cleaned up and working with current Tedit" — fixes Document module errors.
- PR #2015 — "READ-BDF create FONTDESCRIPTOR and write DISPLAYFONT files" — substantial BDF/font work (merged).
- PR #2070 — "TEDIT: New architecture for key bindings, plus better suggestions for initial window regions" (merged 2025-03-31) — major TEdit architecture change.
- PR #2111 — "Extensive loadup scripts revamp" (merged 2025-04-26) — major rework of loadup tooling and workflow.
- PR #2119 — "Rmk88 split screen updates and color, eliminate reliance on STREAMHINT" (merged 2025-07-03) — split-screen and internal cleanup in TEdit.
- Multiple incremental PRs fixing build/HCFILES/site generation and platform issues (see PRs #2074, #2156, #2160, #2163).
Active contributors visible in the sample
- Frequent contributors: rmkaplan, fghalasz, MattHeffron, pamoroso, nbriggs, masinter, and others — contributors appear across code, docs, scripts, and font/encoding work.
Suggested next steps I can do for you
- Fetch the remaining pages (complete list of all 228 issues and all 197 PRs) and produce:
- a full CSV or spreadsheet with number, title, state, labels, assignee, created/closed dates, PR merge status
- counts by label, counts open vs closed, top contributors by number of PRs/issues
- timeline (monthly counts) for issues/PRs in 2025
- more-detailed summaries of selected areas (e.g., all TEdit items, all loadup/build items)
- Produce a brief "release-notes style" summary listing the most important fixes/merges and unresolved items to include in a 2025 project report.
Which of the above would you like next? (I can fetch the rest of the pages and produce a complete CSV or a detailed breakdown.)
--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lispcore/CAGi1hzuJFpn2iHYmM5uFNPd7egrJoi_JzFUyJDGv5K2t-GADbw%40mail.gmail.com.
Nick Briggs
Dec 13, 2025, 9:23:43 PM (3 days ago) Dec 13
to masinter, Paolo Amoroso, Lisp Core
That misses the 17 PRs for Maiko (and any other repositories where the issue is in Medley, but the PR is for the non-Medley repo).
To view this discussion visit https://groups.google.com/d/msgid/lispcore/CAKq15vccULK-Ceo7NdQhEbtmK9--h6h3sUw1%2BymTH3UmeQm3_A%40mail.gmail.com.
Larry Masinter
Dec 14, 2025, 12:21:29 PM (2 days ago) Dec 14
to Nick Briggs, masinter, Paolo Amoroso, Lisp Core
I was just surprised by the availability of different AI engines to answer questions about repository content. This was just an initial prompt -- and not using the results except perhaps as a check for important topics that might have been left out.
--
To view this discussion visit https://groups.google.com/d/msgid/lispcore/08D2E2C2-69F7-4D8B-8665-41C5C7DC8A7A%40gmail.com.
Reply all
Reply to author
Forward
0 new messages