git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: "Stefan Beller" <sbeller@google.com>,
	"Derrick Stolee" <stolee@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git <git@vger.kernel.org>, "Duy Nguyen" <pclouds@gmail.com>,
	"Derrick Stolee" <dstolee@microsoft.com>
Subject: Re: Measuring Community Involvement (was Re: Contributor Summit planning)
Date: Wed, 15 Aug 2018 07:12:01 +0000	[thread overview]
Message-ID: <20180815071201.GA3169@dcvr> (raw)
In-Reply-To: <20180814200611.GG28452@sigill.intra.peff.net>

Jeff King <peff@peff.net> wrote:
> On Tue, Aug 14, 2018 at 12:47:59PM -0700, Stefan Beller wrote:
> > With the advent of public inbox, this is easy to obtain?
> 
> For our project, yes. But I was thinking of a tool that could be used
> for other projects, too.

Nothing prevents public-inbox from being adopted by other projects :)
Fwiw, Linux Foundation has LKML at https://lore.kernel.org/lkml

  reply	other threads:[~2018-08-15  7:12 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 16:31 Contributor Summit planning Jeff King
2018-08-13 16:58 ` Derrick Stolee
2018-08-13 17:15   ` Jeff King
2018-08-27 13:22     ` Johannes Schindelin
2018-08-27 13:30       ` Derrick Stolee
2018-08-28 12:22         ` Johannes Schindelin
2018-08-28 19:06         ` Jonathan Nieder
2018-08-28 19:11           ` Jonathan Nieder
2018-08-29 14:38           ` Johannes Schindelin
2018-08-29  4:52       ` Jeff King
2018-08-29 14:44         ` Johannes Schindelin
2018-08-13 17:46 ` Stefan Beller
2018-08-14  4:31   ` Christian Couder
2018-08-14 14:35     ` Jeff King
2018-08-13 18:49 ` Ævar Arnfjörð Bjarmason
2018-08-13 19:44   ` Jeff King
2018-08-13 20:36   ` Junio C Hamano
2018-08-13 20:41     ` Stefan Beller
2018-08-13 21:06       ` Jeff King
2018-08-13 21:19         ` Stefan Beller
2018-08-13 21:54           ` Jeff King
2018-08-14 17:43             ` Measuring Community Involvement (was Re: Contributor Summit planning) Derrick Stolee
2018-08-14 19:36               ` Jeff King
2018-08-14 19:47                 ` Stefan Beller
2018-08-14 20:06                   ` Jeff King
2018-08-15  7:12                     ` Eric Wong [this message]
2018-08-14 20:42                 ` Junio C Hamano
2018-08-27 15:54                   ` Johannes Schindelin
2018-08-15 16:28               ` Duy Nguyen
2018-08-27 15:55                 ` Johannes Schindelin
2018-08-14 14:30         ` Contributor Summit planning Duy Nguyen
2018-08-14 14:47           ` Jeff King
2018-08-14 16:57             ` Stefan Beller
2018-08-14 20:59             ` Junio C Hamano
2018-08-17 15:18       ` Duy Nguyen
2018-08-27 22:49   ` Johannes Schindelin
2018-08-29  5:02     ` Jeff King
2018-08-14  6:52 ` Elijah Newren
2018-08-14 13:25   ` Randall S. Becker
2018-08-14 14:06     ` Ævar Arnfjörð Bjarmason
2018-08-14 14:30       ` Jeff King
2018-08-14 14:28     ` Jeff King
2018-08-27 13:34 ` Johannes Schindelin
2018-08-29  4:55   ` Jeff King
2018-08-29 14:46     ` Johannes Schindelin
2018-08-30  3:20       ` Jeff King
2018-08-30 11:36         ` Johannes Schindelin

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=20180815071201.GA3169@dcvr \
    --to=e@80x24.org \
    --cc=avarab@gmail.com \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=sbeller@google.com \
    --cc=stolee@gmail.com \
    /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 NNTP newsgroup(s).