4 ms·

Didn't know about that, but was a little surprised by: > In every way that matters, Automattic is a reflection of Mullenweg (you could say he puts the “Matt” i

Didn't know about that, but was a little surprised by: > In every way that matters, Automattic is a reflection of Mullenweg (you could say he puts the “Matt” in Automattic). He started building web software because he wanted a place to store and share his photos; he’s a blogger to the core, and loves anything that aids in the free expression of ideas on the internet. He loves jazz, which is why WordPress releases are named for jazz musicians. Sure name your company whatever you like, but why should releases of an opensource project be named based on one person's taste in music?

coldtea 5y ago
>but why should releases of an opensource project be named based on one person's taste in music? Why not? As good as any other inspiration (like the naming themes admins use for hostnames in their LANs), and one man deciding helps stop the bikeshedding.
- karmakaze 5y ago
  The same argument could be made for any decision, hence the issue with the pattern.
  - coldtea 5y ago
    Obviously the same argument could NOT be made for any decision. Only for those decisions that have the qualities I mentioned on my argument (which are hardly all): "as good as any other" and "stops the bikeshedding". So, it should be decisions on things which don't affect much (the code-name of the release doesn't change anything, especially since people refer to it by version number, e.g. 5.8), and also trivial things prone to bikeshedding (similarly - nothing productive could ever come from a discussion about the naming scheme for releases).
    - karmakaze 5y ago
      Yes that's obvious, and I wasn't speaking to the pattern only being applied to bikeshedding cases but rather as a resolution mechanism in cases of uncertainty or disagreement in general. If it works to get things moving, what's to prevent it from being regularly used, especially if commonly used in other areas--could be a slippery slope if it's not already policy. It would be better not to have these concerns by not having one person's personal preferences dictate things that are small now, and leave room for doubt.

coldtea 5y ago

>but why should releases of an opensource project be named based on one person's taste in music? Why not? As good as any other inspiration (like the naming themes admins use for hostnames in their LANs), and one man deciding helps stop the bikeshedding.

karmakaze 5y ago
The same argument could be made for any decision, hence the issue with the pattern.
- coldtea 5y ago
  Obviously the same argument could NOT be made for any decision. Only for those decisions that have the qualities I mentioned on my argument (which are hardly all): "as good as any other" and "stops the bikeshedding". So, it should be decisions on things which don't affect much (the code-name of the release doesn't change anything, especially since people refer to it by version number, e.g. 5.8), and also trivial things prone to bikeshedding (similarly - nothing productive could ever come from a discussion about the naming scheme for releases).
  - karmakaze 5y ago
    Yes that's obvious, and I wasn't speaking to the pattern only being applied to bikeshedding cases but rather as a resolution mechanism in cases of uncertainty or disagreement in general. If it works to get things moving, what's to prevent it from being regularly used, especially if commonly used in other areas--could be a slippery slope if it's not already policy. It would be better not to have these concerns by not having one person's personal preferences dictate things that are small now, and leave room for doubt.