From: David Collier-Brown <davec-b@rogers.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: Four short links: 11 November 2016
Date: Fri, 11 Nov 2016 11:02:26 -0500 [thread overview]
Message-ID: <391ecb32-45bd-29ab-abeb-f0156692fb45@rogers.com> (raw)
In-Reply-To: <tag:www.oreilly.com, 2016-11-11:/ideas/four-short-links-11-november-2016@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Nat Torkington just pointed to a Ford Foundation study on underfunded
internet infrastructure, (3) below
-------- Forwarded Message --------
Subject: Four short links: 11 November 2016
Date: Fri, 11 Nov 2016 11:50:00 GMT
From: Nat Torkington <>
Four short links: 11 November 2016
/Arrival Science, Open Source Hospital, Unseen Labour, and FOSS Heartbeat/
1. The Science of Arrival
<https://backchannel.com/i-had-one-night-to-invent-interstellar-travel-b2466882ef5c#.kdzakerv2>
(Stephen Wolfram) -- wonderful to see a nerd nerding out about the
science in a movie. (He advised on it, and is chuffed that scenes
have Wolfram Language on the screens)
2. Bahmni <http://www.bahmni.org/> -- /an easy-to-use EMR & hospital
system. It combines and enhances existing open source products into
a single solution./
3. Roads and Bridges: The Unseen Labor Behind Our Digital
Infrastructure
<https://fordfoundcontent.blob.core.windows.net/media/2976/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure.pdf>
(PDF) -- /The pervasive belief, even among stakeholders such as
software companies, that open source is well-funded makes it harder
to generate support. Some infrastructure projects operate
sustainably, either because they have a working business model or
sponsorship, or because their required upkeep is limited. An
unfamiliar audience will also associate open source with enterprise
companies like Red Hat or Docker and assume the problem has been
solved. However, these situations are the outliers, not the rule./
4. FOSS Heartbeat <https://github.com/sarahsharp/foss-heartbeat> --
/uses contributor participation data (currently from GitHub) to
categorize users into these seven roles/, which are: /Issue
reporter, Issue responder, Code contributor, Documentation
contributor, Reviewer, Maintainer, Connector./ Sarah Sharp's latest
project.
Continue reading Four short links: 11 November 2016.
<https://www.oreilly.com/ideas/four-short-links-11-november-2016>
[-- Attachment #2: Type: text/html, Size: 3731 bytes --]
next parent reply other threads:[~2016-11-11 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tag:www.oreilly.com, 2016-11-11:/ideas/four-short-links-11-november-2016@localhost.localdomain>
2016-11-11 16:02 ` David Collier-Brown [this message]
2016-11-11 16:17 ` 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/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=391ecb32-45bd-29ab-abeb-f0156692fb45@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.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