Seems people commenting so far agree collecting plugins for ktexteditor in a separate repo makes sense.
- name of repo?
- release group of repo?
- content of repo?
- layout of repo?
Name: "ktexteditor-addons" has been proposed, would follow naming pattern (e.g. "kdeplasma-addons", "kdepim-addons").
Release group: "KDE Frameworks" does not match, this is about plugins. Being part of "KDE Applications" would mean semi-automatic release & packaging handling. Own release schedule possible, but needs someone to care.
Content: At most this could be all plugins which implement KTextEditor::Plugin. Many existing plugins though are specific to Kate's idea of UI/UX options, like the tabswitcher or filemanager and just happen to reuse the plugin API for simplified code, but are not specific to text documents.
And goal of this repositpry so far has been to help with packaging. Like to enforce/guide distributions to create a separate package with only those plugins which are also interesting for none-Kate apps, to avoid deps on the fiull Kate package. And to ease binary bundle creation e.g. of KDevelop appimages/windows installer/macOS installers, which no longer would need to build all of Kate or maintain patches to just build interesting stuff. Or when building manually with kdesrc-build a non-Kate ktexteditor-based application.
The two plugins mentioned for use outside Kate are: snippets and preview. So the repo could start with these two and get other plugins added if there is demand/interest?
Layout: Right now in the kate repo all plugins are straight below "/addons", with own subdir per plugin. Could perhaps be "/src" or "/plugins" in the new repo, and again own subdir per plugin.
Please everyone give a comment with your replies to each open question.