Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] is there an html expert in the house?
Date: Tue, 22 Mar 2016 12:29:15 -0700	[thread overview]
Message-ID: <CAA93jw5KGBsYZa31RzrJqV8PBpEYPXJCOgmZ5RJO0F_f8MW3LQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4v1+1+uRiW8KPp=0z93_ozQ_X+pTNhvG1LfWNJ57zbww@mail.gmail.com>

well, anyway, I put out what may become "blog.cerowrt.org" into
github. DNS for it should propigate over the next hour or so.

My concept here is that the world has moved to github, and static site
generators, like hugo, are all the rage. I have thus far failed to
migrate the existing redmine installation elsewhere, and I have a very
large queue of things half written that I'd like to stash somewhere
they can be shared....

I tend to write long emails chock full of links to graphics, and I
frequently feel the need to revise or expand upon what I said.

I also used to keep my lab notebook in git, with test results and test
scripts, and if I can do all these things and "get it out there" -
with minimal effort on my part, it seems like a win. If folk want to
author blog entries or otherwise contribute they can fork and develop
locally on their own hardware using hugo -D server... and then issue
pull requests. This also gives us SSO (single sign on) which reduces
the spam to zero (vs the wiki).

That said... boy do I hate html and css, almost as much as I hate
textile, learning hugo has not been painful but it's still complex,
and I still have to migrate the existing bufferbloat.net sites to new
servers somehow, months ago.

  reply	other threads:[~2016-03-22 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 17:13 Dave Taht
2016-03-22 19:29 ` Dave Taht [this message]
2016-03-23 13:41 ` Toke Høiland-Jørgensen
2016-03-23 13:56   ` Dave Taht

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: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw5KGBsYZa31RzrJqV8PBpEYPXJCOgmZ5RJO0F_f8MW3LQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox