Licence

Glint's own code is licensed under the Mozilla Public License 2.0 (MPL-2.0). In short, anyone may use, change and redistribute it. Changes to Glint's own files must be shared under the same licence, and the notices that credit Glint must be kept. Glint may be combined with code under other licences, such as Zephyr's Apache-2.0 code and cleave's MIT code. The licence comes with no warranty and limits liability (sections 6 and 7 of the MPL); the maintainer offers neither.

Each source file starts with this line, in the file's comment syntax:

SPDX-License-Identifier: MPL-2.0

Third-party code kept under third_party/ keeps its own licence and notices.

Sign-off on contributions

Contributions from anyone other than the maintainer must be signed off under the Developer Certificate of Origin below. By adding this line to each check-in comment, the contributor certifies the statements in it:

Signed-off-by: Full Name <email@example.org>

Unsigned contributions are not accepted.

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Provenance

Much of Glint is written by AI agents working under the maintainer's direction, and the check-in history records which agent made each change. The maintainer does not present anyone else's work as their own, but makes no further claim about the provenance of agent-written code. Anyone who finds code here that should carry someone else's notice is asked to say so, so it can be credited or removed.

How work is done

See PLAN.md, Development method: slices: each check-in is one slice, with a claim, the passage it implements, its demonstration and its size.