| 1 |
José González Gómez schrieb: |
| 2 |
> |
| 3 |
> |
| 4 |
> 2006/9/6, Christian Spoo <mail@××××××××××××××.info |
| 5 |
> <mailto:mail@××××××××××××××.info>>: |
| 6 |
> |
| 7 |
> Tomek Lutelmowski schrieb: |
| 8 |
> > I think this is very good idea, even more, I think Gentoo should |
| 9 |
> have error |
| 10 |
> > reporting tool (let say qreport) which sends information like: |
| 11 |
> > |
| 12 |
> > - ebuild version |
| 13 |
> > - type of bug (compiling, stability, security, etc) |
| 14 |
> > - emerge --info |
| 15 |
> > - user comments |
| 16 |
> > |
| 17 |
> > to whatever.gentoo.org <http://whatever.gentoo.org>, which then |
| 18 |
> aggregates such data by ebuilds, platforms |
| 19 |
> > and bug types. People should be encouraged to use this tool |
| 20 |
> whetever possible |
| 21 |
> > (for ex. after emerge errors). I think such tool will colect data |
| 22 |
> much faster |
| 23 |
> > and reliable than wiki. |
| 24 |
> |
| 25 |
> IMHO, Bugzilla was introduced for this purpose. Why create another |
| 26 |
> system? You would have to maintain two independent databases. |
| 27 |
> |
| 28 |
> |
| 29 |
> Because bugzilla is thought to report *negative* experiences, but not |
| 30 |
> *positive* experiences. |
| 31 |
|
| 32 |
Bugzilla isn't only used to report just bugs. It is also used to publish |
| 33 |
new ebuilds which isn't a very *negative* experience I think. |
| 34 |
|
| 35 |
Nevertheless concerning the "error reporting tool" you want I'd stay |
| 36 |
with Bugzilla because it's already well-known and is tried and tested. |
| 37 |
|
| 38 |
Considering your proposal for a system for publishing positive |
| 39 |
experiences I think a wiki-like thing is enough. |
| 40 |
You could make a tabular listing of the package version, the version of |
| 41 |
gcc and the architecture and make the output of emerge --info and |
| 42 |
possibly some other information available using a popup. Just for |
| 43 |
keeping things readable. |
Archives