Sagudo add cc0license

README.md

@@ -1,11 +1,10 @@
-Open Source Efforts at The Obvious Corporation
+Open Source at Medium
 ==============================================
 
 This repository serves as the umbrella project to represent the
-various open source efforts at The Obvious Corporation
-<http://obvious.com>. Come here to get an overview of the various
-projects, to learn how to contribute to them, and to sign up as a
-contributor.
+various open source efforts at [A&nbsp;Medium&nbsp;Corporation](https://medium.com).
+Come here to get an overview of the various projects, to learn how to
+contribute to them, and to sign up as a contributor.
 
 Table Of Contents
 -----------------
@@ -17,11 +16,15 @@ On this page:
 
 Other pages:
 
-* [Sign the OCLA](https://github.com/Obvious/open-source/blob/master/sign-ocla.md)
-* [OCLA Rationale](https://github.com/Obvious/open-source/blob/master/ocla-rationale.md)
-* [Contributors](https://github.com/Obvious/open-source/blob/master/contributors)
-* [Obvious Contributor License Agreement 1.0](https://github.com/Obvious/open-source/blob/master/ocla-1.0.md)
-* [Apache License 2.0](https://github.com/Obvious/open-source/blob/master/apache-license-2.0.md)
+* [Sign the CLA](https://github.com/Medium/opensource/blob/master/sign-cla.md)
+* [CLA Rationale](https://github.com/Medium/opensource/blob/master/cla-rationale.md)
+* [Contributors](https://github.com/Medium/opensource/blob/master/contributors)
+* [Contributor License Agreement 2.0](https://github.com/Medium/opensource/blob/master/cla-2.0.md)
+* [MIT License](https://github.com/Medium/opensource/blob/master/mit-license.md)
+
+Style guides:
+
+* [JavaScript](https://github.com/Medium/opensource/blob/master/styleguides/JavaScript.md)
 
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
@@ -30,53 +33,56 @@ Note to External Contributors
 
 Hello, External Person!
 
-We at Obvious are eager to work with you. For small changes &mdash;
-little bugfixes, correcting typos, and the like &mdash; please just
-submit pull requests to any of our projects. For larger changes,
-though, we have to ask you to jump through a little hoop.
+We at Medium are eager to work with you. For small changes&#8201;&mdash;&#8201;little
+bugfixes, correcting typos, and the like&#8201;&mdash;&#8201;please just submit pull
+requests to any of our projects. For larger changes, though, we have to ask you to jump
+through a little hoop.
 
-In particular, in order for us to accept any major patches from you,
-you will have to electronically sign a statement that indicates two
-things:
+In particular, in order for us to accept any major patches from you, you will have to
+electronically sign a statement that indicates two things:
 
 * You are willingly licensing your contributions under the terms of
-  the open source license of the project that you're contributing to.
+  the open source license of the project that you’re contributing to.
 
 * You are legally able to license your contributions as stated.
 
-The reason we do this is to ensure, to the extent possible, that we
-don't "taint" the projects we manage with contributions that turn out
-to be improper. This protects everyone who wants to use the projects,
-including *you*! If you want a longer explanation, then you can check
-out the [OCLA Rationale
-page](https://github.com/Obvious/open-source/blob/master/ocla-rationale.md).
+The reason we do this is to ensure, to the extent possible, that we don’t “taint”
+the projects we manage with contributions that turn out to be improper. This protects
+everyone who wants to use the projects, including *you*! If you want a longer explanation,
+then you can check out the [CLA Rationale page](https://github.com/Medium/opensource/blob/master/cla-rationale.md).
 
-Once you sign the Obvious Contributor License Agreement (the "OCLA"),
-we will then be able to merge your contributions with a clear
-conscience and with only the friction that results from the usual
-technical back-and-forth of a vibrant open source project.
+Once you sign the Contributor License Agreement (the “CLA”), we will then be able to
+merge your contributions with a clear conscience and with only the friction that results
+from the usual technical back-and-forth of a vibrant open source project.
 
 To get started with this process, visit the
-[Sign the OCLA](https://github.com/Obvious/open-source/blob/master/sign-ocla.md)
+[Sign the CLA](https://github.com/Medium/opensource/blob/master/sign-cla.md)
 page.
 
-For reference, the standard open source license used by The Obvious
-Corporation is the
-[Apache License 2.0](https://github.com/Obvious/open-source/blob/master/apache-license-2.0.md)
-with a small clarifying preamble.
+For reference, projects manageed by A Medium
+Corporation include some using
+[MIT License](https://github.com/Medium/opensource/blob/master/mit-license.md)
+with a small clarifying preamble and some using
+the [Apache 2.0 License](https://github.com/Medium/opensource/blob/master/apache-license-2.0.md).
+
+In addition to our CLA, we have a policy where we avoid owning code that we don’t intend
+to maintain through use. If your patch is not in-line with our intended use case
+at Medium we will not merge it into any of our trees. But don't be discouraged! If
+that’s the case, we encourage you to run your own fork. Email us with a link to it
+and we will consider linking to it from the main repo.
 
 If you have any questions about any of this, please raise them by
-filing a bug on this project, since there's a good chance that if you
+filing a bug on this project, since there’s a good chance that if you
 have a question then someone else has the same question too. If it is
-really and truly a private matter, then you can mail Obvious's
+really and truly a private matter, then you can mail Medium’s
 official Open Sourceror privately, at
-[open-source@obvious.com](mailto:open-source@obvious.com).
+[open-source@medium.com](mailto:open-source@medium.com).
 
 Thanks, and happy hacking!
 
 Cheers,
 
-Your friends at The Obvious Corporation
+Your friends at A Medium Corporation
 
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 
@@ -88,45 +94,33 @@ List of Projects
 These are [Node](http://nodejs.org/) modules that can be used pretty directly as
 libraries in applications.
 
-* [Async Builder](https://github.com/Obvious/asyncBuilder) &mdash;
-  Asynchronous dependency loading "the cool way".
-* [Bidar](https://github.com/Obvious/bidar) &mdash; Binary serialization
-  and object iteration.
-* [Composers](https://github.com/Obvious/composers) &mdash; Asynchronous
-  programming framework.
-* [Daemon Sauce](https://github.com/Obvious/daemonsauce) &mdash; Making
+* [Daemon Sauce](https://github.com/Medium/daemonsauce)&#8201;&mdash;&#8201;Making
   it easy to be a proper *nix daemon.
-* [Falkor](https://github.com/Obvious/falkor) &mdash; HTTP Level Functional
+* [Dynamite](https://github.com/Medium/dynamite)&#8201;&mdash;&#8201;A promise-based DynamoDB client.
+* [Falkor](https://github.com/Medium/falkor)&#8201;&mdash;&#8201;HTTP Level Functional
   Testing Library.
-* [Leb](https://github.com/Obvious/leb) &mdash; Utilities for the LEB128
-  number representation.
-* [Matador](https://github.com/Obvious/matador) &mdash; Application
+* [Kew](https://github.com/Medium/kew)&#8201;&mdash;&#8201;A lightweight promise library optimized for node.js
+* [Matador](https://github.com/Medium/matador)&#8201;&mdash;&#8201;Application
   framework.
-* [Oid](https://github.com/Obvious/oid) &mdash; Utilities for object
+* [Oid](https://github.com/Medium/oid)&#8201;&mdash;&#8201;Utilities for object
   identity.
-* [Pipette](https://github.com/Obvious/pipette) &mdash; Stream and pipe
+* [Pipette](https://github.com/Medium/pipette)&#8201;&mdash;&#8201;Stream and pipe
   utilities.
-* [Populator](https://github.com/Obvious/populator) &mdash;
-  Asynchronous object populator.
-* [Ursa](https://github.com/Obvious/ursa) &mdash; RSA public/private key
-  crypto.
-* [Typ](https://github.com/Obvious/typ) &mdash; Type predicates and
+* [Shepherd](https://github.com/Medium/shepherd)&#8201;&mdash;&#8201;Asynchronous dependency injection for node.js.
+* [Typ](https://github.com/Medium/typ)&#8201;&mdash;&#8201;Type predicates and
   assertions.
-* [Variants](https://github.com/Obvious/variants) &mdash; A variants
+* [Variants](https://github.com/Medium/variants)&#8201;&mdash;&#8201;A variants
   (experiments, mods) system with dynamic flag evaluation.
 
 ### Node Build Tools
 
 These are build-time tools packaged as [Node](http://nodejs.org/) modules.
 
-* [PhantomJS](https://github.com/Obvious/phantomjs) &mdash; NPM wrapper for
+* [PhantomJS](https://github.com/Medium/phantomjs)&#8201;&mdash;&#8201;NPM wrapper for
   grabbing the right PhantomJS binary.
-* [Plovr](https://github.com/Obvious/plovr) &mdash; Integration of
-  the Plovr JavaScript build tool (a packaging of the Google Closure compiler).
-* [Soynode](https://github.com/Obvious/soynode) &mdash; Integration of
+* [Soynode](https://github.com/Medium/soynode)&#8201;&mdash;&#8201;Integration of
   the Soy template system (part of Google Closure).
 
 ### Other
 
-* [Open Source Umbrella Project](https://github.com/Obvious/open-source)
-  &mdash; This site.
+* [Open Source Umbrella Project](https://github.com/Medium/opensource)&#8201;&mdash;&#8201;This site.

ocla-1.0.md → cla-2.0.md

@@ -1,17 +1,15 @@
-The Obvious Contributors License Agreement
+The Contributors License Agreement
 ==========================================
 
-Version 1.0
+Version 2.0
 -----------
 
 ### Preface
 
-This Agreement is between You, the Users, the Contributors, and The
-Obvious Corporation. The intent of the Agreement is to clarify your
-responsibilities as a Contributor.
+This Agreement is between You, the Users, the Contributors, and A Medium Corporation. The intent of the Agreement is to clarify your responsibilities as a Contributor.
 
 The Agreement is meant to protect You, the Users, the Contributors,
-and The Obvious Corporation from the malicious misdeeds of others.
+and A Medium Corporation from the malicious misdeeds of others.
 The Agreement is *not* intended to restrict how You use Your own
 Contributions.
 
@@ -27,11 +25,10 @@ and the singular shall include the plural.
 
 2. "You" / "Your" — The individual signing this Agreement.
 
-3. "The Obvious Corporation" — The company which manages the
-   Projects. The company's website is at <http://obvious.com/>.
+3. "A Medium Corporation" &mdash; The company which manages the
+   Projects. The company's website is at <http://medium.com/>.
 
-4. "Project" &mdash; Open source projects being managed by The
-   Obvious Corporation. The Projects may all be found at
+4. "Project" &mdash; Open source projects being managed by A Medium Corporation. The Projects may all be found at
    <https://github.com/Obvious> with an overview at
    <https://github.com/Obvious/open-source>.
 
@@ -64,7 +61,7 @@ When You provide a Contribution to a Project:
 * You license that Contribution under the terms of the
   license of that Project. More specifically, You grant an irrevocable
   license for Your Contribution to the Users, the Contributors, and
-  The Obvious Corporation.
+  A Medium Corporation.
 
 * You assert that You have the authority and are able to license Your
   Contribution under the license of that Project.
@@ -81,5 +78,5 @@ Furthermore:
 
 * If You become aware of a problem with any of Your Contributions or
   with the fact that You have signed this Agreement, then You agree to
-  inform The Obvious Corporation about the problem, without any undue
+  inform A Medium Corporation about the problem, without any undue
   delay.

ocla-rationale.md → cla-rationale.md

@@ -1,10 +1,10 @@
-OCLA Rationale
+CLA Rationale
 ==============
 
 Why do this at all?
 -------------------
 
-The point of the OCLA signing process is to have a credible record of
+The point of the CLA signing process is to have a credible record of
 a developer stating that they really intend to contribute to an open
 source project. Technically speaking, the thing we are aiming for is a
 *non-repudiable* statement from a contributor, that is, a statement
@@ -18,7 +18,7 @@ by claiming they weren't really contributing under the project's open
 source license. For some projects "trouble" has historically come, for
 example, in the form of patent lawsuits.
 
-The Obvious Corporation wants to do our part to guard against this
+A Medium Corporation wants to do our part to guard against this
 potential trouble, and we believe so should you. We aren't innovating
 here by asking you to sign an agreement, but we *are* trying to
 innovate by making the agreement and process nearly-transparent,
@@ -58,16 +58,16 @@ We no longer live in that time.
 
 One wonderful thing about the world we live in today is that we can
 achieve the necessary non-reputiability without having to have a
-physical document. In the case of the OCLA, we bootstrap this ability
+physical document. In the case of the CLA, we bootstrap this ability
 off of the infrastructure provided by GitHub: More specifically, we
 treat GitHub as a neutral third party to witness the transactions
-between a would-be contributor and The Obvious Corporation. GitHub
+between a would-be contributor and A Medium Corporation. GitHub
 ends up acting sort of like a notary, in that its records of the
 actions — such as in particular the pull requests — of
 people using it can be taken as authoritative and unbiased.
 
 So, when a contributor forks this project, commits a change indicating
-agreement to the OCLA, and files a pull request back with this project,
+agreement to the CLA, and files a pull request back with this project,
 GitHub knows that all that happened, knows when it happened, and knows
 the identity of the entity taking all that action. Should there ever
 be a dispute about whether any of that took place, it's not just
@@ -85,7 +85,7 @@ traditional email. We promise never to use this information for
 any purpose other than resolving authorship disputes.
 
 The upshot is that filing a pull request containing a statement of
-agreement to the OCLA, along with the supplementary email, is close
+agreement to the MCLA, along with the supplementary email, is close
 enough to having submitted a signed physical document saying the same
 things. That is, this tactic is a workable solution to the problem. And
 since fits in naturally with how actual contributions get made, what

contributors/AdityaShirole.md

@@ -0,0 +1,13 @@
+2015-10-30
+
+I hereby agree to the terms of the Contributors License
+Agreement, version 2.0, with MD5 checksum
+0962bd43bb8849553d91650a78cb2924.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Aditya Shirole
+https://github.com/AdityaShirole

contributors/adrianrossouw.md

@@ -0,0 +1,13 @@
+2014-09-15
+
+I hereby agree to the terms of the Contributors License
+Agreement, version 2.0, with MD5 checksum
+0962bd43bb8849553d91650a78cb2924.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Adrian Rossouw
+https://github.com/AdrianRossouw

contributors/afang.md

@@ -0,0 +1,13 @@
+October 8, 2015
+
+I hereby agree to the terms of the Contributors License
+Agreement, version 2.0, with MD5 checksum
+0962bd43bb8849553d91650a78cb2924.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Andy Fang
+https://github.com/afang

contributors/apache/Filirom1.md

@@ -0,0 +1,13 @@
+2013-11-27
+
+I hereby agree to the terms of the Obvious Contributors License
+Agreement, version 1.0, with MD5 checksum
+fbe613f727e76c93e4a5967536c87fbe.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Romain Philibert
+https://github.com/Filirom1

contributors/apache/JaidenAshmore.md

@@ -0,0 +1,13 @@
+22/04/2013
+
+I hereby agree to the terms of the Obvious Contributors License
+Agreement, version 1.0, with MD5 checksum
+fbe613f727e76c93e4a5967536c87fbe.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Jaiden Ashmore
+https://github.com/JaidenAshmore

contributors/apache/JohnYangSam.md

@@ -0,0 +1,13 @@
+2012-12-31
+
+I hereby agree to the terms of the Obvious Contributors License
+Agreement, version 1.0, with MD5 checksum
+fbe613f727e76c93e4a5967536c87fbe.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+John Yang-Sammataro
+https://github.com/JohnYangSam

contributors/apache/Lindurion.md

@@ -0,0 +1,13 @@
+2013-10-11
+
+I hereby agree to the terms of the Obvious Contributors License
+Agreement, version 1.0, with MD5 checksum
+fbe613f727e76c93e4a5967536c87fbe.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+
+Eric W. Barndollar
+https://github.com/Lindurion

contributors/apache/MattWhelan.md

@@ -0,0 +1,13 @@
+Fri Dec  6 15:04:04 PST 2013
+
+I hereby agree to the terms of the Obvious Contributors License
+Agreement, version 1.0, with MD5 checksum
+fbe613f727e76c93e4a5967536c87fbe.
+
+I furthermore declare that I am authorized and able to make this
+agreement and sign this declaration.
+
+Signed,
+Matt Whelan
+
+https://github.com/MattWhelan