Peter Busser wrote:
Here's an ideea -- chicken-setup should:
1) increment a web counter when somebody downloads an
egg (perhaps tracking of the IP for uniqueness
purposes). This way we can show no. of downloads next
to each egg.
This information can already be extracted from the web server log file.
2) report back to base when egg compilation fails.
It's a small start towards QA and it reduces the
burden on disgusted users to report broken eggs.
Easing the bug report procedure is of course a good idea. But it should
be with the user's consent, not automatical.
That was my 1st thought as well. However, it *is* an egg, essentially
an interaction with a remote server, a protocol of sorts. I think it's
reasonable to note that the protocol failed, without the user's
consent. Unreasonable is extracting a lot of diagnostic information
without the user's consent, like scanning their hard drive to learn
lotsa stuff etc. It's probably reasonable to extract some diagnostic
info, like whatever would be ordinarily within Chicken's purview.
I don't think asking for the user's consent is a good idea. They may
say "no" out of perceived fear, or because they had to get up to answer
the door. Instead, it should be decided what any would-be Chicken
developer would reasonably consent to, and report only that. Emphasis
on "would-be Chicken developer," who is by definition a DIY
can-compile-source-code developer. Not a technical illiterate afraid
of anything that might go on inside their computer, as would be the
case with consumer software.
Brandon Van Every