On Fri, Jul 12, 2013 at 3:57 AM, Jan Mercl wrote:
Recently issues (like ) are starting to appear on the project issue
tracker which refer to a no-public-access site for some unknown (to
the rest of us), yet presumably related to the issue information.
Sometimes the publicly visible part is obviously just a non sufficient
per se comment about the real, but non publicly accessible part (eg.
I'm sure no bad intent is behind this, still IMHO this practice is not
okay for an open source project (having an active community outside of
Google) and should be stopped.
Yes. Apologies for that. These are generated by the "Send feedback" link
you see on most pages on golang.org (though not the home page; see the
upper right corner of http://golang.org/doc/
for an example). This is the
same feedback mechanism that Gmail uses if you click the gear and choose
'Send feedback'. There's more information about what users see athttp://www.google.com/tools/feedback/intl/en/learnmore.html.
We are experimenting with this as a way to gather reports about problems
with the golang.org web site. So far it seems to be working: we've received
reports about and fixed a bunch of tiny things that people probably
wouldn't have bothered to file issues about (maybe even from people who
don't know where the issue tracker is) but that are still worth fixing.
Unfortunately, we have no way today to make the reports directly viewable
by people outside Google. I wish we did, but we don't. For now, the first
step for any such report must be that someone at Google has to view the
report and update the issue with a better summary. That would need to
happen no matter what, it's just that right now only people at Google can
do that part. I agree that this is not ideal for an open source project,
but it seems better than not getting these reports at all. It is possible
that we'll be able to make the raw feedback directly viewable later, but I
can't promise that.
Of course, we could instead send all the feedback issues to a non-public
email address or a non-public issue tracker, but since the usual response
is to turn them into public issues, it is easier if they are in the issue
tracker from the start. You can see examples of the conversions at:
Perhaps we can have the newly created and not yet fixed up issues be marked
with a label that we filter out of the usual results.
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/groups/opt_out.