From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging Jami (ex GNU Ring)
Date: Thu, 10 Jan 2019 07:18:45 -0500 [thread overview]
Message-ID: <87a7k81za2.fsf@gmail.com> (raw)
In-Reply-To: <87y37t4mxf.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 09 Jan 2019 21:05:00 +0100")
Hi Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> If there is no longer a 'Ring' project, then let's rule this out.
>
> The current state of affair is not so black & white: It's "Jami" on the web
> page, but everything else is stilled called "Ring": the library, the
> daemon, and
> I'm unsure about the client itself.
>
> It might change in the future.
Long term, Ring as a name would disappear completely to be replaced by
Jami. The Jami developers have so far focused on changing the bits that
were the most visible for the users, but they won't stop there.
I'd be happy to help you in packaging Jami; it's been lurking on my TODO
for far to long :-). I could start by packaging OpenDHT, which should
be relatively straightforward (and a dependency of Jami). What do you
think?
Maxim
next prev parent reply other threads:[~2019-01-10 12:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:50 Packaging Jami (ex GNU Ring) Pierre Neidhardt
2019-01-09 8:58 ` Gábor Boskovits
2019-01-09 9:03 ` Pierre Neidhardt
2019-01-09 15:03 ` Timothy Sample
2019-01-09 16:26 ` Pierre Neidhardt
2019-01-09 17:57 ` Timothy Sample
2019-01-09 18:10 ` Pierre Neidhardt
2019-01-09 18:14 ` Pierre Neidhardt
2019-01-09 19:18 ` Leo Famulari
2019-01-09 20:05 ` Pierre Neidhardt
2019-01-10 12:18 ` Maxim Cournoyer [this message]
2019-01-10 12:55 ` Pierre Neidhardt
2019-01-10 4:17 ` swedebugia
2019-01-10 5:41 ` swedebugia
2019-01-10 9:08 ` Pierre Neidhardt
2019-01-10 9:10 ` Pierre Neidhardt
2019-01-10 13:13 ` swedebugia
2019-01-10 13:19 ` Pierre Neidhardt
2019-01-10 20:13 ` Pierre Neidhardt
2019-01-11 15:02 ` swedebugia
2019-01-11 17:43 ` Pierre Neidhardt
2019-01-11 18:32 ` Pierre Neidhardt
2019-01-11 18:53 ` Pierre Neidhardt
2019-01-11 20:10 ` Pierre Neidhardt
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7k81za2.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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/guix.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).