On Fri, Apr 3, 2009 at 8:58 AM, Carlos E. R.
Telling a user to report upstream should be the last resort. It is certainly daunting for me!
I think it is more appropriate for the maintainer to report upstream with CC to the user to add additional data the people upstream may require, because the maintainer should be accustomed to the requirements upstream and knows what they want or like.
agreed. the vast majority of times (there's been exceptions, to be sure) i've tried communications @ upstream, i've been _completely_ ignored. not a comment. occassionally i get a "screamer" @ upstream IRC, to add to the overall fun ... subsequently heading back downstream, to *SUSE bugzilla, getting a developer involved, and having _them_ re-ask (admittedly, with greater "geek-speak-clarity", all due respect intended ...) the question @ upstream _does_ get results. i'd suggest that if/until that becomes a minority case, that there should be some recognition that user->upstream may not be the best recourse for getting problems solved that benfit the project.
Maybe because there are gazillions of other. more important, priority problems to fix ?
Even filesystem crash or data loss? Isn't that worth a comment in many months?
Carlos' question is, imho, quite valid -- and the circumstance is repeatedly demonstrable. isn't one of the points arising in this thread the issue that if there ARE judged to be "gazillions of other. more important, priority problems to fix" that at the very least it might be nice for a user to know, via a comment in said submitted bug, that that determination has been made? ideally, perhaps even including the user in that determination discussion? -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org