From: James Bottomley <James.Bottomley@HansenPartnership.com> To: Konstantin Ryabitsev <email@example.com>, Joe Perches <firstname.lastname@example.org> Cc: Vlastimil Babka <email@example.com>, "firstname.lastname@example.org" <email@example.com>, LKML <firstname.lastname@example.org> Subject: Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch Date: Thu, 03 Dec 2020 13:13:47 -0800 [thread overview] Message-ID: <4b973b02352860978331eef110bae69e0d576adf.camel@HansenPartnership.com> (raw) In-Reply-To: <email@example.com> On Thu, 2020-12-03 at 14:17 -0500, Konstantin Ryabitsev wrote: > On Thu, Dec 03, 2020 at 08:55:54AM -0800, Joe Perches wrote: > > Perhaps automate a mechanism to capture that information as > > git notes for the patches when applied. > > Git notes have a limited usefulness for this -- they are indeed part > of the repository, but they aren't replicated unless someone does a > --mirror clone (or specifically fetches refs/notes/*). If the goal is > to improve visibility for contributors, then putting this info into a > git note will hardly make more difference than providing a Link: that > someone has to follow to a list archival service. > > I can offer the following proposal: > > - kernel.org already monitors all mailing lists that are archived on > lore.kernel.org for the purposes of pull request tracking > (pr-tracker-bot). > - in the near future, we will add a separate process that will > auto-explode all pull requests into individual patches and add them > to a separate public-inbox archive (think of it as another > transparency log, since pull requests are transient and opaque). > > We can additionally: > > - identify all Link: and Message-Id: entries in commit messages, > retrieve the threads they refer to, and archive them as part of > the same (or adjacent) transparency log. > > This offers an improvement over the status quo, because if > lore.kernel.org becomes unavailable, someone would have to have > access to all backend archive repositories it is currently tracking > in order to be able to reconstitute relevant conversations -- whereas > with this change, it should be sufficient to just have the copy of > the transparency log to have a fully self-contained high-relevancy > archive of both individual commits and conversations that happened > around them. I don't think this is strictly necessary because there's more than lore that archive's our lists, but the people at the internet history project would remind me not to look a gift horse in the mouth, so I think this would certainly be a useful addition. The thing which Link: doesn't necessarily track is iterations, so if you replied to v2 and your feedback got incorporated, there's a v3 iteration which has a different msgid. Is there a way of getting this full history, not just the current thread? > I'm just not sure if this will help with the subject of the > conversation, or if it does not serve the goal of recognizing > developer contributions by making them more visible. I added Jon to the cc since a lot of managers (community or otherwise) do use the lwn.net stats as a performance guide. The real question is could we get something measurable out of the data? say number of replies to an accepted patch counting in the reviewer stats or something? James _______________________________________________ Ksummit-discuss mailing list Ksummitfirstname.lastname@example.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-12-03 21:13 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-02 23:43 Vlastimil Babka 2020-12-03 4:02 ` Dan Williams 2020-12-03 9:34 ` Leon Romanovsky 2020-12-03 9:36 ` Geert Uytterhoeven 2020-12-03 10:40 ` Leon Romanovsky 2020-12-03 18:30 ` Greg KH 2020-12-03 19:04 ` Leon Romanovsky 2020-12-09 0:34 ` Kees Cook 2020-12-09 5:01 ` Joe Perches 2020-12-09 7:58 ` Dan Carpenter 2020-12-09 8:45 ` Vlastimil Babka 2020-12-09 9:18 ` Geert Uytterhoeven 2020-12-09 8:54 ` Joe Perches 2020-12-09 10:30 ` Dan Carpenter 2020-12-09 17:45 ` Dan Williams 2020-12-03 10:33 ` Dan Carpenter 2020-12-03 13:41 ` Julia Lawall 2020-12-03 13:58 ` James Bottomley 2020-12-03 16:55 ` Joe Perches 2020-12-03 19:17 ` Konstantin Ryabitsev 2020-12-03 19:24 ` Joe Perches 2020-12-03 21:13 ` James Bottomley [this message] 2020-12-03 18:52 ` Matthew Wilcox 2020-12-03 20:04 ` James Bottomley 2020-12-04 4:54 ` Theodore Y. Ts'o
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4b973b02352860978331eef110bae69e0d576adf.camel@HansenPartnership.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch' \ /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
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 NNTP newsgroup(s).