proposal: use .tangled/ for config #275

While I agree that configuration in repo would be handy, it should not be .tangled/. Instead I think it should be something like .config/tangled. Please, do not pollute the repository root more than it is done right now.

@hauleth.dev .config/ is an XDG convention, whereas repository meta has a convention of being right at the root. You'll find things like .vscode/, .github/, .zen/, etc. Although it might seem a little polluting, this is generally how other repositories handle it too: there's no need to go against the grain

I'll also add that as a consequence of it being XDG convention, it's common for dotfiles repos with .config in them; might be a bad idea to overload that.

@ducky.ws yes, using .config directory is XDG-like. However why it is some kind of disadvantage? How is the fact that others doing something making it right? Masses are always right? Before XDG everyone also was spitting their dot files all around $HOME - that was also right?

I think that as Tangled.sh is still your it should do better than others instead of blindly following whatever they are doing. If some idea is good, then use it, if it is bad, then ignore it.

How about .repo or .repository instead of .tangled?

I think there can be quite a lot of people using .config directory to store there configs.

I can found over 2k repositories have .config directory for some reasons. These are just from sourcegraph-indexed repositories excluding archived ones so there can be even more.https://sourcegraph.com/search?q=context:global+file:%5E%5C.config/+select:repo&patternType=keyword&sm=0

Meanwhile .repo or .repository is used quite less and shows clearly that it is for repository settings. So it can be used as future standard if tangled-like hosting services gain more attention.

I'm quite new here so sorry if I completely miss the context.

we can use .repo/tangled if we are going to be more specific, tangled-specific features