unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org, Jean Louis <bugs@gnu.support>,
	"Perry E. Metzger" <perry@piermont.com>,
	qhong@mit.edu
Subject: Re: Collaborative editing.
Date: Thu, 19 Aug 2021 16:18:28 +0200	[thread overview]
Message-ID: <20210819141828.ahdhf6xllaqjtqti@Ergus> (raw)
In-Reply-To: <87pmu9srrr.fsf@posteo.net>

On Thu, Aug 19, 2021 at 09:33:28AM +0000, Philip Kaludercic wrote:
>Ergus <spacibba@aol.com> writes:
>
>> Could we try to add crdt to Elpa? Is the author somehow opposed to do the paperwork or so?
>
>The package still seems to be on version 0.0.0, and the HACKING[0] file
>indicates that a few intended items are not implemented yet. It might

>make sense to push for a preliminary version to be published as to
>provide a basic collaborative environment available on ELPA (or NonGNU
>ELPA if necessary), and then later work on full-compatibility.

This is the point. When some users know about the package searching in
the packages-list; maybe they will want to collaborate or report issues,
so it won't becomes a single man effort. IMHO a package doesn't really
exist until it is in Elpa or at least Melpa.

Otherwise in a couple of years there will be someone starting again
another similar effort from scratch.
>
>[0] https://code.librehq.com/qhong/crdt.el/-/raw/master/HACKING.org
>
>> On August 15, 2021 7:46:43 AM GMT+02:00, Jean Louis <bugs@gnu.support> wrote:
>>>* Perry E. Metzger <perry@piermont.com> [2021-08-13 02:44]:
>>>> I know there have been some experiments with collaborative editing modes in
>>>> the past that were written purely in Elisp but none seem to be currently
>>>> maintained and I'm not sure if any were actually very good to begin with.
>>>
>>>CRDT works just fine and is well maintained, you can contact author
>>>Qiantan Hong <qhong@mit.edu> at any time you wish.
>>>
>>>Do:
>>>
>>>$ git clone https://code.librehq.com/qhong/crdt.el.git
>>>
>>>Let me know if you need any help or assistance to start with
>>>collaborative editing.
>>>
>>>
>>>--
>>>Jean
>>>
>>>Take action in Free Software Foundation campaigns:
>>>https://www.fsf.org/campaigns
>>>
>>>In support of Richard M. Stallman
>>>https://stallmansupport.org/
>>>
>
>-- 
>	Philip Kaludercic



  reply	other threads:[~2021-08-19 14:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 23:43 Collaborative editing Perry E. Metzger
2021-08-13  5:32 ` Tim Cross
2021-08-13  6:40 ` Eli Zaretskii
2021-09-01  6:32   ` Ag Ibragimov
2021-09-01 11:56     ` Search for message-id (was: Collaborative editing.) Eli Zaretskii
2021-08-15  5:46 ` Collaborative editing Jean Louis
2021-08-15 11:24   ` Ergus
2021-08-19  9:32     ` Philip Kaludercic
2021-08-19  9:33     ` Philip Kaludercic
2021-08-19 14:18       ` Ergus [this message]
2021-08-19 14:38         ` dick
2021-08-19 15:19         ` Perry E. Metzger
2021-08-19 15:56           ` Eli Zaretskii
2021-08-19 15:36         ` Philip Kaludercic
2021-08-28  8:41           ` Qiantan Hong
2021-08-28 11:40             ` Philip Kaludercic
2021-08-28 11:53               ` Qiantan Hong
2021-08-28 12:14                 ` Philip Kaludercic
2021-08-28  9:17           ` Qiantan Hong
  -- strict thread matches above, loose matches on Subject: below --
2020-05-30  7:17 What is the most useful potential feature which Emacs lacks? Van Ly
2020-05-31  7:10 ` Richard Stallman
2020-05-31 10:01   ` Van Ly
2020-05-31 12:49     ` excalamus--- via Emacs development discussions.
2020-06-01  9:11       ` Bastien
2020-06-01 15:03         ` Eli Zaretskii
2020-06-01 23:32           ` Bastien
2020-06-01 23:50             ` Jean-Christophe Helary
2020-06-06  9:42               ` Eli Zaretskii
2020-06-06  9:59                 ` Thibaut Verron
2020-06-06 10:18                   ` tomas
2020-06-07  3:36                     ` collaborative editing Richard Stallman
2020-06-07  9:28                       ` tomas

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210819141828.ahdhf6xllaqjtqti@Ergus \
    --to=spacibba@aol.com \
    --cc=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=perry@piermont.com \
    --cc=philipk@posteo.net \
    --cc=qhong@mit.edu \
    /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.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).