I think we need to find a better way to get feedback. People's natural inclination is to complain if there is a problem, but to say nothing if the package works correctly. So I think that maintainers are probably made aware if a package has a problem. But if they get no feedback that could mean that everything is OK, or it could mean that no one is using the package. How to tell the difference?

What if fink was set up to automatically report successful compilations to the package maintainer? The e-mail could contain the package version, OS version, and list of installed packages. It could also report unsuccessful compilations to the maintainer, although this is probably not necessary. This would mean a flood of e-mails for maintainers with many popular packages, but they could set up some kind of filter in their e-mail to deal with it.

Granted that this approach doesn't cover the case where a package compiles but doesn't work properly, but you can't cover all cases.

Kevin Horton


At 08:52 12/12/2003 -0500, you wrote:
I probably should have posted that on -beginners or -users, then. I've been guilty of this: I'm perfectly happy installing from unstable source, so I forget to send feedback to the maintainer.

Now that I've gutted my system and started afresh with Panther, I'll try to set a good example for the rest of the users.

One thing that might help would be more "calls for feedback" from the maintainers--the reminder certainly helps me remember.
--
Alexander Hansen
Levitated Dipole Experiment
http://www.psfc.mit.edu/LDX
On Dec 12, 2003, at 5:28 AM, D. Höhn wrote:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Alexander K. Hansen wrote:
<snip>
|
| I, personally would like to see a faster turnover of packages that lots of
| people use from unstable to stable.
|

The problem you describe uo there depends soley on user feedback. If I
add package foo on the 13.

and I get 30 good reports on the 25. you might see me moving it to
stable on the 16.
This is how we handled it in teh past and it has proven to be a goo
strategy. Packages which have a high demand, which are used and where
there are no trouble reports get moved by the maintainer or in rare
cases by the core developers.

- -d



------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to