1.0.0

Author: jonathantneal

.gitignore

@@ -0,0 +1,3 @@
+node_modules
+*.*cache
+*.log*

.travis.yml

@@ -0,0 +1,3 @@
+language: node_js
+node_js:
+  - stable

CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changes to CSS Database
+
+### 1.0.0 (January 16, 2017)
+
+- Initial version

LICENSE.md

@@ -0,0 +1,106 @@
+# CC0 1.0 Universal
+
+## Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator and
+subsequent owner(s) (each and all, an “owner”) of an original work of
+authorship and/or a database (each, a “Work”).
+
+Certain owners wish to permanently relinquish those rights to a Work for the
+purpose of contributing to a commons of creative, cultural and scientific works
+(“Commons”) that the public can reliably and without fear of later claims of
+infringement build upon, modify, incorporate in other works, reuse and
+redistribute as freely as possible in any form whatsoever and for any purposes,
+including without limitation commercial purposes. These owners may contribute
+to the Commons to promote the ideal of a free culture and the further
+production of creative, cultural and scientific works, or to gain reputation or
+greater distribution for their Work in part through the use and efforts of
+others.
+
+For these and/or other purposes and motivations, and without any expectation of
+additional consideration or compensation, the person associating CC0 with a
+Work (the “Affirmer”), to the extent that he or she is an owner of Copyright
+and Related Rights in the Work, voluntarily elects to apply CC0 to the Work and
+publicly distribute the Work under its terms, with knowledge of his or her
+Copyright and Related Rights in the Work and the meaning and intended legal
+effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+	 protected by copyright and related or neighboring rights (“Copyright and
+	 Related Rights”). Copyright and Related Rights include, but are not limited
+	 to, the following:
+	1. the right to reproduce, adapt, distribute, perform, display,
+		 communicate, and translate a Work;
+	2. moral rights retained by the original author(s) and/or performer(s);
+	3. publicity and privacy rights pertaining to a person’s image or likeness
+		 depicted in a Work;
+	4. rights protecting against unfair competition in regards to a Work,
+		 subject to the limitations in paragraph 4(i), below;
+	5. rights protecting the extraction, dissemination, use and reuse of data
+		 in a Work;
+	6. database rights (such as those arising under Directive 96/9/EC of the
+		 European Parliament and of the Council of 11 March 1996 on the legal
+		 protection of databases, and under any national implementation thereof,
+		 including any amended or successor version of such directive); and
+	7. other similar, equivalent or corresponding rights throughout the world
+		 based on applicable law or treaty, and any national implementations
+		 thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention of,
+applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
+unconditionally waives, abandons, and surrenders all of Affirmer’s Copyright
+and Related Rights and associated claims and causes of action, whether now
+known or unknown (including existing as well as future claims and causes of
+action), in the Work (i) in all territories worldwide, (ii) for the maximum
+duration provided by applicable law or treaty (including future time
+extensions), (iii) in any current or future medium and for any number of
+copies, and (iv) for any purpose whatsoever, including without limitation
+commercial, advertising or promotional purposes (the “Waiver”). Affirmer makes
+the Waiver for the benefit of each member of the public at large and to the
+detriment of Affirmer’s heirs and successors, fully intending that such Waiver
+shall not be subject to revocation, rescission, cancellation, termination, or
+any other legal or equitable action to disrupt the quiet enjoyment of the Work
+by the public as contemplated by Affirmer’s express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason be
+judged legally invalid or ineffective under applicable law, then the Waiver
+shall be preserved to the maximum extent permitted taking into account
+Affirmer’s express Statement of Purpose. In addition, to the extent the Waiver
+is so judged Affirmer hereby grants to each affected person a royalty-free, non
+transferable, non sublicensable, non exclusive, irrevocable and unconditional
+license to exercise Affirmer’s Copyright and Related Rights in the Work (i) in
+all territories worldwide, (ii) for the maximum duration provided by applicable
+law or treaty (including future time extensions), (iii) in any current or
+future medium and for any number of copies, and (iv) for any purpose
+whatsoever, including without limitation commercial, advertising or promotional
+purposes (the “License”). The License shall be deemed effective as of the date
+CC0 was applied by Affirmer to the Work. Should any part of the License for any
+reason be judged legally invalid or ineffective under applicable law, such
+partial invalidity or ineffectiveness shall not invalidate the remainder of the
+License, and in such case Affirmer hereby affirms that he or she will not (i)
+exercise any of his or her remaining Copyright and Related Rights in the Work
+or (ii) assert any associated claims and causes of action with respect to the
+Work, in either case contrary to Affirmer’s express Statement of Purpose.
+
+4. Limitations and Disclaimers.
+		1. No trademark or patent rights held by Affirmer are waived, abandoned,
+			 surrendered, licensed or otherwise affected by this document.
+		2. Affirmer offers the Work as-is and makes no representations or
+			 warranties of any kind concerning the Work, express, implied, statutory
+			 or otherwise, including without limitation warranties of title,
+			 merchantability, fitness for a particular purpose, non infringement, or
+			 the absence of latent or other defects, accuracy, or the present or
+			 absence of errors, whether or not discoverable, all to the greatest
+			 extent permissible under applicable law.
+		3. Affirmer disclaims responsibility for clearing rights of other persons
+			 that may apply to the Work or any use thereof, including without
+			 limitation any person’s Copyright and Related Rights in the Work.
+			 Further, Affirmer disclaims responsibility for obtaining any necessary
+			 consents, permissions or other rights required for any use of the Work.
+		4. Affirmer understands and acknowledges that Creative Commons is not a
+			 party to this document and has no duty or obligation with respect to
+			 this CC0 or use of the Work.
+
+For more information, please see
+http://creativecommons.org/publicdomain/zero/1.0/.

README.md

@@ -0,0 +1,162 @@
+# CSS Database [<img src="https://rawgit.com/jonathantneal/media-expressions-spec/gh-pages/css-logo.svg" alt="CSS Logo" width="90" height="90" align="right">][CSS Database]
+
+[![Build Status][cli-img]][cli-url]
+[![Licensing][lic-img]][lic-url]
+[![Changelog][log-img]][log-url]
+
+[CSS Database] is a comprehensive list of CSS features and their positions in the process of becoming implemented web standards. These positions reflect the [TC39 process].
+
+## Staging Process
+
+This staging process reflects the real-life stability of new CSS features.
+
+You can read an [inside view of the CSSWG] to learn about the official (and unofficial) development stages of CSS specifications. In reality, specifications and browser implementations happen out of sync. Stable CSS features are missing in all browsers, while other CSS features developed outside the [CSSWG] are already behind flags in Chrome. This is too ambiguous for the web development community, and a more accountable process is desired.
+
+#### Stage 0: Aspirational
+
+> “This is a crazy idea.”
+
+A CSS specification presented to the CSSWG by a [champion] within or outside the CSSWG. It should be considered highly instable and subject to change.
+
+#### Stage 1: Experimental
+
+> “This idea might not be crazy.”
+
+A CSS specification formally endorsed by the [CSSWG]. It should be considered highly instable and subject to change.
+
+#### Stage 2: Draft
+
+> “This idea is not crazy.”
+
+A CSS specification formally endorsed by the [CSSWG] and requiring implementations to move forward. It should be considered stable and subject to little change.
+
+#### Stage 3: Adoption
+
+> “This idea is becoming part of the web.”
+
+A CSS specification formally endorsed by the [CSSWG] and being implemented by [recognized browser vendors], possibly behind a flag. It should be considered stable and subject to little change.
+
+#### Stage 4: Complete
+
+> “This idea is part of the web.”
+
+A CSS specification formally endorsed by the [CSSWG] and implemented by all [recognized browser vendors].
+
+#### No Stage: Unrecognized
+
+> “I have no idea what I’m doing.”
+
+This is any specification that has not yet been presented to the [CSSWG], or that has been formally rejected or deprecated by the [CSSWG].
+
+## Contributing
+
+### Join the CSSWG
+
+Passionate and informed developers should consider joining the CSSWG. Read the [instructions for joining the CSSWG]. Pull requests are welcomed to update this section with a beginner-friendly version of those instructions.
+
+### Update this database
+
+Pull requests are some of the greatest contributions, so be sure they are focused in scope and avoid unrelated commits.
+
+- All contributions must follow the syntax and style of existing JSON files, which;
+	1. Exist as `features/${ feature }.json`, where `feature` is a thematic, [kebab-case] label representing the title and category of the feature.
+	2. Include all the [required fields].
+
+- New features include a link to a specification, which;
+	1. Describes what the feature does in as few words as possible.
+	2. Describes why the feature exists in as few words as possible.
+	3. Describes how the feature and its parts operate as clearly and completely as possible.
+
+- Changing features include a relevant citation proving its new position in the [staging process].
+
+For best results, be sure your contributions make sense to everyone else. If you’re unfamiliar with git, consider the following workflow.
+
+1. To begin, [fork this project], clone your fork, and add our upstream.
+	```bash
+	# Clone your fork of the repo into the current directory
+	git clone https://github.com/<your-user>/${ id }
+	# Navigate to the newly cloned directory
+	cd ${ id }
+	# Assign the original repo to a remote called "upstream"
+	git remote add upstream https://github.com/${ user }/${ id }
+	# Install the tools necessary for development
+	npm install
+	```
+
+2. Create a branch for your feature or update:
+	```bash
+	# Move into a new branch for a feature
+	git checkout -b feature/thing
+	```
+	```bash
+	# Or, move into a new branch for a update
+	git checkout -b update/something
+	```
+
+3. Be sure your code follows our practices.
+	```bash
+	# Test current code
+	npm test
+	```
+
+4. Push your branch up to your fork:
+	```bash
+	# Push a feature branch
+	git push origin feature/thing
+	```
+	```bash
+	# Or, push a fix branch
+	git push origin fix/something
+	```
+
+---
+
+## Terminology
+
+### Required Fields
+
+Required fields within a JSON file are, in order:
+
+- **`title`**: a unique name for the feature.
+- **`description`**: a brief description of the feature.
+- **`specification`**: a link to the latest draft of the specification.
+- **`stage`**: the position of the feature within the [staging process]. Stages should be a number, and unrecognized stages should be `null`.
+- **`citations`**: an array of links related to the feature or its progress.
+
+### Additional Fields
+
+Additional fields within a JSON file may be, in order:
+
+- **`issues`**: a link to issue tracking for the feature.
+- **`polyfills`**: an array of links to polyfills for the feature. Each link contains a `name` and `link` field, in that order.
+
+### Recognized Browser Vendors
+
+Recognized browser vendors include, in alphabetical order; Apple, Google, Microsoft, Mozilla, and Opera.
+
+### Champion
+
+A champion is the person responsible for advocating a new CSS feature to completion, performing the legwork necessary to ensure the concerns of interested [CSSWG] members are identified and incorporated into the proposal.
+
+[Champion]: #champion
+[CSSWG]: https://wiki.csswg.org/spec
+[CSS Database]: https://github.com/jonathantneal/css-db
+[fork this project]: fork
+[inside view of the CSSWG]: http://fantasai.inkedblade.net/weblog/2011/inside-csswg/process
+[instructions for joining the CSSWG]: https://www.w3.org/2004/01/pp-impl/32061/instructions
+[kebab-case]: http://wiki.c2.com/?KebabCase
+[recognized browser vendors]: #recognized-browser-vendors
+[required fields]: #required-fields
+[staging process]: #staging-process
+[TC39 process]: https://thefeedbackloop.xyz/tc39-a-process-sketch-stages-0-and-1/
+
+[npm-url]: https://www.npmjs.com/package/css-db
+[npm-img]: https://img.shields.io/npm/v/css-db.svg
+[cli-url]: https://travis-ci.org/jonathantneal/css-db
+[cli-img]: https://img.shields.io/travis/jonathantneal/css-db.svg
+[lic-url]: LICENSE.md
+[lic-img]: https://img.shields.io/badge/license-CC0--1.0-blue.svg
+[log-url]: CHANGELOG.md
+[log-img]: https://img.shields.io/badge/changelog-md-blue.svg
+[git-url]: https://gitter.im/postcss/postcss
+[git-img]: https://img.shields.io/badge/chat-gitter-blue.svg