Propose your solution
Attachments
No attachments.
Duplicates
Comments
|
Shady3D
wrote on the 23 Nov 09 at 06:52
|
|
|
|
its great but these workarounds should be approved by Ubuntu team, to make sure that these scripts don't harm the users, but this is great idea.
|
|
Ssdg
wrote on the 23 Nov 09 at 10:02
|
|
|
|
Interesting, but what's the point, the time to issue a workaround will be taken on the time to issue a real patch... so it will slow down overall problems resolutions.
|
|
shinger
wrote on the 23 Nov 09 at 15:23
|
|
|
|
@Ssdg Well some problems arent fixed for a long time. So a workaround is kind of nice to have. And a agree with andrew and shady about Canonical approving them before putting it online for users to download.
|
|
doobiest
wrote on the 26 Nov 09 at 20:02
|
|
|
|
Looks like I may have posted a duplicate. Although I think the detail of mine helps capture the need of this for novice users, please see Idea #22667 and tell me what you think
|
|
doobiest
wrote on the 26 Nov 09 at 20:03
|
|
|
my rationale was:
Think about who bugs affect the most and who it leaves the most helpless.. Novice users, people who aren't commandline savvy.
Say there's a bug which prevents your sound card from working. For the average to experienced user it's annoying but manageable. We can drop to a shell, type in some magic and get it to work. If it breaks again, continually repeat the steps until the bug has been fixed in a later build. No big deal.
For the Novice user however this is a big deal. Not only are the ill-equipped with the means to work around the issue, the have to wait until the bug is fixed in a new build, and the pray they know to update the software.
This can equate to weeks and week of having a crippled OS. Its a poor customer experience and it's going to make them want to switch back to their old copy of XP and give up hope.
I feel that this could be easily dealt with and greatly increase the end user experience with a very simple application.
|
|
|
I don't think it makes sense to make workarounds available in this way. The same people that want the ease-of-use of automatic solution distribution are the ones who will want the ease-of-use of thoroughly tested solutions, which obviously takes time. And developer's time is better spent fixing the actual issue than managing workarounds.
I read this request as a call to reduce solution turnaround time for problems with known solutions. I believe Canonical is aware of this problem and is working to address it by streamlining communication with upstream developers.
Other than that, the only thing I see is a desire to avoid regressions. I feel that is best accomplished by releasing the best-tested versions, especially ones that have limited new features.
|
|
dhilvert
wrote on the 30 Nov 09 at 18:54
|
|
|
@Dataphile Perhaps the primary motivation for workarounds is that not everyone's hardware is the same. If a new user has a network card that doesn't work, and five other users with the same card have successfully tested a proposed work-around, it might make sense to make that user's experience a bit easier by providing this information directly, and by offering to implement a fix in a tested, automated manner. This same fix might not make sense for all Ubuntu users, and might not ultimately make sense for upstream to adopt, but users should have a choice in this area, and implementing workarounds and fixes in a common format (I would suggest as .deb packages) not only makes their implementation more reliable from user to user, but also allows for better compatibility with long-term development than does manual intervention.
Not only would this benefit novice users, but also advanced users, since the latter would not need to mentally account for workarounds if the package manager is doing it for them.
(And package maintainers, in looking at what suggestions to send upstream, could report on the efficacy of fixes in a controlled way, since automation would reduce user error.)
|
Post your comment
|
