[[!meta title="Emacs core development: how it works"]]
[[!meta copyright="Copyright © 2023 Stefan Kangas"]]
[[!inline pages="internal(2023/info/core-nav)" raw="yes"]]

<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
<!-- You can manually edit this file to update the abstract, add links, etc. --->


# Emacs core development: how it works
Stefan Kangas

[[!inline pages="internal(2023/info/core-before)" raw="yes"]]

-   Why it is fun and exciting to contribute to Emacs
    -   We have easy bugs that anyone can fix, in random packages
    -   And extremely hard ones for experts in things like garbage
        collection, and compilers
-   We are not scary, in fact working to build a welcoming culture.
-   The nature of a public list
    -   Don't listen to random people being negative or hostile
    -   No response is not necessarily a bad thing
-   Cultural aspects of emacs-devel vs GitHub
-   How to behave (be polite, etc.)
-   Email vs forge, help wanted.
-   Why copyright assignment
-   Plans for Emacs 30 (maybe) - needs coordinating with Eli

If I have more time, I'd like to cover more things, for example:

-   GNU ELPA vs NonGNU ELPA - why and how
    -   Our plans for GNU ELPA going forward (bundle stuff in tarballs)
-   The future of Emacs: a vision

Basically, I want to do everything I can to inspire people to join core
development and to lower the barrier to participating.  In effect trying
to work on "bridging the gap" that we have identified exists between
emacs-devel and the community.

About the speaker:

Stefan Kangas is one of the Emacs core maintainers.



[[!inline pages="internal(2023/info/core-after)" raw="yes"]]

[[!inline pages="internal(2023/info/core-nav)" raw="yes"]]