Contributions, Issues, and Pull Requests.

[jub0t]

I'm actively accepting contributions, ideas, bug reports, feature requests, etc. Please read the text below on how to get started on contributing.

Rules

• No Third Party API/Cloud integration such as voice generators, image generators, video generators, etc.
• No code-changes or pull-request out of the blue (will be rejected).

Contributing:

• Read Issues and their comments to understand what needs to be worked on.
• Join the Concat Discord Server (link is also available on the README) for faster communication with the Contributors and community.
• Pick an area/issue you think you can help with and work on that. Work on one thing at a time, do not send PRs with large changes (like codebase refactoring).
• Submit your changes as a Pull Request.

Things to keep in mind

• We are building this project for consumer grade Desktop devices, so any code or piece of software that is integrated into this app must run locally (no APIs) and must be performant and scalable enough to run on most devices (potatoes). Don't suggest things like "local image inference" or the likes unless you have a really compelling argument.

Pages:
Issues: for Issues, Bug reports, Feature Requests, etc.

[michaltomczykowski]

A small contributing.md with project scope/architecture/structure/passing tests would be kinda useful

[TinyBrickBoy]

Idea: an Arch PKGBUILD in the repo under packaging/arch, next to the Nix flake.

On Arch and other rolling distros the AppImage from Releases opens as an empty
window. It carries the libwayland-client from its Ubuntu 22.04 builder, which is
older than the Mesa it ends up talking to, so EGL display creation fails with
EGL_BAD_PARAMETER and nothing renders. Building against the system WebKitGTK,
Wayland and Mesa avoids that class of problem entirely, and Arch users are the
group most likely to be filing the rough-edge reports you are asking for, so
making the app one command to install there pays back in bug reports.

It would be a -git package rather than a versioned one, because every green
build on main mints a new alpha tag and a pinned release goes stale within a
day. Nothing new at runtime: ffmpeg comes from the repos and whisper.cpp is an
optional dependency for transcription. It is a packaging file plus a short
README section, so it does not touch the app itself, and it is not on the
roadmap.

If you would rather it live on the AUR than in-tree, that works too and I would
maintain it there. Tell me which you prefer and I will send a PR.

[Bolaside]

oh man i'd be really grateful if you put it on AUR

[tpbrunner4-gif]

[tpbrunner4-gif]

found out .png files work and display properly, .jpg do not.

[Emmybilli]

software looks good and smooth but has no auto caption for windows yet. i think that would be a massive upgrade if added. its something that will really keep user on the software

[Domica]

@Emmybilli Can you clarify a bit, you mean captions for the whole timeline at once? You can submit an idea to issues as a feature with more details.

[firelord-rupeski]

Would be good to have an auto-update feature or some way to notify the app that a new update is available.

[sanyaskago-max]

Can't use local Windows fonts. Hanken Grotesk does not support Cyrillic letters.