From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-orgmode@gnu.org, bzg@gnu.org, Corwin Brust <corwin@bru.st>,
Krupal <krupalinbox@gmail.com>
Cc: Joseph Turner <joseph@ushin.org>
Subject: [DISCUSSION] Contributing policy for WORG
Date: Sun, 19 Jan 2025 08:11:53 +0000 [thread overview]
Message-ID: <875xmbdxyu.fsf@localhost> (raw)
Hi,
Corwin recently noticed that our
https://orgmode.org/worg/worg-about.html page is not very consistent
about whom and how should contribute to WORG.
One part of that page suggests to "Create an account on Sourcehut" and
then push changes freely, while another part suggests going through the
mailing list.
My first reflex was to make things consistent with Org code
contributions, but I recall that Bastien had somewhat different ideas
about WORG contributions - more in line with "free to push changes" and
generally with a spirit of wiki pages (Bastien, correct me if I am
making things up).
Now, thinking about it, I do believe that our general goal should be
making it easier for users to push changes to WORG - easier than
contributing code. And these days creating an account might be easier
for people compared to writing to a mailing list.
Maybe we can simplify things even more by settings something up so that
people can download, edit, and upload WORG pages right from Emacs. For
example, hyperdrive might be used as an alternative to git workflow,
especially if we can cook some kind of setup via a simple M-x <dwm>
command. (see <https://breatheoutbreathe.in/blog/2024-12-16-mirror-worg-to-a-hyperdrive.html>)
WDYT?
--
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
reply other threads:[~2025-01-19 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=875xmbdxyu.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-orgmode@gnu.org \
--cc=joseph@ushin.org \
--cc=krupalinbox@gmail.com \
/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).