From: "James Ramsay" <firstname.lastname@example.org>
To: "Emily Shaffer" <email@example.com>
Cc: "Jeff King" <firstname.lastname@example.org>, email@example.com
Subject: Re: RFC - Git Developer Blog
Date: Fri, 13 Sep 2019 09:29:33 -0400 [thread overview]
Message-ID: <885DEEA4-154B-4990-945D-19DABC87C627@jramsay.com.au> (raw)
On 6 Aug 2019, at 16:49, Emily Shaffer wrote:
> On Tue, Aug 06, 2019 at 09:20:52AM -0400, Jeff King wrote:
>> On Mon, Aug 05, 2019 at 06:49:35PM -0700, Emily Shaffer wrote:
>>> Are folks interested in writing and reviewing this kind of content?
>>> ideas for where we may be able to host (maybe git-scm)?
>> I think it would make sense to have blog.git-scm.com (and .org) with
>> this content. I'd be happy to deal with the technical side of setting
>> the name up. I think it should live in a different repository than
>> main site, though (which is an overly-messy Rails app).
> I'd certainly be happy with that setup if others agree, although the
> incorporation with Git Rev News sounds interesting too (I'll reply to
> that post also).
As volunteered yesterday at the Virtual Contributors' Summit, I have
created a project on GitLab to start working on this
https://gitlab.com/git-scm/blog. I hope to have a basic text centric
implementation for feedback in the next few weeks. For now, all I've
created is merge request with an empty Hugo site and automated deploys.
Those who would like to be added as maintainers, you should be able to
Request Access using the link near the project name.
Peff, you mentioned Jason might have some designs or ideas with regards
visuals. I'm happy to be put in touch directly or collaborate here.
next prev parent reply other threads:[~2019-09-13 13:29 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
2019-08-06 13:20 ` Jeff King
2019-08-06 20:49 ` Emily Shaffer
2019-09-13 13:29 ` James Ramsay [this message]
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
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:
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 \
* 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
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).