Why do hapi projects have executable license, readme, etc?

[sholladay]

It's true. Many hapi projects seem to have had chmod +x applied to LICENSE, README.md, .travis.yml, maybe others.

Examples:

• wreck https://github.com/hapijs/wreck/blob/e37802b44f78002a9da94c850d31bf1dbfd42529/LICENSE
• boom https://github.com/hapijs/boom/blob/389633710d3f0eebc5d776ce18f89d2597e9720c/LICENSE
• hapi-auth-cookie https://github.com/hapijs/hapi-auth-cookie/blob/96e800acfd0b54c6f67f43fd61f07237b0ae127b/LICENSE

Having these permissions on files that aren't supposed to contain any code is concerning. Not to mention confusing. I was about to fix it in a hapi-auth-cookie PR, but then I saw it is not alone.

[Marsup]

I guess it's only because some people are working from windows.

[nlf]

Exactly. Windows is silly sometimes

[sholladay]

Oh Windows. My old friend.

Thanks!