From: Ypo <email@example.com> To: Jean Louis <firstname.lastname@example.org> Cc: Org-mode <email@example.com> Subject: Re: (✿╹◡╹) there are always ways to go - Re: Sad tweet Date: Tue, 25 May 2021 03:07:51 +0000 (UTC) [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YKwUKIWRAq/aZ7sj@protected.localdomain> I think he is the creator of the magit package. May 24, 2021 23:02:56 Jean Louis <email@example.com>: > * Ypo <firstname.lastname@example.org> [2021-05-24 00:30]: >> I've read this: >> >> "Contributing to Emacs is so frustrating. It's not worth it for minor things and if I cannot get some experience and confidence with minor things, then I likely won't ever make major contributions." >> https://twitter.com/magit_emacs/status/1396536686570610697?s=19 > > Alright, but no need for desperation. There is a way forward. > > Make your own package, see (info "(elisp) Packaging") > > As when you make your own package you are extending Emacs. > > Then apply the package to be included in GNU ELPA: > https://elpa.gnu.org on email@example.com mailing list. > > That way you are contributing to GNU Emacs. > > Your package can improve some functions and thus get kudos from other > users. > > Then it becomes so much easier to point out to your improvements and > propose them to mainstream Emacs or Org mode. > > -- > Jean > > Take action in Free Software Foundation campaigns: > https://www.fsf.org/campaigns > > Sign an open letter in support of Richard M. Stallman > https://stallmansupport.org/
next prev parent reply other threads:[~2021-05-25 3:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-23 21:28 Ypo 2021-05-24 3:38 ` bandali 2021-05-24 7:12 ` Kévin Le Gouguec 2021-09-25 14:29 ` Bastien 2021-09-25 14:34 ` Timothy 2021-09-25 14:59 ` Bastien 2021-05-24 21:01 ` (✿╹◡╹) there are always ways to go - " Jean Louis 2021-05-25 3:07 ` Ypo [this message] 2021-05-25 6:51 ` Jean Louis 2021-05-26 14:10 ` Matt Price 2021-09-26 6:57 ` Corwin Brust
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: (✿╹◡╹) there are always ways to go - Re: Sad tweet' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).