unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
* workflow problems and possible public-inbox solutions
@ 2019-10-18  3:25 Eric Wong
  2019-10-18 19:01 ` Eric Wong
  2019-10-18 19:03 ` Konstantin Ryabitsev
  0 siblings, 2 replies; 4+ messages in thread
From: Eric Wong @ 2019-10-18  3:25 UTC (permalink / raw)
  To: workflows; +Cc: meta

It seems like there's a bunch of problems the workflows@vger
list is trying to solve.  Some can be solved independently
of others.

Here's a summary of them and where items in
https://public-inbox.org/TODO list can be possible solution
(I'm not claiming it can solve everything :P)


1. vger deliverability problems to major mail providers

(NNTP|public-inbox) => POP3 bridge, since all major providers
support importing mail from POP3.

 https://public-inbox.org/meta/20160411034104.GA7817@dcvr.yhbt.net/

Locally-run NNTP -> mail fetchers can also work, but requires
more effort to setup.


2. attestation of messages

Self-publishing "Sent Mail" folders via NNTP or git,
(similar to Certificate Transparency):
https://lore.kernel.org/workflows/20191010192852.wl622ijvyy6i6tiu@chatter.i7.local/

This would provide redundancy, too; and it's probably more
usable and learnable than GPG :P



3. patch series evolution tracking

Further optimize searching and linkification for patches and
blob OIDs.

public-inbox can already search based on pre/post-image OIDs
(dfpre:/dfpost:) and use that recreate blobs from a series of
patches.

Future: Arbitrary diffs can be generated off recreated blobs.
--interdiff output can be parsed and searched on.

Some proposed solutions to make --range-diff output more
search-friendly, too:

  https://public-inbox.org/git/b9fb52b8-8168-6bf0-9a72-1e6c44a281a5@oracle.com/
  ("email as a bona fide git transport")

  https://public-inbox.org/git/20191017121045.GA15364@dcvr/
  ("range-diff: show old/new blob OIDs in comments")



4. secret exchanges for embargoed issues

No idea, really; not my department :P

It would be good if all messages in the exchange can be
published and mirrored once the embargo is lifted, though.



5. bug tracking

public-inbox already learned to parse and apply patches; so
parsing a debbugs-like language could be done, too.  Maybe
public-inbox can be optimized to improve searching on
"Fixes: $COMMIT_OID" in trailers until we decide on other
parts of the grammar.


Maybe some other stuff, too (feel free to add)
Thanks for reading.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-10-19  0:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-10-18  3:25 workflow problems and possible public-inbox solutions Eric Wong
2019-10-18 19:01 ` Eric Wong
2019-10-18 19:03 ` Konstantin Ryabitsev
2019-10-19  0:29   ` Eric Wong

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).