6 ms·

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 introduc

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 10y ago
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 10y ago
  The ideal solution is a migration path; retain support for config in project root, but check a configuration directory first.
  - jacques_chester 10y ago
    Workable. It'd be nice to clean up the global namespace a bit. Especially when it's a single-repo project.
  - rickhanlonii 10y ago
    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 10y ago
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-templates https://github.com/blog/2111-issue-and-pull-request-template...
- beefsack 10y ago
  Except this isn't GitHub specific.
- code_research 10y ago
  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!
- Sir_Cmpwn 10y ago
  How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.
  - code_research 10y ago
    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 10y ago
      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?
      - 10y ago

jacques_chester 10y ago

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 10y ago
The ideal solution is a migration path; retain support for config in project root, but check a configuration directory first.
- jacques_chester 10y ago
  Workable. It'd be nice to clean up the global namespace a bit. Especially when it's a single-repo project.
- rickhanlonii 10y ago
  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 10y ago

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-templates https://github.com/blog/2111-issue-and-pull-request-template...

beefsack 10y ago
Except this isn't GitHub specific.
code_research 10y ago
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!
Sir_Cmpwn 10y ago
How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.
- code_research 10y ago
  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 10y ago
    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?
    - 10y ago