From: Joseph Turner <joseph@ushin.org>
To: Bastien Guerry <bzg@gnu.org>
Cc: jman <emacs-orgmode@city17.xyz>,
Ihor Radchenko <yantar92@posteo.net>,
emacs-orgmode@gnu.org, Corwin Brust <corwin@bru.st>,
Krupal <krupalinbox@gmail.com>
Subject: Re: [DISCUSSION] Contributing policy for WORG
Date: Mon, 27 Jan 2025 17:52:36 -0800 [thread overview]
Message-ID: <87ikpzso0r.fsf@ushin.org> (raw)
In-Reply-To: <87zfjky7q9.fsf@bzg.fr> (Bastien Guerry's message of "Tue, 21 Jan 2025 07:57:34 +0100")
Bastien Guerry <bzg@gnu.org> writes:
> Joseph Turner <joseph@ushin.org> writes:
>
>>> 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.
>
> Between the good old patch-based contribution way and the experimental
> peer-to-peer way, there is probably yet another (complementary) way.
>
> What about gollum?
>
> https://github.com/gollum/gollum
>
> From what I understand, it would provide a way to let users modify Org
> files by editing them from a web interface (without Git knowledge), on
> top of rendering the .org files as HTML pages.
Interesting project. Would you want to allow contributions from anyone?
Or would you need to set up auth also? I'm not sure if contributions
automatically push master.
> Would someone try to set up a proof-of-concept?
next prev parent reply other threads:[~2025-01-28 1:54 UTC|newest]
Thread overview: 10+ 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
2025-01-21 6:57 ` Bastien Guerry
2025-01-28 1:52 ` Joseph Turner [this message]
2025-01-28 8:07 ` Bastien Guerry
2025-01-28 20:48 ` Joseph Turner
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=87ikpzso0r.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).