Additional details on borgmatic sub-command wrapping idea.

Google-Summer-of-Code-2023-Ideas.md

@@ -299,7 +299,7 @@ Other issues tagged [help wanted](https://github.com/borgbackup/borg/issues?q=is
 **Skills required**: Python, Linux<br />
 **Description**: borgmatic is effectively a wrapper around Borg backup, providing additional features like a configuration file, database integration, etc. But borgmatic only wraps a fraction of the sub-commands that Borg provides. And for those that it does wrap, it doesn't necessarily support all command-line flags as borgmatic options. Users can always drop back down to running Borg directly for those missing sub-commands (or use the `borgmatic borg` action), but that doesn't provide all the conveniences of borgmatic and its configuration file.<br />
 **Task outline**: Implement borgmatic actions for all Borg sub-commands that are not yet implemented. For each Borg flag within those sub-commands, decide whether it makes sense to add a new borgmatic configuration option for it—or whether it would be more appropriate as a borgmatic action command-line flag. Also as part of this work, consider implementing missing flags/options on existing borgmatic actions.<br />
-**Additional details**: none<br />
+**Additional details**: Not all Borg sub-commands make sense to wrap. For instance, Borg invokes `borg serve` internally, and there's likely not a good use case for running it via borgmatic. Similarly, some Borg flags like `--info` and `--debug` shouldn't be exposed directly via borgmatic configuration options or command-line flags, because borgmatic uses them implicitly (e.g. via `--verbosity`) without exposing them to the end-user.<br />
 **Possible mentors**: [@witten][witten], [@real-yfprojects][real-yfprojects] (backup mentor)
 
 ### Backup and restore SQLite databases