vivac 0.17.2

Provenance tree for work: every node knows which node it was born from
# Contributing

**Issues are open. Pull requests are not, yet.**

## Issues

If something does not work, or does not do what the docs say it does, open an
issue. That is the report I want most: vivac has been measured on my own
projects and nowhere else, and whether it holds up on yours is the one thing I
cannot find out alone.

The forms ask for the version, the harness and the system, and for what you
ran. They do not ask for your tree, and please do not paste it: a tree is
prose about your project — what was decided in it and why — and an issue is
public. Paste the command and the error it printed, and reword anything that
names what you are working on.

A question is welcome, and so is a proposal, as long as it says what it would
let you do that you cannot do now.

I maintain this alone, so there is no promised response time. Every issue is
read, and every one gets an answer, even when the answer is no. A new issue
carries the `triage` label until it has one, so what is still waiting is
never a matter of trust: it is
[a search](https://github.com/JAAvila-Of/vivac/issues?q=is%3Aopen+label%3Atriage).

## Pull requests

Not being accepted at the moment. Not for lack of interest, and not as a
judgement on anybody's code. The model is still moving, and every decision
here is justified against the [pillars](docs/PILLARS.md) and against a design
corpus that is not public. That makes outside review unfair in one direction:
a well-written patch could be turned down for a reason its author had no way
to read, and asking for work under those terms would waste it. If you can see
the fix, describe it in an issue: it gets in just as well from there.

If you want to build on it, the licence is `MIT OR Apache-2.0` and a fork
needs nobody's permission. Nothing here is a claim on what you do with it.

This will change. When the model settles, this file will say so.

## Conduct

[`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md) says what is expected in the issues,
and what I do when it is not.

## Security

A security flaw does not go in an issue: [`SECURITY.md`](SECURITY.md) says
where it goes and why.