From: "Loris Bennett" <email@example.com>
Subject: Re: Release Org 9.4.2
Date: Wed, 16 Dec 2020 16:13:53 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Eric S Fraga <email@example.com> writes:
> On Wednesday, 16 Dec 2020 at 13:04, Gustav Wikström wrote:
>> But to be fair, the collaboration features of GitHub surely would be a
>> BIG net positive if the goal is to attract contributions and gain a
>> bigger mindshare.
> Not necessarily. Some of us dislike web based tools intensely, in fact
> anything that does not work well in Emacs ;-).
> In practice, I will not participate in projects that, for instance, use
> slack or discourse or ... Requiring the use of github for interaction
> would lead to a reduction in the (albeit rather small) contributions I
> make to this project. A mailing list (or nntp) plus git is perfect for
> my working methods.
But even if a project is hosted on GitHub, you can still interact with
it just via Emacs, it is still Git after all.
One project I have made minor contributions to is EasyBuild, a framework
for managing the building and installation of (mainly) scientific
software, which is hosted on GitHub:
However, I can interact with it via Magit, and even if I don't use
Emacs, the project has command-line tools which allow the creation of a
pull request without the me having to know anything about GitHub or even
Obviously the EasyBuild people have put quite a lot of work into making
this possible and it is mainly to allow people to contribute
self-contained "recipes" for building particular pieces of software,
rather than work on the main code of the framework.
To be honest, last time I tried, responding to comments on pull-requests
didn't work so well via Emacs, so unfortunately I ended up having to
using the web-interface.
But on the other hand, they also have a mailing list, so there is
something for everyone ;-)
>> This is a hobby project and it would be cool if it could be something
>> else at least for someone!
> Why cool? What's cool is that so many contribute, in a wide range of
> ways, without some financial recompense!
This signature is currently under construction.
next prev parent reply other threads:[~2020-12-16 15:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 7:04 Release Org 9.4.2 Bastien
2020-12-14 14:10 ` Pankaj Jangid
2020-12-14 14:18 ` Bastien
2020-12-14 15:19 ` Pankaj Jangid
2020-12-15 11:38 ` Eric S Fraga
2020-12-15 13:58 ` Pankaj Jangid
2020-12-15 14:24 ` Bastien
2020-12-16 3:59 ` Pankaj Jangid
2020-12-16 6:19 ` Bastien
2020-12-16 7:00 ` Pankaj Jangid
2020-12-16 7:14 ` TEC
2020-12-16 13:04 ` Gustav Wikström
2020-12-16 13:49 ` Eric S Fraga
2020-12-16 14:11 ` Gustav Wikström
2020-12-16 14:50 ` Eric S Fraga
2020-12-16 15:05 ` Gustav Wikström
2020-12-29 9:42 ` TEC
2020-12-29 12:14 ` Gustav Wikström
2020-12-16 15:13 ` Loris Bennett [this message]
2020-12-16 19:01 ` Tim Cross
2020-12-17 13:27 ` Eric S Fraga
2020-12-17 15:32 ` Greg Minshall
2020-12-17 23:19 ` Samuel Wales
2020-12-16 14:56 ` Pankaj Jangid
2020-12-16 18:41 ` Tim Cross
2020-12-22 14:27 ` Lennart C. Karssen
2020-12-22 15:07 ` TEC
2020-12-22 16:18 ` Bastien
2020-12-22 19:46 ` Jean Louis
2020-12-15 21:12 ` Daniele Nicolodi
2020-12-16 5:19 ` Pankaj Jangid
2020-12-18 21:49 Asa Zeren
2020-12-21 12:25 ` Eric S Fraga
2021-01-02 22:45 ` TRS-80
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
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).