From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: release timelines (-extindex, JMAP, lei)
Date: Fri, 5 Mar 2021 22:20:19 +0000 [thread overview]
Message-ID: <20210305222019.GB1010@dcvr> (raw)
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.
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'm excited that it allows vendor extensions, which means our
git-show|solver /$INBOX_URL/$OBJECT_ID/s/ blob-reconstruction
endpoint can be exposed via JMAP.
* lei saved searches can probably done quick for 1.7,
but without full keywords support for externals...
* Dealing with per-message keywords and externals in lei
is going to be tough and delayed, I think:
https://public-inbox.org/meta/20210224204950.GA2076@dcvr/
("lei: per-message keywords and externals")
It may involve spinnning up a Python daemon to use
custom PostingSource since Search::Xapian doesn't support it;
and I don't expect anybody outside of FreeBSD to use SWIG Xapian.pm.
* lei has a bunch of rough edges and I'm not comfortable declaring
it as supported, especially when there's a risk of data loss to
users.
* .mailmap + Xapian synonym support would be nice in lei and
HTTP/IMAP/JMAP endpoints
In any case, I need to take a few days away to clear my head.
next reply other threads:[~2021-03-05 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 22:20 Eric Wong [this message]
2021-03-06 18:31 ` release timelines (-extindex, JMAP, lei) Kyle Meyer
2021-03-08 2:54 ` Eric Wong
2021-03-08 21:33 ` Konstantin Ryabitsev
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=20210305222019.GB1010@dcvr \
--to=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.
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).