http://www.freebsd.org/cgi/getmsg.cgi?fetch=506636+517178+/u...
http://en.wikipedia.org/wiki/Color_of_the_bikeshed
http://catb.org/jargon/html/B/bikeshedding.html
http://www.urbandictionary.com/define.php?term=bikeshedding
All of these definitions require the issue to be of marginal benefit to the overall problem. The observation that people feel the need to contribute their opinion on matters they feel they know about is why bikeshedding happens, but it's not bikeshedding itself.
The more important point was that you can't call someone wrong when they're using the actual, original definition correctly, which I was (the link I included was how the term entered the geek lexicon).
But. All of this is a digression. The entire reason I said I don't think this is bikeshedding is because I think there's value in discussing why join is a member of strings and not sequences in Python. Understanding this point helps in understanding Python's design.