NonGNU ELPA - Questions
summary
Explains why NonGNU ELPA exists now: a real case where s.el symbol namespace conflict breaks Emacs and the chosen remedy is a symbol-renaming wrapper that loads renamed code so existing users work but global names stay free. Archive is partially live, organized as per-package repos (not one monolith), no copyright assignment required, packages get reviewed individually, MELPA integration is rejected, license compliance is enforced, and basic security and automated fetching still need design.
AI-written summary · about
chapters (27)
- 0:00Introduction and first question
- 1:04Namespace conflict with s.el
- 4:21NonGNU ELPA existence and setup
- 6:30Benefits and MELPA integration
- 9:28Licensing and free software criteria
- 12:03Gender-neutral pronouns in writing
- 15:01Package inclusion without maintainer consent
- 16:52Security considerations in NonGNU ELPA
- 17:57Favorite distro and free software
- 19:29Decision-making authority for NonGNU ELPA
- 20:12Non-free sites and GitHub links
- 22:22GNU AGPL for Emacs packages
- 22:42Favorite programming language
- 24:16Response to harassment accusation
- 25:21Diversity and Emacs extensibility
- 26:48Word processing features in Emacs
- 27:14Working for non-free software companies
- 29:31Advice on free software stewardship
- 32:28Tools from pre-UNIX days
- 33:54Fortune-tellers and future predictions
- 35:25Future of GNU Emacs and compromises
- 37:15Moving packages between core and ELPA
- 38:41Higher education and non-free software
- 41:56Saying no to non-free software
- 44:11Personal use of Emacs
- 45:18Other projects beyond NonGNU ELPA
- 46:22Closing remarks
related talks
46mElm & Open Source: What's Next?
51mEPEL Renewed
34mRelicensing: When Your Open Source Tool Turns to the Dark Side
48mThe ELISA Project – Enabling Open Source in Safety-Critical Applications
42mThe Good, the Bad and NPX
48mThe ELISA Project – Enabling Open Source in Safety-Critical Applications
01h 09mThe Beman Project: Bringing C++ Standard Libraries to the Next Level
42mWhen Your Open Source Tool Turns to the Dark Side
