[code_research]

This is a very interesting service, thank you!

May I ask you for some little thing that might change the (development) world? Would you please like to introduce a folder, where people might put their dependency.yml file - this is an effort to finally stop the spreading cancer of "put one more config file into the project root".

I would like to suggest to call that folder simply "config" - all the projects and tools out there should have no problem with that. Optionally there could be one top level config file called "config.rc" - this file points to the actual config dir if it is not "config".

It would be verrry nice if one service just starts with that and hopefully all the others will follow and it will become a defacto standard. The pollution of the top level project directories really must stop.

Thank you!

[jacques_chester]

I've thought of the same thing, but I feel that the horse has well and truly bolted, run back through the barn a few times, kicked some shelving over and then continued out the front and over the horizon at a brisk pace.

[beefsack]

The ideal solution is a migration path; retain support for config in project root, but check a configuration directory first.

[jacques_chester]

Workable. It'd be nice to clean up the global namespace a bit. Especially when it's a single-repo project.

[rickhanlonii]

I think you'll want to check the root first then config to avoid breaking existing projects, but I'm a big +1 on this idea.

[andrewnez]

Agreed, I'll definitely the ability to move your dependencyci.yml file into a .github folder like the issue and pull request templates: https://github.com/blog/2111-issue-and-pull-request-template...

[code_research]

beefsack is right, please do NOT make it a github specific thing. Just one config folder. All config files for services, integration, etc. should go there.

Thanks again!

[beefsack]

Except this isn't GitHub specific.

[Sir_Cmpwn]

How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.

[code_research]

In the config.rc file you could call that folder however you want.

I personally do not like ".meta", because it is not clear what kind of information it may contain. "Meta" might be anything, documentation, description, website, design papers, everything is meta. It is a bit like using "Information" as a menu entry for a website.

[CiPHPerCoder]

It sounds like we should probably all get together and write a draft RFC for this. Choosing a good directory to toss everything into would be grand.

I'd prefer .well-known since there's already an RFC for it, but maybe .dev-extra would be more appropriate?

[robbles]

Do you really want to type either of those prefixes thousands of times? Brevity and lack of special chars in the name would be nice to have.

[glenjamin]

`.config` is probably a decent choice, as ~/.config for per-user settings seems to be gradually gaining adoption.

[jcassee]

Or .well-known? (analogous to https://tools.ietf.org/html/rfc5785)

[happyslobro]

How about we put each individual config file in its own individual directory? We could name the directory after the file too, so that it is clear where each file is ;)

No but seriously, I don't think this mess of config files in the project root is really a big deal. I already grouped the interesting stuff under /src. If it is a big deal, then lets hash out an RFC that covers the general concept of "configuration" once and for all and be done with it.

[tomschlick]

What about /.bots or /.ci ? Those are specific to these types of services.