making a workaround web page for bugs, in LTS release, not fixed
Marco Pallotta
marco.pallotta at gmail.com
Mon Jan 11 00:18:12 UTC 2010
Il giorno dom, 10/01/2010 alle 13.21 -0800, Ryein ha scritto:
> I like that idea. Integrate bug tracking and solutions together and
> into the OS. If you need more developers I am sure this would spring
> board into that if a good system existed for that. A simple tag
> system could easily link closely related topics together as well as
> solution validity. Solutions with the highest success rate posted by
> users would be shown first.
I think the problem is just how to find a valid system in order to
choose the right workaround.
I think a solution could be proposing, by the user that takes part in
the bug discussion, a workaround that has to be confirmed in order to be
posted in the "workaround for bugs" web page. This is good if we want to
provide a service with careful info (for example this could be mandatory
if web page is a sort of "official" web page maintained by Canonical).
So, to start working at the projects, we can think to restrict the
workarounds to those that have been confirmed by someone different to
the proposer and are related to confirmed bugs.
> I'm a programmer myself. Let me know if
> you need any help with this. Either web side or on the desktop.
>
> On Sun, Jan 10, 2010 at 6:12 AM, Marco Pallotta
> <marco.pallotta at gmail.com> wrote:
> > Il giorno ven, 08/01/2010 alle 11.58 -0600, C de-Avillez ha scritto:
> >> On 01/08/10 00:58, Marco Pallotta wrote:
> >> > 2010/1/7 Charlie Kravetz <cjk at teamcharliesangels.com>:
> >> >
> >> >>
> >> >> Ubuntu bugsquad already has a policy that workarounds should be
> >> >> identified and moved into the bug description. If that was happening,
> >> >> it should be easy to grab the section labeled "WORKAROUND:", right?
> >> >>
> >> >
> >> > Well,
> >> >
> >> > I saw not many of these labeled bugs. I think we whould start a
> >> > different process to identify a workaround solution for an issue that
> >> > will not be fixed.
> >> >
> >>
> >> Yes, they are used far less than ideal. Still, they should be used (and
> >> when I find a bug that is missing a workaround in the description, I add
> >> it in).
> >>
> >> But still, we could have a workarounds page in the Wiki (perhaps either
> >> *or*, or *also*, in answers.lp). There we could put the most important
> >> issues, and their workarounds. But not all, I think. There are some very
> >> technical issues that -- if you are hit with it, you most probably also
> >> know where to look for an asnwer.
> >
> > Well, also if there are technical issues I would expexct to find a
> > workaround in the "workaround for bugs" web page also for them if this
> > can help to save time to find a solution for an issue (also if the user
> > is not a newbie....at the end....time is time for everyone). However we
> > could also link the workaround with the specific bug from which it come
> > from so that any user (if he wanted to do it) can delve into the
> > question.
> >
> >
> >> It is unrealistic to expect all Ubuntu users to browse lp.net/ubuntu/bugs.
> >>
> >
> > I think the problem may be related to how link this workaround web page
> > into the desktop. If, for example, the user knows that, for any issue
> > found in any app, he has to simply click on a icon, to find a possibile
> > solution to it, he will do it instead of spend time to surfing into the
> > web for looking for a solution.
> >
> >
> > --
> > ==================================================
> > MARCO PALLOTTA
> >
> > e-mail: marco.pallotta at gmail.com
> >
> > CHAT:
> > msn #: pallotta at inwind.it
> > googletalk #: marco.pallotta at gmail.com
> > skype #: marco.pallotta
> >
> > Public GPG key: hkp://keyserver.ubuntu.com:11371
> > ==================================================
> >
> >
> > --
> > Ubuntu-devel-discuss mailing list
> > Ubuntu-devel-discuss at lists.ubuntu.com
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
> >
--
==================================================
MARCO PALLOTTA
e-mail: marco.pallotta at gmail.com
CHAT:
msn #: pallotta at inwind.it
googletalk #: marco.pallotta at gmail.com
skype #: marco.pallotta
Public GPG key: hkp://keyserver.ubuntu.com:11371
==================================================
More information about the Ubuntu-devel-discuss
mailing list