austinandClaude Opus 5
76c6e05ee0
Lint / REUSE compliance (push) Successful in 3s
Lint / clang-format (push) Failing after 5s
Build and Test / Build and run tests (push) Failing after 2s
Build and Publish Flatpak / Build Flatpak (push) Failing after 3s
Build and Publish Flatpak / Deploy hosted repo to Pages (push) Skipped
- Fix Save on the edit form silently dropping stage changes; report a missing company or title instead of saving a blank field - Rework the pipeline Sankey: drop-offs split off each stage in level lanes and rejoin their outcome without braiding - Count each application once as a forward path, so back moves and ghosted-then-rejected no longer draw extra ribbons - First-run choice of database location (default, a folder, or an existing file used in place), plus a Database section in Preferences - --db <path> for the GUI and every subcommand - Bump the version, add the 0.1.4 metainfo release, and update the manifest's pinned tag Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01BxDf7HqD1xPnsZP8wt3NTk
117 lines
4.5 KiB
XML
117 lines
4.5 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!-- SPDX-FileCopyrightText: 2026 ToServeTheKing <[email protected]> -->
|
|
<!-- SPDX-License-Identifier: CC0-1.0 -->
|
|
<component type="desktop-application">
|
|
<id>io.github.toservetheking.Kareer</id>
|
|
<metadata_license>CC0-1.0</metadata_license>
|
|
<project_license>GPL-3.0-or-later</project_license>
|
|
|
|
<name>Kareer</name>
|
|
<summary>Track your job applications</summary>
|
|
|
|
<keywords>
|
|
<keyword>job</keyword>
|
|
<keyword>career</keyword>
|
|
<keyword>applications</keyword>
|
|
<keyword>tracker</keyword>
|
|
<keyword>resume</keyword>
|
|
<keyword>sankey</keyword>
|
|
</keywords>
|
|
|
|
<description>
|
|
<p>
|
|
Kareer is a Kirigami application for tracking job applications from
|
|
first contact through to an offer. It records the details that matter -
|
|
company, title, salary range and expectations, source, and dates - and
|
|
every stage change is kept as history.
|
|
</p>
|
|
<p>
|
|
A Sankey diagram visualizes the whole pipeline at a glance, showing
|
|
where applications progress and where they drop off between stages
|
|
such as Applied, Screening, Interview and Offer.
|
|
</p>
|
|
<p>
|
|
Every action is also available from the command line, so applications
|
|
can be logged automatically by other tools (for example a resume
|
|
generator) without opening the GUI.
|
|
</p>
|
|
</description>
|
|
|
|
<launchable type="desktop-id">io.github.toservetheking.Kareer.desktop</launchable>
|
|
|
|
<screenshots>
|
|
<screenshot type="default">
|
|
<image>https://raw.githubusercontent.com/toservetheking/Kareer/main/screenshots/dashboard.png</image>
|
|
<caption>The application pipeline as a Sankey diagram</caption>
|
|
</screenshot>
|
|
</screenshots>
|
|
|
|
<branding>
|
|
<color type="primary" scheme_preference="light">#63d4c7</color>
|
|
<color type="primary" scheme_preference="dark">#1a7a70</color>
|
|
</branding>
|
|
|
|
<url type="homepage">https://github.com/toservetheking/Kareer</url>
|
|
<url type="bugtracker">https://github.com/toservetheking/Kareer/issues</url>
|
|
|
|
<provides>
|
|
<binary>kareer</binary>
|
|
</provides>
|
|
|
|
<developer id="io.github.toservetheking">
|
|
<name>toservetheking</name>
|
|
</developer>
|
|
|
|
<content_rating type="oars-1.1"/>
|
|
|
|
<releases>
|
|
<release version="0.1.4" date="2026-09-11">
|
|
<description>
|
|
<ul>
|
|
<li>Fix Save on the edit form silently dropping stage changes, and report missing company or title</li>
|
|
<li>Rework the pipeline diagram so drop-offs split off each stage and rejoin their outcome without braiding</li>
|
|
<li>Count each application once in the pipeline, so moving back a stage or being ghosted then rejected no longer draws extra ribbons</li>
|
|
<li>Choose where the database lives on first run: the default location, a folder of your choice, or an existing database</li>
|
|
<li>Move, open or reset the database location from Preferences</li>
|
|
<li>Add a --db option to use a specific database file from the command line or the GUI</li>
|
|
</ul>
|
|
</description>
|
|
</release>
|
|
<release version="0.1.3" date="2026-08-31">
|
|
<description>
|
|
<ul>
|
|
<li>Redesign the Sankey pipeline layout: top-aligned funnel, columns spread across the full width, labels always visible</li>
|
|
<li>Order ribbons at each stage to stop them braiding over each other</li>
|
|
<li>Canonicalize stage names written via the CLI (e.g. "rejected" now maps to "Rejected") and repair existing databases</li>
|
|
<li>Debounce window-resize relayouts and stop re-reading the database on resize</li>
|
|
</ul>
|
|
</description>
|
|
</release>
|
|
<release version="0.1.2" date="2026-07-03">
|
|
<description>
|
|
<ul>
|
|
<li>Rework the add/edit form onto a generic, catalog-driven field model</li>
|
|
<li>Add a Preferences page with a color-scheme switcher</li>
|
|
<li>Add an About page</li>
|
|
<li>Ship a full hicolor icon set instead of a single scalable SVG</li>
|
|
<li>Match KDE System Settings' Audio page layout for the edit form</li>
|
|
</ul>
|
|
</description>
|
|
</release>
|
|
<release version="0.1.1" date="2026-07-03">
|
|
<description>
|
|
<ul>
|
|
<li>Run the test suite in CI on every pull request</li>
|
|
<li>Add REUSE license-compliance metadata</li>
|
|
<li>Add a CONTRIBUTING guide</li>
|
|
</ul>
|
|
</description>
|
|
</release>
|
|
<release version="0.1.0" date="2026-07-03">
|
|
<description>
|
|
<p>Initial release.</p>
|
|
</description>
|
|
</release>
|
|
</releases>
|
|
</component>
|