From: Caio Henrique <caiohcs0@gmail.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Implicit assumptions in the latest discussions
Date: Thu, 17 Sep 2020 12:29:12 -0300 [thread overview]
Message-ID: <87mu1owhfb.fsf@gmail.com> (raw)
In-Reply-To: <af35f13b-ec86-5f36-628c-cc4373fa02ca@grinta.net> (Daniele Nicolodi's message of "Thu, 17 Sep 2020 16:45:49 +0200")
Daniele Nicolodi <daniele@grinta.net> writes:
> I don't know where you got the impression that I am advocating for Emacs
> to be developed using Gitlab or Github. Advances in software carpentry
> (a buzzword that nicely encompasses what I am talking about here) best
> practices in the last 20 years expand to things completely unrelated to
> the use of Gitlab or Github. Unfortunately, hacking on Emacs still
> requires obliging to outdated conventions that only stand in the way of
> contributors.
I got the same impression, and most of these sites require non-free
JavaScript. What outdated conventions are you talking about then? I'm a
new contributor and I'm born close to ~2000. The "hardest" aspect of
contributing until now has been signing the copyright assignments, which
takes a couple of days and I'm currently doing it, but this also isn't
"hard".
Using Gnus made it easy to follow the mailing lists. Debbugs is also
easy to use to track bugs. So I can contribute to Emacs without having
to exit Emacs, it's very comfy IMO.
I also like the code style conventions like not using too long lines,
since I can look at 3 different buffers at the same time.
next prev parent reply other threads:[~2020-09-17 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 13:30 Implicit assumptions in the latest discussions Daniele Nicolodi
2020-09-17 14:01 ` Robert Pluim
2020-09-17 14:45 ` Daniele Nicolodi
2020-09-17 15:04 ` Arthur Miller
2020-09-17 15:09 ` Daniel Martín
2020-09-17 15:29 ` Caio Henrique [this message]
2020-09-17 15:32 ` Robert Pluim
2020-09-17 17:41 ` Eli Zaretskii
2020-09-17 19:31 ` Mingde (Matthew) Zeng
2020-09-18 7:45 ` Emanuel Berg via Emacs development discussions.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu1owhfb.fsf@gmail.com \
--to=caiohcs0@gmail.com \
--cc=daniele@grinta.net \
--cc=emacs-devel@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.