From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: release timelines (-extindex, JMAP, lei)
Date: Mon, 8 Mar 2021 16:33:32 -0500 [thread overview]
Message-ID: <20210308213332.w3aoum7nnsri5zh3@chatter.i7.local> (raw)
In-Reply-To: <20210305222019.GB1010@dcvr>
On Fri, Mar 05, 2021 at 10:20:19PM +0000, Eric Wong wrote:
> So I think the -extindex stuff might be stable and suitable for
> general consumption. The HTML WWW UI around -extindex has some
> rough edges but nothing that would take too much effort to fix.
\o/
> But I'm deeply worried about unleashing a new on-disk format
> that's insufficient and being stuck supporting it forever
> (as I am with v1 inboxes)...
>
> * JMAP is going to be a more effort, but I think our current
> on-disk data model is OK or at least extensible enough for it.
> I might delay JMAP until 1.8.
>
> JMAP will be significantly less effort than inventing something
> new (and one-off) with GraphQL or REST. And it would be less
> effort for client authors, as well; since client code can be
> used for non-public-inbox servers, too.
I don't really have any specific opinion on this matter. I don't really know
of any other provider outside of Fastmail that uses JMAP, but it *is* a
published IETF standard around RFC2822 messages, so it makes sense to use it
for this purpose.
> * lei saved searches can probably done quick for 1.7,
> but without full keywords support for externals...
I was wondering if lei should be part of the same suite as public-inbox proper
as opposed to a standalone (or interdependent) client tool. Unless I'm
mistaken, someone running a public-inbox origin or mirror server wouldn't
necessarily be an active lei user. Decoupling them from each-other would allow
different release cadence, no?
> In any case, I need to take a few days away to clear my head.
Please take care!
Thanks for your effort on this project.
Best,
-K
next prev parent reply other threads:[~2021-03-08 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 22:20 release timelines (-extindex, JMAP, lei) Eric Wong
2021-03-06 18:31 ` Kyle Meyer
2021-03-08 2:54 ` Eric Wong
2021-03-08 21:33 ` Konstantin Ryabitsev [this message]
2021-03-08 22:16 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210308213332.w3aoum7nnsri5zh3@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/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://80x24.org/public-inbox.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).