From: Joseph Turner <joseph@ushin.org>
To: jman <emacs-orgmode@city17.xyz>
Cc: Ihor Radchenko <yantar92@posteo.net>,
emacs-orgmode@gnu.org, bzg@gnu.org,
Corwin Brust <corwin@bru.st>, Krupal <krupalinbox@gmail.com>
Subject: Re: [DISCUSSION] Contributing policy for WORG
Date: Mon, 20 Jan 2025 18:05:14 -0800 [thread overview]
Message-ID: <878qr4j50l.fsf@ushin.org> (raw)
In-Reply-To: <87wmep6p8h.fsf@city17.xyz> (jman's message of "Tue, 21 Jan 2025 00:26:54 +0100")
jman <emacs-orgmode@city17.xyz> writes:
> Joseph Turner <joseph@ushin.org> writes:
>
>> Thanks for the suggestion! I imagine such a command would do this:
> (...)
>
> I am not a Worg contributor but such workflow would definitively scare me off.
Understandable :) If we added some sort of bleeding-edge peer-to-peer
way to contribute to worg, it would certainly be in addition to
tried-and-true methods like emailed patches.
> Just out of curiosity: what is wrong with a git workflow to contribute to Worg?
I really like the git+email workflow. Perhaps we could also benefit
from something like https://git-send-email.io for teaching new Emacs
users how to submit patches with Emacs. Maybe it could simply teach
people how to use M-x report-emacs-bug or M-x package-vc-prepare-patch.
I think the biggest hurdle is setting up Emacs for email, so maybe we
need a wizard command for that.
Joseph
next prev parent reply other threads:[~2025-01-21 2:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 8:11 [DISCUSSION] Contributing policy for WORG Ihor Radchenko
2025-01-20 21:57 ` Joseph Turner
2025-01-20 22:27 ` Bastien Guerry
2025-01-20 22:34 ` Corwin Brust
2025-01-20 23:26 ` jman
2025-01-21 2:05 ` Joseph Turner [this message]
2025-01-21 6:57 ` Bastien Guerry
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 \
--in-reply-to=878qr4j50l.fsf@ushin.org \
--to=joseph@ushin.org \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-orgmode@city17.xyz \
--cc=emacs-orgmode@gnu.org \
--cc=krupalinbox@gmail.com \
--cc=yantar92@posteo.net \
/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 public 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).