Licence & contributions

VectorStep is licensed under Apache License 2.0. You are genuinely welcome to use it, run it, modify it, and fork it. The NOTICE file in each repo carries the copyright statement.

VectorStep is open source, but not open contribution. External code contributions are not accepted — pull requests are closed unmerged, regardless of how good they are. This is a policy about provenance, not a judgement about any particular patch. VectorStep is maintained by a single author, and keeping the copyright history unambiguous matters more to the project’s future than the occasional merged fix. SQLite operates the same way, for the same reason.

What is very welcome

• Bug reports. Steps to reproduce, what you expected, what happened, and the version you were running are usually enough.
• Feature requests and use cases — especially ones that explain what you were trying to do, not just what you want added.
• Questions about how something works. If the docs didn’t answer it, that’s useful signal on its own.
• Reports that the documentation is wrong or confusing. These are treated as bugs.

Please describe problems in prose rather than pasting a suggested patch — a report is more useful than a diff, and it keeps the contribution boundary clean for both sides.

Forking

Forking is explicitly fine and the licence permits it. If you need behaviour the project doesn’t provide, maintaining your own fork is a legitimate answer. The only carve-out: you may not use the VectorStep name or logo in a way that implies your fork is endorsed by or affiliated with this project. See Extending VectorStep for the three extension points designed for exactly this.

Getting in touch

If you’d rather just talk to a person — about a use case, whether something is a bug, or anything else — reach out at alex@vectorstep.io.