gather more supporters

[ssbarnea]

Promoting use .config on so many tools does not make sense if there is only one dude behind the initiative. It makes sense to set a goal of gathering supporters first, before going for other promotion methods.

If we can get tool maintainers among early supporters even better as the best way to support this kind of standardization is to add support to your own tool first.

How can you help?

• If you maintain a project that has a repository level config, add support for .config or at least put a comment here stating that you plan do it.
• Do not directly propose adoption of .config to mainstream projects yet, timing is essential and you don't want to aim too high from start.
• Check with tool maintainers first before you even add a ticket, do it only if they show support.
• One way to declare your support for this adoption is to add supports-dot-config label to your project on github, as this will prove to be an easier way to list which projects added support or plan to do it.

[ssbarnea]

• Lobby for .config/ shannonmoeller/find-config#2
• the creeping scourge of tooling config files in project root directories nodejs/tooling#79
• https://news.ycombinator.com/item?id=24066748 (2020)
• https://www.reddit.com/r/linux/comments/4xt3af/can_we_put_an_end_to_the_old_configuration_file/ (2017) archived

[pawamoy]

About promoting the idea:

• supporters could add a dot-config GitHub topic to their repository
• supporters could add a dot-config badge to their README

[ssbarnea]

@pawamoy There is a problem with dot-config, topic as it is already used by many to mark the fact that these repos contain .config files, not really the same thing as this idea.

[pawamoy]

Ah, I didn't actually check the existing topics. Something similar but not used yet would be fine too :)

[ssbarnea]

That is why I started using https://github.com/topics/supports-dot-config topic.