"Definitely not, it's a potential security risk for starters"
Since the codebase isn't obfuscated, this is really a non argument. People who are wanting to be malicious need only get the free version and check for holes.
Saying its going to deter sales, how do you feel about EESE then? That has some of the best rankings on google and there is no stopping it now.
"it's already a hard enough sell against the likes of the other CMS platforms on the market"
Why is it already hard to sell? Just the price? Is it because its a line item? Because at $300 its roughly 2-3 normal billable hours at most shops. I know many people don't even list the price and just roll it into the total. I understand that laymen love free stuff, but even with the bug tracker public, tell them to google 'wordpress hacked' vs 'ExpressionEngine hacked'. The results are _wildly_ different.
Definitely not, it's a potential security risk for starters - yes someone with nefarious intentions can login to view but having it non public reduces the risk of issues being scraped to who knows where. Come to think of it, have you seen any CMS platform that allows full indexing of their bug tracking systems?
If they were indexed you also have the problem of bug submitters posting URLs to live sites, or dev server addresses which shouldn't be made public. Then you have code snippets and a whole ton of stuff that someone could misuse.
Personally I've never had any problem, i have the bug tracker bookmarked so a click and quick search often reveals what I'm looking for without fuss.
Perhaps there's a opportunity to do some reverse thinking here. Why not extend the bug tracker to link to external solutions/fixes/help/workarounds and/or provide a quick way of searching the web from a bug page with relevent keywords? That way bug tracking data is kept safe while giving the community an avenue to explore resolutions to problems, of course this would require Ellislab to modify the bug tracker to suit.
For what it's worth, bugs were indexed by Google for years until the redesign of the site.
I was initially in the Yes camp. After reading Carl's comment however, I realised the implications could be more detrimental than the gains therefor I am voting No.
That said, I do think there needs to be more awareness to remind developers to check the bug tracker when trying to solve an issue (I know I am guilty of this). Maybe some Twitter blasts similar to what is currently being done with EESE. Maybe putting a reminder up on EESE (if it's possible).
I'm afraid I'm in the No camp on this one.... it's already a hard enough sell against the likes of the other CMS platforms on the market, but from my clients point of view when they google ExpressionEngine - they get lots of positives and sites/info/blogs about ExpressionEngine which further bolster/support my argument.
If the bugtrack list were in publicly listed in google, it would make our lives as sales people (ignore the developer aspect for the time being) that much more difficult. We all know that Google is the elephant who never forgets - so regardless of the fact that there may only be *x* number of bugs, over a period of time, Google is going to continue to index and all of a sudden a search will return an exponential number of bugs regardless of their state.
Anyway, just my opinion.... I think that if the bugtrack is made more accurate in its searching methodology (hell, just give Low $50 and use that - it's pretty damn awesome), then I think it would answer the problem - but as for putting them into Google to be searched by anyone? Not for me.
I think only officially "Accepted" bugs (and maybe those labeled "See Comments") ought to be publicly searchable. The other submitted ones are often just developer oversight. Showing those might make EE look like it has more bugs than it really does, if appearance is a concern at all.
Yes, as many of my clients that I support have an active EE install .
This is a huge no-brainer. I don't have a problem with registering in order to create or comment on a bug, but for heaven's sake, indexing the bug tracker will reduce support requests, both for EL and for the community on Stack Exchange & Twitter, and save everybody a heck of a lot of time.
I absolutely want to see the EE bug report indexed by search engines. When I run into a problem my first destination is always Google. Google knows everything! I trust the results and have ultimate control using their search operators. Moving the EE bug report behind a login created a barrier between me and data relevant to doing my daily job. As a long-time customer, I vote 100% to free the bugs!