From: Joseph Turner <joseph@ushin.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 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 13:57:03 -0800 [thread overview]
Message-ID: <87msfli1xs.fsf@breatheoutbreathe.in> (raw)
In-Reply-To: <875xmbdxyu.fsf@localhost> (Ihor Radchenko's message of "Sun, 19 Jan 2025 08:11:53 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> 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>)
Thanks for the suggestion! I imagine such a command would do this:
- install hyperdrive.el
- download and install external gateway program with hyperdrive-install
- open worg hyperdrive. We could use the hyperdrive I created for the
blog post hyper://bpb1bq6sdfajw4bok7k9tdmrq153pbwzcyfkrqrfxw3hhihyddhy/
which is also accessible here:
https://bpb1bq6sdfajw4bok7k9tdmrq153pbwzcyfkrqrfxw3hhihyddhy.hyper.hypha.coop/
but I'd suggest the worg maintainers (Ihor) create a new hyperdrive that
mirrors worg, so that the maintainers control the keys.
- Create a new hyperdrive which mirrors the maintainers' worg hyperdrive.
Then the users edit their hyperdrive and then run a second command to:
- send the URL of the user-created hyperdrive to the maintainers. How?
Via email? hyperdrive.el doesn't currently have a way to "push"
changes to someone else, only "pull", although this could be added.
For the worg use-case, where all changes need to go back to a central
hub (the worg maintainers and the central git repository), I think
hyperdrive might not help all that much.
Hyperdrive is useful for distributing content like a personal website on
a peer-to-peer network. The hyperdrive.el Emacs interface adds things
like Org mode link handling, but it doesn't support collaboratively
editing text documents. [ The hypercore stack does include the
https://github.com/holepunchto/autobase library for creating multiwriter
data structures, but significant effort would be required to create an
auto-merging program on top of hyperdrive. Here's an example of the
kind of multiwriter programs which can be written with autobase:
https://github.com/hypercore-protocol/p2p-multiwriter-with-autobase ]
From Ihor's direct email to me:
> I imagined that we can simply point users to
> 1. install hyperdrive from ELPA
> 2. M-x magic
> 3. View/edit/add WORG pages locally in Emacs
> 4. <more magic> (involving me adding user hyperdrives to sync with mine,
> where I can push upstream)
> 5. The edits appear on WORG website
Something like this might work for one-time contributions, but
subsequent contributions would require restarting the process, since
after the maintainers copy the desired changes, there's currently no way
merge the two hyperdrive histories.
Perhaps someone wants to write a CRDT designed to handle Org documents. :)
Joseph
next prev parent reply other threads:[~2025-01-20 21:58 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 [this message]
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
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=87msfli1xs.fsf@breatheoutbreathe.in \
--to=joseph@ushin.org \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--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).