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: Tue, 28 Jan 2025 12:48:21 -0800 [thread overview]
Message-ID: <87lduuu0kq.fsf@ushin.org> (raw)
In-Reply-To: <87frl3cqfb.fsf@bzg.fr> (Bastien Guerry's message of "Tue, 28 Jan 2025 09:07:20 +0100")
Bastien Guerry <bzg@gnu.org> writes:
> Hi Joseph,
>
> Joseph Turner <joseph@ushin.org> writes:
>
>>> 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?
>
> If someone has the time to install a test-instance Gollum, then we can
> experiment with it and see if it feels like a good way to open Worg to
> more contributions. If sensible regarding spam and security, yes, I'd
> like anyone to be able to contribute.
I think it's a worthy experiment. Right now, I cannot volunteer to set
this up, but I'll be happy to test it out.
>> I'm not sure if contributions automatically push master.
>
> I'm not sure either, the experiment could tell.
prev parent reply other threads:[~2025-01-28 20:49 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
2025-01-28 8:07 ` Bastien Guerry
2025-01-28 20:48 ` Joseph Turner [this message]
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=87lduuu0kq.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).