We're considering going the extra mile after including several well known files from the charm's project (`metadata.yaml`, `config.yaml`, etc). We have several options: - include **everything** present in the project's directory - include everything except some specifics, like Juju does: - don't include `.git`, `.bzr`, etc... (or directly avoid including all hidden files/dirs) - don't include symlinks that are pointing to outside the project's directory - include only very well known files (`metadata.yaml`, etc), and have a configuration for the developer to specify other files to be included. Last option involves having some kind of "manifest", but note that first two options also would grow some kind of "block list" for the developer to specify something to *not* be included. There's a compromise between both choices: if the developer needs to specify which files to be included, they may get caught by surprise, having built and published a charm lacking a file (broken!); if the developer needs to blocklist which files to be avoided in the package, they may got caught by surprise and have published a controversial file (security!).