I am looking for a suitable license for a current software project. The project is special as it is rather a template, its primary goal is to provide a solid basis for scientific software. Therefore, I would like to provide the source code (only little amounts of actual source code, the majority of the project are configuration files for CMake, YAML configuration files for continuous integration, etc.) under a license that is very permissive.
The typical work flow would be to clone the project and adapting it, including renaming the project and changing the license in LICENSE and (if any) in the source code files. Hence, anyone should be able to copy and adapt the source code, use it for their own project (commercial or open-source), and even re-license it.
Now the only thing that prevents me from CC0'ing the code is that an attribution would be nice. However, I am not sure how attribution is actually defined. For me it would be sufficient if at some point (README or ACKNOWLEDGMENTS for open-source projects, in the documentation of a commercial software) the original project is mentioned.
What would be a suitable license for this situation? I was thinking about Creative Commons CC-BY 4.0 license, which would require attribution but apart from that everyone is allowed to do anything. The CC licenses are generally considered not appropriate for software (as pointed out here, for example), but I would say it might fit here as it is not a common software project.
How does the license have to be included? In LICENSE I would say. Does it have to be in all the source files (which I find inconvenient)?
What forms could the attribution assume?