From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lang Subject: Re: Promoting Git developers Date: Mon, 16 Mar 2015 16:39:12 -0700 (PDT) Message-ID: References: <54FDA6B5.8050505@drmicha.warpmail.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Christian Couder , Michael J Gruber , David Kastrup , git , Jeff King , Scott Chacon To: Junio C Hamano X-From: git-owner@vger.kernel.org Tue Mar 17 00:39:39 2015 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YXebi-000325-5o for gcvg-git-2@plane.gmane.org; Tue, 17 Mar 2015 00:39:38 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754575AbbCPXjd (ORCPT ); Mon, 16 Mar 2015 19:39:33 -0400 Received: from mail.lang.hm ([64.81.33.126]:51037 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbbCPXjc (ORCPT ); Mon, 16 Mar 2015 19:39:32 -0400 Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id t2GNdDxE023740; Mon, 16 Mar 2015 15:39:13 -0800 X-X-Sender: dlang@asgard.lang.hm In-Reply-To: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Sun, 15 Mar 2015, Junio C Hamano wrote: > Christian Couder writes: > >> I wrote something about a potential Git Rev News news letter: > > I read it. Sounds promising. > > Just one suggestion on the name and half a comment. > > How would "Git Review" (or "Git Monthly Review", or replace your > favourite "how-often-per-period-ly" in its name) sound? I meant it > to sound similar to academic journals that summarize and review > contemporary works in the field and keeps your original "pun" about > our culture around "patch reviews". > > I obviously do not know how the actual contents would look like at > this point, but depending on the quality of the publication I might > be able to steal some descriptions when keeping the notes on topics > in flight that appear in my "What's cooking" report. And it can go > the other way around, too. The publication may want to peek my > "What's cooking" report for hints on how to characterize each topic > and assess its impact to the evolution of Git. I'll bet that LWN would publish, or at least link to, such articles on a regular basis, and if you end up doing an in-depth writeup on a particularly discussed topic, they would probably give it pretty good visibility. David Lang