From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: Re: lei-managed pseudo mailing lists Date: Mon, 26 Apr 2021 18:47:17 +0000 [thread overview] Message-ID: <20210426184717.GA29112@dcvr> (raw) In-Reply-To: <email@example.com> Konstantin Ryabitsev <firstname.lastname@example.org> wrote: > On Mon, Apr 26, 2021 at 05:37:26PM +0000, Eric Wong wrote: > > > The latter is specifically something I think would be of interest to kernel > > > folks, so I envision that we'd have something like the following: > > > > > > - a maintainer publishes a configuration file we can pass to lei > > > > The command-line might be enough, the pathname of the current > > state/config file is a bit tricky and tied to its output. > > I suppose "lei import-search" can be a command, though... > > Excellent, excellent. How well does it deal with the situation when the search > parameters change? "lei edit-search" can be used to zero the maxuid parameters; and normal v2 deduplication will prevent duplicates from showing up. It's not automatic, though; though that probably seems like a good idea to keep manual, anyways, given the step 2. below. > > > - our backend lei process uses all of lore.kernel.org sources to create and > > > continuously update a new public-inbox repository with matching search > > > results > > > > There's already some accomodations for that in LeiSavedSearch > > which can present itself as a PublicInbox::Inbox-ish object to > > PublicInbox::WWW (untested). > > > > Searching an within LSS isn't implemented, yet, but I think it's > > doable w/o extra Xapian storage. > > > > However, git object storage isn't duplicated, which is nice for > > local use (instaweb-like), but supporting clone/fetch isn't as > > natural... > > I'm thinking we need the ability to make it a real clonable repository -- > perhaps without its own xapian index? Actual git repositories aren't large, > especially if they are only used for direct git operations. Disk space is > cheap, it's the IO that's expensive. :) True, though cache overheads hurt a bit. I also wonder if lei can increase traffic to public-inbox-<imapd|nntpd> to reduce the need/use of "git clone". > If these are real clonable repositories, then it would be easy for people to > set up replication for just the curated content people want. Understood. Using --output v2publicinbox:... w/o --shared is totally doable. > > Perhaps supporting a v2 inbox as an lei q output destination > > is in order: > > > > lei q --output v2publicinbox:/path/to/v2 --shared SEARCH_TERMS > > > > --shared would be "git clone --shared", the new v2 inbox can > > use ~/.cache/lei/all_locals_ever.git/ as an alternate and not > > duplicate space for blobs. > > Not really worried about deduping blobs, but I'm wondering how to make it work > well when search parameters change (see above). E.g.: > > 1. we create the repo with one set of parameters > 2. maintainer then broadens it up to include something else > 3. maintainer then decides that it's now *way* too much and narrows it down again > > We don't really want step 2 to lead to a permanent ballooning of the > repository, so perhaps all query changes should force-append a dt: with the > open-ended datetime of the change? Or do you already have a way to deal with > this situation? The aforementioned maxuid prevents stuff that's too old from being seen. Otherwise, there's always "public-inbox-learn rm". > > > - we set up a mlmmj list that doesn't receive any direct mail but is only fed > > > from saved search results; people can subscribe/unsubscribe as they would > > > with any other mlmmj list > > > > > > Any particular reason this wouldn't work? > > > > Nope :) As long as all the data formats can interoperate > > (mostly RFC5322/2822). "lei convert" is nice, too :) > > Great! I believe this will help untangle the current situation with "where > should I send this kernel patch". > > I want "just send it to email@example.com" to be a valid option > again. Participating subsystems can then define what patches they want to see > by setting up pseudo-lists and letting participating reviewers/maintainers > subscribe to them via their preferred mail delivery mechanism. Yup, that seems easiest for new contributors.
next prev parent reply other threads:[~2021-04-26 18:47 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-26 16:44 Konstantin Ryabitsev 2021-04-26 17:37 ` Eric Wong 2021-04-26 18:20 ` Konstantin Ryabitsev 2021-04-26 18:47 ` Eric Wong [this message] 2021-04-26 19:46 ` Konstantin Ryabitsev 2021-04-26 20:34 ` 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=20210426184717.GA29112@dcvr \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: lei-managed pseudo mailing lists' \ /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
user/dev discussion of public-inbox itself This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 meta meta/ https://public-inbox.org/meta \ firstname.lastname@example.org public-inbox-index meta Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.mail.public-inbox.meta nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.mail.public-inbox.meta nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.io/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git