On 08/04/2014 08:45 AM, Charles Haynes wrote:
Totally agree with Travis. Also - who is the intended audience for
this? People who want to know how the different layers of the OSI
stack work in practice?
-- Charles
On Mon, Aug 4, 2014 at 10:27 PM, Travis Biehn <[email protected]
<mailto:[email protected]>> wrote:
Think it might be useful to, like, pin this to an OSI layer?
You're going to be including all sorts of ludicrous stuff, like
gcc & svn/git.
Critical internet software, that's the stuff that makes happy
machines speak transport layer to each other.
Upon further reflection, what I'm really interested in is a way to
filter a flat list of everything-but-the-kitchen sink so that the
following criteria can float the weaker titles up to the top:
* number of internet-facing machines running the software
* complexity of the underlying code
* average time for relevant dev community to fix critical bugs
* average time for bug-fixes to propagate (if at all-- I'm looking at
you, home routers!)
* budget of the relevant dev community
-Jonathan
--
Liberationtech is public & archives are searchable on Google. Violations of
list guidelines will get you moderated:
https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe,
change to digest, or change password by emailing moderator at
[email protected].
