git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Lang <david@lang.hm>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	David Kastrup <dak@gnu.org>, git <git@vger.kernel.org>,
	Jeff King <peff@peff.net>, Scott Chacon <schacon@gmail.com>
Subject: Re: Promoting Git developers
Date: Mon, 16 Mar 2015 22:56:18 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1503162254080.22474@nftneq.ynat.uz> (raw)
In-Reply-To: <xmqqh9tkp54u.fsf@gitster.dls.corp.google.com>

On Mon, 16 Mar 2015, Junio C Hamano wrote:

> David Lang <david@lang.hm> writes:
>
>> On Sun, 15 Mar 2015, Junio C Hamano wrote:
>>
>>> Christian Couder <christian.couder@gmail.com> 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'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.
>
> I hope you are right, but my observation of our coverage by lwn.net
> is somewhat pessimistic.  In our early days, our progress often used
> to appear on the "Kernel Development" page, which I presume is the
> most important page of the weekly for the kernel developers, but in
> several months, the mention of us has moved two pages back to
> "Development" and listed together with folks like OCaml Weekly,
> PostgreSQL Weekly, etc.  I would not count that as "pretty good
> visibility" particularly.
>
> I am taking it as a positive change, though.  Once we got stable
> enough not to be a roadblock for the kernel folks and proven
> ourselves not to regress, our progress probably ceased to be
> newsworthy to them ;-)

It ceased to be about kernel development, and fell into the normal development 
bucket :-)

Routine release notes (like your notes from the maintainer) do end up just 
getting links to them as you have seen. But if someone is summarizing the 
discussions on the mailing list, those will be a bit more interesting, and if 
there is a particularly hot topic, the summary of that discussion can be a full 
fledged article on it's own.

David Lang

  reply	other threads:[~2015-03-17  5:56 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber
2015-03-09 14:31   ` Promoting Git developers David Kastrup
2015-03-09 18:32     ` Philip Oakley
2015-03-10  7:45   ` Junio C Hamano
2015-03-10 11:51   ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23     ` Promoting Git developers Junio C Hamano
2015-03-11  1:04       ` Jason St. John
2015-03-11  2:13         ` Duy Nguyen
2015-03-11  4:16           ` Junio C Hamano
2015-03-12  2:15             ` Duy Nguyen
2015-03-12  4:53               ` Junio C Hamano
2015-03-12  7:45                 ` Fredrik Gustafsson
2015-03-12 18:43                   ` Junio C Hamano
2015-03-11  2:36         ` Junio C Hamano
2015-03-11  7:31           ` Jeff King
2015-03-11  7:38             ` Junio C Hamano
2015-03-11  7:54               ` Jeff King
2015-03-11 21:28                 ` Junio C Hamano
2015-03-11 23:17                   ` Andrew Ardill
2015-03-12 22:31                   ` Jeff King
2015-03-12 22:36                     ` Junio C Hamano
2015-03-12 22:43                       ` Jeff King
2015-03-12  5:05             ` Junio C Hamano
2015-03-12 22:38               ` Jeff King
2015-03-12 22:58                 ` Junio C Hamano
2015-03-15  9:12                   ` Christian Couder
2015-03-11 13:53       ` Christian Couder
2015-03-11 20:42         ` Junio C Hamano
2015-03-15  8:46           ` Christian Couder
2015-03-15 22:18             ` Junio C Hamano
2015-03-15 22:43               ` Randall S. Becker
2015-03-16  9:10                 ` Christian Couder
2015-03-16  9:20                   ` David Kastrup
2015-03-16 17:06                     ` Stefan Beller
2015-03-17 20:08                       ` Christian Couder
2015-03-17 20:16                         ` Junio C Hamano
2015-03-16 23:39               ` David Lang
2015-03-17  5:25                 ` Junio C Hamano
2015-03-17  5:56                   ` David Lang [this message]
2015-03-17 20:15               ` Christian Couder
2015-03-17  9:43             ` Thomas Ferris Nicolaisen
2015-03-17 19:51               ` Christian Couder

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1503162254080.22474@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=christian.couder@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=schacon@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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