From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>, Derrick Stolee <stolee@gmail.com>,
Andrew Ardill <andrew.ardill@gmail.com>,
Emily Shaffer <emilyshaffer@google.com>,
git <git@vger.kernel.org>
Subject: Re: RFC - Git Developer Blog
Date: Wed, 7 Aug 2019 13:44:57 -0400 [thread overview]
Message-ID: <20190807174457.GA62589@syl.local> (raw)
In-Reply-To: <xmqqef1wj3r4.fsf@gitster-ct.c.googlers.com>
On Wed, Aug 07, 2019 at 10:15:43AM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> >> It would also be helpful to have a post for every major release
> >> highlighting new features and giving users examples of how to use them.
> >> Taylor has been writing these on the GitHub blog [1], but maybe he
> >> would be interested in writing them for this new venue?
> >>
> >> [1] https://github.blog/2019-06-07-highlights-from-git-2-22/
> >
> > Yes, I generally try and publish a blog post once-per-release, and
> > generally with the following two goals in mind:
> >
> > - talk about and publicize some of the new features in the latest
> > release (or releases, if I've missed a blog post or two)
> >
> > - share some interesting tidbits about existing features.
> >
> > I think it would be good to have these blog posts in both places, should
> > this proposal materialize. I would have to ask about whether or not
> > GitHub would be comfortable about cross-posting to a new venue, and I'd
> > be happy to raise the question when it comes up.
>
> Yeah, I find these blog postings at GitHub quite helpful. Thanks
> for writing them.
Thanks for maintaining the release notes. I often start there to figure
out what to write about, and having them so well organized makes my job
a lot easier.
> I wonder if a semi-automated republication (ala "Planet"), instead
> of cross-posting, is an option that is easier to manage, though.
Probably. I don't know how Planet works, but if it can accept an RSS
feed (and doesn't require too much on GitHub's end), it's probably
sensible.
Thanks,
Taylor
next prev parent reply other threads:[~2019-08-07 17:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 1:49 RFC - Git Developer Blog Emily Shaffer
2019-08-06 3:33 ` Junio C Hamano
2019-08-06 4:59 ` Christian Couder
2019-08-06 13:27 ` Jeff King
2019-08-06 21:07 ` Emily Shaffer
2019-08-07 17:00 ` Taylor Blau
2019-08-06 4:52 ` Andrew Ardill
2019-08-06 12:19 ` Derrick Stolee
2019-08-06 21:00 ` Emily Shaffer
2019-08-07 17:12 ` Taylor Blau
2019-08-07 17:07 ` Taylor Blau
2019-08-07 17:15 ` Junio C Hamano
2019-08-07 17:44 ` Taylor Blau [this message]
2019-08-06 13:20 ` Jeff King
2019-08-06 20:49 ` Emily Shaffer
2019-09-13 13:29 ` James Ramsay
2019-09-13 14:05 ` pedro rijo
2019-09-17 19:22 ` James Ramsay
2019-09-17 19:32 ` Emily Shaffer
2019-09-17 19:39 ` pedro rijo
2019-10-23 22:36 ` James Ramsay
2019-10-23 23:48 ` Jeff King
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=20190807174457.GA62589@syl.local \
--to=me@ttaylorr.com \
--cc=andrew.ardill@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).