<story><title>The .meta directory: let&apos;s tidy things up</title><url>https://dotmeta.org/</url></story><parent_chain><item><author>paulhodge</author><text>I&amp;#x27;d suggest having them in a directory just called config&amp;#x2F;&lt;p&gt;On having it start with a dot: Why? Why would we pretend that these crucial files don&amp;#x27;t exist?&lt;p&gt;On having it named meta: These files aren&amp;#x27;t &amp;quot;about&amp;quot; the project or &amp;quot;above&amp;quot; the project, they ARE the project.</text></item></parent_chain><comment><author>sph</author><text>It&amp;#x27;s not configuration though. Specifically, it&amp;#x27;s not configuration of the project in question, it&amp;#x27;s configuration for third party accessories.&lt;p&gt;If I&amp;#x27;m writing an editor, I expect the config directory in the source code to hold the configuration for the editor, not .babelrc&lt;p&gt;meta is a much better name and they are &amp;quot;about&amp;quot; the project, not the project itself, so I disagree on that point. Though I agree it should not be hidden. I will start having a &amp;quot;meta&amp;quot; directory in my projects</text></comment>
<story><title>The .meta directory: let&apos;s tidy things up</title><url>https://dotmeta.org/</url></story><parent_chain><item><author>paulhodge</author><text>I&amp;#x27;d suggest having them in a directory just called config&amp;#x2F;&lt;p&gt;On having it start with a dot: Why? Why would we pretend that these crucial files don&amp;#x27;t exist?&lt;p&gt;On having it named meta: These files aren&amp;#x27;t &amp;quot;about&amp;quot; the project or &amp;quot;above&amp;quot; the project, they ARE the project.</text></item></parent_chain><comment><author>activiation</author><text>~&amp;#x2F;.config is already a thing</text></comment>