wirenote 0.1.0__tar.gz

wirenote-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.tmp
+
+# Raw captures: hostnames, user name, device names, room names. Commit only scrubbed
+# traces made with scripts/make_replay.py (tests/replay/).
+tests/fixtures/
+.venv/
+.pytest_cache/
+
+# AI assistant working files stay local: plans, specs, agent instructions.
+docs/superpowers/
+.superpowers/
+.claude/
+CLAUDE.md
+AGENTS.md

wirenote-0.1.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+All notable changes are listed here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow [Semantic Versioning](https://semver.org/).
+
+## [0.1.0] - 2026-10-26
+
+First public release. Runs on Linux (x86_64 and ARM64) with PipeWire and Python 3.11 to 3.14.
+
+### Added
+
+- Call detection on PipeWire, with a Record / Ignore prompt; app rules in `apps.toml`.
+- Two-track recording (your mic and the system audio), auto-stop, crash recovery.
+- Transcription with faster-whisper, speakers told apart and named, local summaries through Ollama or, opt-in, Claude.
+- Markdown notes and a local meetings app: search, playback, notes during the call, action items, Ask across meetings, follow-up email.
+- Settings page: summaries, transcription, consent line, Claude key and calendars.
+- `wirenote setup install` / `uninstall`, `wirenote doctor`, `wirenote open`.
+- Works outside KDE: clipboard through `wl-copy`, `xclip` or `xsel`, and prompts without notification buttons.
+
+### Security
+
+- Recordings, notes and settings are private to your user (umask 077).
+- The meetings app only serves your own user, through a one-time login.
+- Calendar feeds are limited and must use https; untrusted text is escaped in notifications and notes.
+- Logs leave out room names, note paths and speaker names; model downloads are pinned.
+
+[0.1.0]: https://github.com/knowhrishi/wirenote/releases/tag/v0.1.0

wirenote-0.1.0/CLA.md

@@ -0,0 +1,150 @@
+# Wirenote Individual Contributor License Agreement
+
+Version 1.0, 26 October 2026
+
+Thank you for contributing to Wirenote. This agreement sets out the rights you
+give when you send a contribution. **You keep the copyright in your work.** You
+sign once, and the agreement covers every contribution you send to Wirenote.
+
+In short: you allow the Maintainer to use your contribution in Wirenote under
+the GNU Affero General Public License and also under other terms, for example
+a commercial edition for companies; in return, every accepted contribution
+stays available as open source. The numbered sections below are the binding
+text.
+
+## 1. Definitions
+
+- **"Maintainer"**: Hrishikesh Jadhav, who maintains Wirenote, and anyone to
+  whom this agreement is transferred under section 8.
+- **"You"**: the natural person who signs this agreement.
+- **"Wirenote"**: the software published at
+  <https://github.com/knowhrishi/wirenote>, including its documentation and
+  all its past and future versions, under whatever name it is published.
+- **"Contribution"**: any work of authorship, such as code, documentation,
+  translations, designs or tests, that You Submit to Wirenote and that is
+  intended for inclusion in it. Material that You clearly mark as
+  "Not a Contribution" when You Submit it is not a Contribution.
+- **"Submit"**: to send a Contribution to the Maintainer in any form,
+  including pull requests, patches, issue comments and attachments, and
+  messages on the project's communication channels.
+
+## 2. Copyright license
+
+You grant the Maintainer, and the recipients of software distributed by the
+Maintainer, a worldwide, non-exclusive, free-of-charge, royalty-free,
+irrevocable license, for the full term of copyright, to reproduce, modify,
+prepare derivative works of, publicly display, publicly perform, make
+available to the public, sublicense and distribute Your Contributions and
+derivative works of them, in any form and **under any license terms**,
+including licenses other than the GNU Affero General Public License, such as
+proprietary or commercial licenses.
+
+This license covers all types of use known when You Submit the Contribution
+and, as far as the applicable law allows this agreement to grant them, types
+of use that become known later.
+
+To the extent the applicable law gives You a claim to payment for these
+rights, You waive it, as far as that law allows. You may still sell your own
+copies or other licenses of Your Contributions; this agreement is
+non-exclusive.
+
+## 3. Patent license
+
+You grant the Maintainer, and the recipients of software distributed by the
+Maintainer, a worldwide, non-exclusive, free-of-charge, royalty-free,
+irrevocable patent license to make, have made, use, offer to sell, sell,
+import and otherwise transfer Your Contributions and Wirenote. This license
+covers only those patent claims that You can license and that are necessarily
+infringed by Your Contribution alone or by its combination with the version
+of Wirenote to which You Submitted it.
+
+If any entity starts patent litigation (including a cross-claim or
+counterclaim) alleging that Your Contribution, or Wirenote, infringes a
+patent, the patent licenses granted to that entity under this agreement for
+that Contribution or for Wirenote end on the date that litigation is filed.
+
+## 4. The Maintainer's commitments
+
+1. **Open source stays open.** Every Contribution that is accepted into
+   Wirenote will remain available to the public under a license approved by
+   the Open Source Initiative, such as the GNU Affero General Public License,
+   version 3 or later. The rights in section 2 allow the Maintainer to offer
+   Wirenote under other terms as well; they do not allow withdrawing Your
+   Contribution from the open source version.
+2. **Credit.** Your authorship stays recorded in the project's version
+   history.
+3. **No obligation.** The Maintainer may decide not to use a Contribution,
+   and may change it before or after including it.
+
+## 5. What You confirm
+
+1. You are legally able to enter into this agreement.
+2. Each Contribution is Your original creation, or You have the right to
+   Submit it under this agreement. If any part of a Contribution comes from
+   someone else, You say so when You Submit it, and You name its source and
+   license.
+3. As far as You know, Your Contributions do not infringe anyone else's
+   rights.
+4. If an employer or anyone else has rights in Your Contributions (for
+   example because Your employment contract covers software You write), You
+   have their written permission to Submit the Contributions and to grant
+   the licenses in this agreement, or they have waived those rights.
+5. You will tell the Maintainer promptly if any of this stops being true.
+
+If You want to contribute on behalf of your employer or another
+organization, please open an issue first; the organization then signs a
+separate agreement.
+
+## 6. No warranty; liability
+
+Unless You agree otherwise in writing, You provide Your Contributions
+"as is", without warranties or conditions of any kind, and You are not
+expected to provide support for them.
+
+As far as the applicable law allows, neither You nor the Maintainer is
+liable to the other for damages arising from this agreement, except for
+damages caused intentionally or through gross negligence, and except for
+injury to life, body or health.
+
+## 7. Moral rights
+
+Nothing in this agreement affects moral rights that the applicable law does
+not allow You to give up. Within those limits, You agree that the Maintainer
+may modify Your Contributions, combine them with other works, and credit You
+through the version history rather than in each file.
+
+## 8. Transfer
+
+The Maintainer may transfer this agreement, with all its rights and
+obligations, to a person or legal entity that takes over the maintenance of
+Wirenote, including a company the Maintainer founds or controls. The
+transfer is valid only if the new party is bound by section 4. You agree to
+such a transfer in advance.
+
+## 9. Stopping
+
+You may end this agreement at any time for Contributions You Submit in the
+future, by telling the Maintainer in writing (an issue or an email is
+enough). The licenses for Contributions You Submitted before that remain in
+force.
+
+## 10. General
+
+1. This agreement is governed by the law of the Federal Republic of Germany,
+   excluding the United Nations Convention on Contracts for the
+   International Sale of Goods. Mandatory consumer protection rules of the
+   country where You live remain unaffected.
+2. If any provision of this agreement is invalid or unenforceable, the rest
+   remains in force, and the invalid provision is replaced by a valid one
+   that comes closest to its purpose.
+3. This agreement is the complete agreement between You and the Maintainer
+   about Your Contributions. A later version of it applies to You only if
+   You sign that version.
+
+## 11. How to sign
+
+When You open Your first pull request, the CLA Assistant bot posts a comment
+with a link. Follow it, sign in with GitHub, and select "I agree". Your
+GitHub account name, the date and the version of this agreement are
+recorded. You do not need to sign again for later pull requests, unless a
+new version of this agreement is published.

wirenote-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement privately, through the repository's **Security** tab › **Report a vulnerability** (only the maintainer can read it; start the title with "Code of conduct"). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

wirenote-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,43 @@
+# Contributing to Wirenote
+
+Thank you for helping. Bug reports, tested fixes, support for more call apps and desktops, and clearer docs are all welcome.
+
+## Before you start
+
+- **Bugs:** open an issue with your distribution, desktop, PipeWire version (`pipewire --version`) and the output of `wirenote doctor`. Never attach recordings, transcripts, calendar links or full logs: they contain other people's words and names.
+- **Larger changes:** open an issue first, so we can agree on the approach before you spend time on it.
+- **Security problems:** do not open an issue; see [SECURITY.md](SECURITY.md).
+
+## Development setup
+
+```sh
+git clone https://github.com/knowhrishi/wirenote
+cd wirenote
+uv sync
+uv run pytest -q
+uv run pyflakes src tests
+```
+
+Run your checkout as the real thing with `uv tool install --editable --force .` and `wirenote setup install`.
+
+The design notes in [docs/dev/](docs/dev/) explain why the detector, the capture and the processing work the way they do; [docs/dev/PLAN.md](docs/dev/PLAN.md) has the defaults table every threshold in the code refers to.
+
+## Pull requests
+
+- Keep each pull request to one change, with a test that fails without it. The tests run without PipeWire, a GPU or network access; keep it that way (see the fakes in `tests/`).
+- Every Python file starts with the license header:
+  ```python
+  # SPDX-License-Identifier: AGPL-3.0-or-later
+  # Copyright (c) 2026 Hrishikesh Jadhav
+  ```
+  If you add a file, use the same header; you keep the copyright in your changes (see the CLA below).
+- Anything that sends data off the computer must be opt-in and listed in [PRIVACY.md](PRIVACY.md) and in the app's disclosure text.
+- To add a call app, add a rule to the defaults in `src/wirenote/config/apps.py` and say how you verified it (`wirenote dump-streams` during a call shows what the detector sees).
+
+## Contributor License Agreement
+
+Before your first pull request is merged, you sign the [CLA](CLA.md) once; a bot asks you on the pull request. It lets the maintainer also offer Wirenote under other terms (for example a supported edition for companies), while every accepted contribution stays available under an open source license.
+
+## Code of conduct
+
+Everyone taking part follows the [code of conduct](CODE_OF_CONDUCT.md).