From: Junio C Hamano <gitster@pobox•com>
To: Thomas Ferris Nicolaisen <tfnico@gmail•com>
Cc: Christian Couder <christian.couder@gmail•com>,
git <git@vger•kernel.org>, David Kastrup <dak@gnu•org>,
Eric Sunshine <sunshine@sunshineco•com>,
Matthieu Moy <Matthieu.Moy@imag•fr>,
Nguyen Thai Ngoc Duy <pclouds@gmail•com>,
Paul Tan <pyokagan@gmail•com>,
Johannes Schindelin <Johannes.Schindelin@gmx•de>,
Dongcan Jiang <dongcan.jiang@gmail•com>,
Jeff King <peff@peff•net>, Doug Kelly <dougk.ff7@gmail•com>,
Bharat Suvarna <bharat.bs84@icloud•com>, Kevin D <me@ikke•info>,
"Randall S. Becker" <rsbecker@nexbridge•com>,
Stephen Robin <stephen.robin@gmail•com>
Subject: Re: Draft of Git Rev News edition 1
Date: Sun, 22 Mar 2015 21:49:41 -0700 [thread overview]
Message-ID: <xmqq619sb9ne.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAEcj5uV0adYn_F6D1mmueR5F8N459dgP1TTWmPiEH9NFeDqFeQ@mail.gmail.com> (Thomas Ferris Nicolaisen's message of "Sun, 22 Mar 2015 21:50:53 +0100")
Thomas Ferris Nicolaisen <tfnico@gmail•com> writes:
> Good point. There hasn't been a decision on frequency. Weekly is a
> good rhythm for publications seeking readership, but that's a lot of
> work. My vote is we should first aim for a monthly consistent release.
> I'll try working this into the draft, and Christian may change as he
> sees fit.
I agree weekly would be too much for any hobbist, given how
high-volume our list has, but I probably shouldn't have said
"periodical". Surely, aiming for consistent update is a very good
thing to gain reader trust if anything else, but it is OK if it were
"we will see a new release when enough interesting things happen",
too.
The primary reason I suggested to explicitly state the beginning of
coverage is to set and manage the expectation of the readers. I
think the current draft roughly covers 1/4 - 1/3 of discussions that
happened in the month of March 2015 and nothing earlier than that,
so "This issue covers what happened in March" or something would be
appropriate. I'll throw a pull-request.
>> - As an inaugural edition, we may want to have a word on
>> how it came in existence by covering the discussion that
>> led to its birth. Perhaps the discussion that led to the
>> publication should be made into as an item on its own,
>> next to "make git-pull a builtin", "Forbid log --graph..." etc.
>> Because it is neither a review nor a support discussion,
>> "Reviews & Support" heading may want to become
>> "Discussions". I think that is a better title for the section
>> anyway, if its purpose is "what happened on the list that
>> are not visible from "git log", as I expect future editions
>> to cover design discussions that advanced the shared
>> understanding of a problem but not quite solidified to
>> become a patch series.
>>
>
> I hope it's OK that I leave this bit to Christian.
I took a stab at this myself, and threw another pull-request.
Thanks.
next prev parent reply other threads:[~2015-03-23 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 11:03 Draft of Git Rev News edition 1 Christian Couder
2015-03-22 11:21 ` David Kastrup
2015-03-22 12:19 ` Christian Couder
2015-03-22 20:52 ` Thomas Ferris Nicolaisen
2015-03-22 21:24 ` David Kastrup
2015-03-22 18:47 ` Junio C Hamano
2015-03-22 20:50 ` Thomas Ferris Nicolaisen
2015-03-23 4:49 ` Junio C Hamano [this message]
2015-03-23 5:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq619sb9ne.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=Matthieu.Moy@imag$(echo .)fr \
--cc=bharat.bs84@icloud$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=dak@gnu$(echo .)org \
--cc=dongcan.jiang@gmail$(echo .)com \
--cc=dougk.ff7@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ikke$(echo .)info \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=pyokagan@gmail$(echo .)com \
--cc=rsbecker@nexbridge$(echo .)com \
--cc=stephen.robin@gmail$(echo .)com \
--cc=sunshine@sunshineco$(echo .)com \
--cc=tfnico@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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