chore(yants): Prepare for depot-merge
Yants is being integrated at //depot/nix/yants
This commit is contained in:
Vincent Ambo
parent
5f6b51cce4
commit
210893ce09
13 changed files with 1 additions and 341 deletions
|
|
@ -1,4 +0,0 @@
|
||||||
language: nix
|
|
||||||
nix: 2.2.2
|
|
||||||
script:
|
|
||||||
- nix eval --raw '(import ./tests.nix)' --show-trace
|
|
||||||
|
|
@ -1,20 +0,0 @@
|
||||||
A SERMON ON ETHICS AND LOVE
|
|
||||||
===========================
|
|
||||||
|
|
||||||
One day Mal-2 asked the messenger spirit Saint Gulik to approach the Goddess and request Her presence for some desperate advice. Shortly afterwards the radio came on by itself, and an ethereal female Voice said **YES?**
|
|
||||||
|
|
||||||
"O! Eris! Blessed Mother of Man! Queen of Chaos! Daughter of Discord! Concubine of Confusion! O! Exquisite Lady, I beseech You to lift a heavy burden from my heart!"
|
|
||||||
|
|
||||||
**WHAT BOTHERS YOU, MAL? YOU DON'T SOUND WELL.**
|
|
||||||
|
|
||||||
"I am filled with fear and tormented with terrible visions of pain. Everywhere people are hurting one another, the planet is rampant with injustices, whole societies plunder groups of their own people, mothers imprison sons, children perish while brothers war. O, woe."
|
|
||||||
|
|
||||||
**WHAT IS THE MATTER WITH THAT, IF IT IS WHAT YOU WANT TO DO?**
|
|
||||||
|
|
||||||
"But nobody Wants it! Everybody hates it."
|
|
||||||
|
|
||||||
**OH. WELL, THEN *STOP*.**
|
|
||||||
|
|
||||||
At which moment She turned herself into an aspirin commercial and left The Polyfather stranded alone with his species.
|
|
||||||
|
|
||||||
SINISTER DEXTER HAS A BROKEN SPIROMETER.
|
|
||||||
115
CONTRIBUTING.md
115
CONTRIBUTING.md
|
|
@ -1,115 +0,0 @@
|
||||||
Contribution Guidelines
|
|
||||||
=======================
|
|
||||||
|
|
||||||
<!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-refresh-toc -->
|
|
||||||
**Table of Contents**
|
|
||||||
|
|
||||||
- [Contribution Guidelines](#contribution-guidelines)
|
|
||||||
- [Before making a change](#before-making-a-change)
|
|
||||||
- [Commit messages](#commit-messages)
|
|
||||||
- [Commit content](#commit-content)
|
|
||||||
- [Code quality](#code-quality)
|
|
||||||
- [Builds & tests](#builds--tests)
|
|
||||||
|
|
||||||
<!-- markdown-toc end -->
|
|
||||||
|
|
||||||
This is a loose set of "guidelines" for contributing to my projects.
|
|
||||||
Please note that I will not accept any pull requests that don't follow
|
|
||||||
these guidelines.
|
|
||||||
|
|
||||||
Also consider the [code of conduct](CODE_OF_CONDUCT.md). No really,
|
|
||||||
you should.
|
|
||||||
|
|
||||||
## Before making a change
|
|
||||||
|
|
||||||
Before making a change, consider your motivation for making the
|
|
||||||
change. Documentation updates, bug fixes and the like are *always*
|
|
||||||
welcome.
|
|
||||||
|
|
||||||
When adding a feature you should consider whether it is only useful
|
|
||||||
for your particular use-case or whether it is generally applicable for
|
|
||||||
other users of the project.
|
|
||||||
|
|
||||||
When in doubt - just ask me!
|
|
||||||
|
|
||||||
## Commit messages
|
|
||||||
|
|
||||||
All commit messages should follow the style-guide used by the [Angular
|
|
||||||
project][]. This means for the most part that your commit message
|
|
||||||
should be structured like this:
|
|
||||||
|
|
||||||
```
|
|
||||||
type(scope): Subject line with at most 68 a character length
|
|
||||||
|
|
||||||
Body of the commit message with an empty line between subject and
|
|
||||||
body. This text should explain what the change does and why it has
|
|
||||||
been made, *especially* if it introduces a new feature.
|
|
||||||
|
|
||||||
Relevant issues should be mentioned if they exist.
|
|
||||||
```
|
|
||||||
|
|
||||||
Where `type` can be one of:
|
|
||||||
|
|
||||||
* `feat`: A new feature has been introduced
|
|
||||||
* `fix`: An issue of some kind has been fixed
|
|
||||||
* `docs`: Documentation or comments have been updated
|
|
||||||
* `style`: Formatting changes only
|
|
||||||
* `refactor`: Hopefully self-explanatory!
|
|
||||||
* `test`: Added missing tests / fixed tests
|
|
||||||
* `chore`: Maintenance work
|
|
||||||
|
|
||||||
And `scope` should refer to some kind of logical grouping inside of
|
|
||||||
the project. In smaller projects or when the scope is very large, it
|
|
||||||
can be omitted.
|
|
||||||
|
|
||||||
Please take a look at the existing commit log for examples.
|
|
||||||
|
|
||||||
## Commit content
|
|
||||||
|
|
||||||
Multiple changes should be divided into multiple git commits whenever
|
|
||||||
possible. Common sense applies.
|
|
||||||
|
|
||||||
The fix for a single-line whitespace issue is fine to include in a
|
|
||||||
different commit. Introducing a new feature and refactoring
|
|
||||||
(unrelated) code in the same commit is not fine.
|
|
||||||
|
|
||||||
`git commit -a` is generally **taboo**.
|
|
||||||
|
|
||||||
In my experience making "sane" commits becomes *significantly* easier
|
|
||||||
as developer tooling is improved. The interface to `git` that I
|
|
||||||
recommend is [magit][]. Even if you are not yet an Emacs user, it
|
|
||||||
makes sense to install Emacs just to be able to use magit - it is
|
|
||||||
really that good.
|
|
||||||
|
|
||||||
For staging sane chunks on the command line with only git, consider
|
|
||||||
`git add -p`.
|
|
||||||
|
|
||||||
## Code quality
|
|
||||||
|
|
||||||
This one should go without saying - but please ensure that your code
|
|
||||||
quality does not fall below the rest of the project. This is of course
|
|
||||||
very subjective, but as an example if you place code that throws away
|
|
||||||
errors into a block in which errors are handled properly your change
|
|
||||||
will be rejected.
|
|
||||||
|
|
||||||
In my experience there is a strong correlation between the visual
|
|
||||||
appearance of a code block and its quality. This is a simple way to
|
|
||||||
sanity-check your work while squinting and keeping some distance from
|
|
||||||
your screen ;-)
|
|
||||||
|
|
||||||
## Builds & tests
|
|
||||||
|
|
||||||
Most of my projects are built using [Nix][] to avoid "build pollution"
|
|
||||||
via the user's environment. If you have Nix installed and are
|
|
||||||
contributing to a project that has a `default.nix`, consider using
|
|
||||||
`nix-build` to verify that builds work correctly.
|
|
||||||
|
|
||||||
If the project has tests, check that they still work before submitting
|
|
||||||
your change.
|
|
||||||
|
|
||||||
Both of these will usually be covered by Travis CI.
|
|
||||||
|
|
||||||
|
|
||||||
[Angular project]: https://gist.github.com/stephenparish/9941e89d80e2bc58a153#format-of-the-commit-message
|
|
||||||
[magit]: https://magit.vc/
|
|
||||||
[Nix]: https://nixos.org/nix/
|
|
||||||
202
LICENSE
202
LICENSE
|
|
@ -1,202 +0,0 @@
|
||||||
|
|
||||||
Apache License
|
|
||||||
Version 2.0, January 2004
|
|
||||||
http://www.apache.org/licenses/
|
|
||||||
|
|
||||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
||||||
|
|
||||||
1. Definitions.
|
|
||||||
|
|
||||||
"License" shall mean the terms and conditions for use, reproduction,
|
|
||||||
and distribution as defined by Sections 1 through 9 of this document.
|
|
||||||
|
|
||||||
"Licensor" shall mean the copyright owner or entity authorized by
|
|
||||||
the copyright owner that is granting the License.
|
|
||||||
|
|
||||||
"Legal Entity" shall mean the union of the acting entity and all
|
|
||||||
other entities that control, are controlled by, or are under common
|
|
||||||
control with that entity. For the purposes of this definition,
|
|
||||||
"control" means (i) the power, direct or indirect, to cause the
|
|
||||||
direction or management of such entity, whether by contract or
|
|
||||||
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
||||||
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
||||||
|
|
||||||
"You" (or "Your") shall mean an individual or Legal Entity
|
|
||||||
exercising permissions granted by this License.
|
|
||||||
|
|
||||||
"Source" form shall mean the preferred form for making modifications,
|
|
||||||
including but not limited to software source code, documentation
|
|
||||||
source, and configuration files.
|
|
||||||
|
|
||||||
"Object" form shall mean any form resulting from mechanical
|
|
||||||
transformation or translation of a Source form, including but
|
|
||||||
not limited to compiled object code, generated documentation,
|
|
||||||
and conversions to other media types.
|
|
||||||
|
|
||||||
"Work" shall mean the work of authorship, whether in Source or
|
|
||||||
Object form, made available under the License, as indicated by a
|
|
||||||
copyright notice that is included in or attached to the work
|
|
||||||
(an example is provided in the Appendix below).
|
|
||||||
|
|
||||||
"Derivative Works" shall mean any work, whether in Source or Object
|
|
||||||
form, that is based on (or derived from) the Work and for which the
|
|
||||||
editorial revisions, annotations, elaborations, or other modifications
|
|
||||||
represent, as a whole, an original work of authorship. For the purposes
|
|
||||||
of this License, Derivative Works shall not include works that remain
|
|
||||||
separable from, or merely link (or bind by name) to the interfaces of,
|
|
||||||
the Work and Derivative Works thereof.
|
|
||||||
|
|
||||||
"Contribution" shall mean any work of authorship, including
|
|
||||||
the original version of the Work and any modifications or additions
|
|
||||||
to that Work or Derivative Works thereof, that is intentionally
|
|
||||||
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
||||||
or by an individual or Legal Entity authorized to submit on behalf of
|
|
||||||
the copyright owner. For the purposes of this definition, "submitted"
|
|
||||||
means any form of electronic, verbal, or written communication sent
|
|
||||||
to the Licensor or its representatives, including but not limited to
|
|
||||||
communication on electronic mailing lists, source code control systems,
|
|
||||||
and issue tracking systems that are managed by, or on behalf of, the
|
|
||||||
Licensor for the purpose of discussing and improving the Work, but
|
|
||||||
excluding communication that is conspicuously marked or otherwise
|
|
||||||
designated in writing by the copyright owner as "Not a Contribution."
|
|
||||||
|
|
||||||
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
||||||
on behalf of whom a Contribution has been received by Licensor and
|
|
||||||
subsequently incorporated within the Work.
|
|
||||||
|
|
||||||
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
||||||
this License, each Contributor hereby grants to You a perpetual,
|
|
||||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
||||||
copyright license to reproduce, prepare Derivative Works of,
|
|
||||||
publicly display, publicly perform, sublicense, and distribute the
|
|
||||||
Work and such Derivative Works in Source or Object form.
|
|
||||||
|
|
||||||
3. Grant of Patent License. Subject to the terms and conditions of
|
|
||||||
this License, each Contributor hereby grants to You a perpetual,
|
|
||||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
||||||
(except as stated in this section) patent license to make, have made,
|
|
||||||
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
||||||
where such license applies only to those patent claims licensable
|
|
||||||
by such Contributor that are necessarily infringed by their
|
|
||||||
Contribution(s) alone or by combination of their Contribution(s)
|
|
||||||
with the Work to which such Contribution(s) was submitted. If You
|
|
||||||
institute patent litigation against any entity (including a
|
|
||||||
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
||||||
or a Contribution incorporated within the Work constitutes direct
|
|
||||||
or contributory patent infringement, then any patent licenses
|
|
||||||
granted to You under this License for that Work shall terminate
|
|
||||||
as of the date such litigation is filed.
|
|
||||||
|
|
||||||
4. Redistribution. You may reproduce and distribute copies of the
|
|
||||||
Work or Derivative Works thereof in any medium, with or without
|
|
||||||
modifications, and in Source or Object form, provided that You
|
|
||||||
meet the following conditions:
|
|
||||||
|
|
||||||
(a) You must give any other recipients of the Work or
|
|
||||||
Derivative Works a copy of this License; and
|
|
||||||
|
|
||||||
(b) You must cause any modified files to carry prominent notices
|
|
||||||
stating that You changed the files; and
|
|
||||||
|
|
||||||
(c) You must retain, in the Source form of any Derivative Works
|
|
||||||
that You distribute, all copyright, patent, trademark, and
|
|
||||||
attribution notices from the Source form of the Work,
|
|
||||||
excluding those notices that do not pertain to any part of
|
|
||||||
the Derivative Works; and
|
|
||||||
|
|
||||||
(d) If the Work includes a "NOTICE" text file as part of its
|
|
||||||
distribution, then any Derivative Works that You distribute must
|
|
||||||
include a readable copy of the attribution notices contained
|
|
||||||
within such NOTICE file, excluding those notices that do not
|
|
||||||
pertain to any part of the Derivative Works, in at least one
|
|
||||||
of the following places: within a NOTICE text file distributed
|
|
||||||
as part of the Derivative Works; within the Source form or
|
|
||||||
documentation, if provided along with the Derivative Works; or,
|
|
||||||
within a display generated by the Derivative Works, if and
|
|
||||||
wherever such third-party notices normally appear. The contents
|
|
||||||
of the NOTICE file are for informational purposes only and
|
|
||||||
do not modify the License. You may add Your own attribution
|
|
||||||
notices within Derivative Works that You distribute, alongside
|
|
||||||
or as an addendum to the NOTICE text from the Work, provided
|
|
||||||
that such additional attribution notices cannot be construed
|
|
||||||
as modifying the License.
|
|
||||||
|
|
||||||
You may add Your own copyright statement to Your modifications and
|
|
||||||
may provide additional or different license terms and conditions
|
|
||||||
for use, reproduction, or distribution of Your modifications, or
|
|
||||||
for any such Derivative Works as a whole, provided Your use,
|
|
||||||
reproduction, and distribution of the Work otherwise complies with
|
|
||||||
the conditions stated in this License.
|
|
||||||
|
|
||||||
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
||||||
any Contribution intentionally submitted for inclusion in the Work
|
|
||||||
by You to the Licensor shall be under the terms and conditions of
|
|
||||||
this License, without any additional terms or conditions.
|
|
||||||
Notwithstanding the above, nothing herein shall supersede or modify
|
|
||||||
the terms of any separate license agreement you may have executed
|
|
||||||
with Licensor regarding such Contributions.
|
|
||||||
|
|
||||||
6. Trademarks. This License does not grant permission to use the trade
|
|
||||||
names, trademarks, service marks, or product names of the Licensor,
|
|
||||||
except as required for reasonable and customary use in describing the
|
|
||||||
origin of the Work and reproducing the content of the NOTICE file.
|
|
||||||
|
|
||||||
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
||||||
agreed to in writing, Licensor provides the Work (and each
|
|
||||||
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
||||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
||||||
implied, including, without limitation, any warranties or conditions
|
|
||||||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
||||||
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
||||||
appropriateness of using or redistributing the Work and assume any
|
|
||||||
risks associated with Your exercise of permissions under this License.
|
|
||||||
|
|
||||||
8. Limitation of Liability. In no event and under no legal theory,
|
|
||||||
whether in tort (including negligence), contract, or otherwise,
|
|
||||||
unless required by applicable law (such as deliberate and grossly
|
|
||||||
negligent acts) or agreed to in writing, shall any Contributor be
|
|
||||||
liable to You for damages, including any direct, indirect, special,
|
|
||||||
incidental, or consequential damages of any character arising as a
|
|
||||||
result of this License or out of the use or inability to use the
|
|
||||||
Work (including but not limited to damages for loss of goodwill,
|
|
||||||
work stoppage, computer failure or malfunction, or any and all
|
|
||||||
other commercial damages or losses), even if such Contributor
|
|
||||||
has been advised of the possibility of such damages.
|
|
||||||
|
|
||||||
9. Accepting Warranty or Additional Liability. While redistributing
|
|
||||||
the Work or Derivative Works thereof, You may choose to offer,
|
|
||||||
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
||||||
or other liability obligations and/or rights consistent with this
|
|
||||||
License. However, in accepting such obligations, You may act only
|
|
||||||
on Your own behalf and on Your sole responsibility, not on behalf
|
|
||||||
of any other Contributor, and only if You agree to indemnify,
|
|
||||||
defend, and hold each Contributor harmless for any liability
|
|
||||||
incurred by, or claims asserted against, such Contributor by reason
|
|
||||||
of your accepting any such warranty or additional liability.
|
|
||||||
|
|
||||||
END OF TERMS AND CONDITIONS
|
|
||||||
|
|
||||||
APPENDIX: How to apply the Apache License to your work.
|
|
||||||
|
|
||||||
To apply the Apache License to your work, attach the following
|
|
||||||
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
||||||
replaced with your own identifying information. (Don't include
|
|
||||||
the brackets!) The text should be enclosed in the appropriate
|
|
||||||
comment syntax for the file format. We also recommend that a
|
|
||||||
file or class name and description of purpose be included on the
|
|
||||||
same "printed page" as the copyright notice for easier
|
|
||||||
identification within third-party archives.
|
|
||||||
|
|
||||||
Copyright [yyyy] [name of copyright owner]
|
|
||||||
|
|
||||||
Licensed under the Apache License, Version 2.0 (the "License");
|
|
||||||
you may not use this file except in compliance with the License.
|
|
||||||
You may obtain a copy of the License at
|
|
||||||
|
|
||||||
http://www.apache.org/licenses/LICENSE-2.0
|
|
||||||
|
|
||||||
Unless required by applicable law or agreed to in writing, software
|
|
||||||
distributed under the License is distributed on an "AS IS" BASIS,
|
|
||||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
||||||
See the License for the specific language governing permissions and
|
|
||||||
limitations under the License.
|
|
||||||
1
nix/yants/.skip-subtree
Normal file
1
nix/yants/.skip-subtree
Normal file
|
|
@ -0,0 +1 @@
|
||||||
|
Yants subtree contains no further derivations.
|
||||||
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
|
Before Width: | Height: | Size: 32 KiB After Width: | Height: | Size: 32 KiB |
|
Before Width: | Height: | Size: 69 KiB After Width: | Height: | Size: 69 KiB |
|
Before Width: | Height: | Size: 42 KiB After Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 68 KiB After Width: | Height: | Size: 68 KiB |
Loading…
Reference in a new issue