I find EditorConfig very useful for company where I work to enforce coding style since company had no policy on coding style (and everybody wan't their own coding style).
Bit it was bit tedious experience, and still can't perform some actions (even not sure does specification exists or not). Find it hard to locate any order in this specification(s) for .editorconfig files. Had to look at multiple places/sources to gather information, or just try-by-your-self to see does specification exist. I would suggest forming EditorConfig_suggestions, EditorConfig_workgroup, and similar groups. Then form the EditorConfig draft specification published on GitHub with time table itinerary of the EditorConfig work-group. Common work-group process: take suggestion to work-group and vote suggestion (open community voting system would be appreciated) for next draft, or return for more workout (better language). Accepted suggestion should be then put in next published version specified by work-group itinerary. And officially publish specific versions of EditorConfig standard (yearly vYYYY or quarterly vYYYY[A-D]) on GitHub or similar versioning control site. Think some more complete "standard" would be much more appreciated by community. thanks for reading -- You received this message because you are subscribed to the Google Groups "EditorConfig" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/editorconfig/8dec8c3b-abdd-421c-95a1-8c2e965bced5n%40googlegroups.com.
