Re:Show HN: Dependency CI – Continuous testing for your depe...
by Sir_Cmpwn on Tuesday July 12, 2016 @08:46AM
(#12078544)
How about .meta? Hopefully we can encourage github to support this, too. Maybe .meta/github/ could be a thing, too.
[ Parent
| on HN ]
Re:Show HN: Dependency CI – Continuous testing for your depe...
by code_research on Tuesday July 12, 2016 @09:17AM
(#12078703)
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.
Re:Show HN: Dependency CI – Continuous testing for your depe...
by CiPHPerCoder on Tuesday July 12, 2016 @09:34AM
(#12078799)
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?
Re:Show HN: Dependency CI – Continuous testing for your depe...
by robbles on Tuesday July 12, 2016 @12:08PM
(#12080201)
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.
Re:Show HN: Dependency CI – Continuous testing for your depe...
by glenjamin on Tuesday July 12, 2016 @09:26AM
(#12078755)
`.config` is probably a decent choice, as ~/.config for per-user settings seems to be gradually gaining adoption.
Re:Show HN: Dependency CI – Continuous testing for your depe...
by jcassee on Tuesday July 12, 2016 @09:29AM
(#12078771)
Or .well-known? (analogous to https://tools.ietf.org/html/rfc5785)