From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] www.bufferbloat.net server has finally died
Date: Wed, 11 May 2016 08:44:26 -0700 [thread overview]
Message-ID: <CAA93jw49sZA6Nnr=ntLxsGpHgqtg5E4tNW=ET-sMrRq+xcfkfA@mail.gmail.com> (raw)
... as I was unable to summon the chops to get a new redmine instance
going on a more modern OS in the cloud, I am not sure where to go from
here.
I have several fairly recent backups of it and can go to the co-lo
facility thursday to extract the hard disk to pull off the most
current data, but that leaves what to do with it as a problem.
In my case I'd been experimenting with switching to github for issue
tracking, as well as using the static site generator "hugo" for the
cerowrt blog.
I felt that bufferbloat.net content needed a ton of curation on the
existing stuff (that was far, far, far too tedious to do with a
website interface), and was more or less planning to convert all the
content from textile/redmine to markdown/hugo at some point.
I do not have the time presently to fix this (And that conversion
either to a new redmine instance or hugo is a big job), as I will be
out of the country for much of the coming weeks.
What I can do is put in a redirect to archive.org like:
https://web.archive.org/web/20160429085659/https://www.bufferbloat.net/
If someone would like to volunteer to "own" www.bufferbloat.net and
fix it, that would be great.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-05-11 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 15:44 Dave Taht [this message]
2016-05-11 17:01 ` Outback Dingo
2016-05-11 17:15 ` Dave Taht
[not found] <mailman.5.1463068801.8093.bloat@lists.bufferbloat.net>
2016-05-12 16:05 ` Francisco Arevalo
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw49sZA6Nnr=ntLxsGpHgqtg5E4tNW=ET-sMrRq+xcfkfA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@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