[emacs-berlin] Proposal for the next meetup

jman emacs-berlin at city17.xyz
Thu Sep 26 07:22:28 UTC 2024


I want to thank everyone that tonight actively participated and patiently guided us to an effective 
workflow to work on packages. I am really happy and have learned a few interesting things.
I am thinking to some improvementes for the next time (besides the technical problems about internet 
connection and screen sharing):

1. Maybe try working on a less widely used packages. For some reason, I feel intimidated submitting 
a patch to the `smartparens` maintainer, but I feel more confident doing the same for a package that 
has less impact on the ecosystem.

2. Preparing a local working copy of `smartparens` and satisfy its dependencies was easy (we just 
needed `dash` and the latest version worked fine) but I wonder if it can get trickier with other 
packages. Packages have dependencies (and transitional dependencies!) and I am not sure how a 
package "X" pins a specific version of a dependency "Y" and "Z". I am thinking to dependencies that 
are not Emacs built-ins. Is that a thing in the Emacs world? I can't make up an example right now 
but I had headaches with dependencies from Javascript (npm) and Rust projects (cargo).

Anyway, see you next time!

Best,


More information about the emacs-berlin mailing list