* Platonides [Wed, 16 Feb 2011 00:40:38 +0100]:
> MZMcBride wrote:
> > To this end, I filed a JIRA ticket with the Toolserver ops about
> getting the
> > Wikimedia Bugzilla database replicated with public views:
> > https://jira.toolserver.org/browse/TS-901
>
> The bugzilla db is on a different ma
MZMcBride wrote:
> To this end, I filed a JIRA ticket with the Toolserver ops about getting the
> Wikimedia Bugzilla database replicated with public views:
> https://jira.toolserver.org/browse/TS-901
The bugzilla db is on a different machine, it may not be worth it.
Leo wrote:
> One thing that b
> "BV" == Brion Vibber writes:
BV> Bugzilla actually ships with a default robots.txt that denies everything, we
BV> just never removed it. :)
Time to do the same for these lists.
(Psst, news.tcx.org.uk is now publishing them too, one more nail in the
coffin of security via obscurity.)
___
> With the impending Bugzilla 4 release, I would like to take some
> time in setting up the test instance to perhaps play with some of
> these options to see if we can tweak it into being more useful to
> everyone.
BZ4 is coming? Cool. You can't *imagine* how happy I'd be to help with
that proje
On Tue, Feb 15, 2011 at 10:44 AM, Leo wrote:
> One thing that bugged me a while:
> Why does the bz robots.txt deny any bots? I think having it indexed by google
> & co would'nt exactly make searching harder.
>
> Leo
Probably because historically you couldn't hide email addresses from
anon (non lo
On Tue, Feb 15, 2011 at 12:35 PM, Chad wrote:
> I mentioned this earlier today in IRC, but I'll mention it again here on-
> list. Take a look at the "Guided format"[0] for entering bugs. These
> templates can be customized, and I think we can use that as a starting
> point for creating nicer bug i
On Mon, Feb 14, 2011 at 4:44 PM, Leo wrote:
> One thing that bugged me a while:
> Why does the bz robots.txt deny any bots? I think having it indexed by
> google & co would'nt exactly make searching harder.
>
Bugzilla actually ships with a default robots.txt that denies everything, we
just never
On Mon, Feb 14, 2011 at 8:01 PM, MZMcBride wrote:
> I don't think there's going to be any magical set of configuration changes
> to make Bugzilla less horrible, but it's certainly worth a shot.
>
Neither do I, Bugzilla is always going to suck. Maybe we
can make it suck a little less though ;-)
>
Chad wrote:
> Part of this is because default configuration for Bugzilla *sucks*
> The workflow doesn't have to be so awful, and the fields don't
> have to be so scary. We've just never taken the time to tune it
> properly to make it nicer & easier to use. I'm not saying it's the
> best tool in the
I don't know about others, but I personally find the Bugzilla interface to
> be a complete pain-in-the-ass and just generally awful. Any search of the
> bugs in the system is often slow and filled with noise.
One thing that bugged me a while:
Why does the bz robots.txt deny any bots? I think havin
phoebe ayers wrote:
> There are many good ideas in this list. I have one small idea re:
> bugzilla -- is it possible to make browsing bugs more transparent
> (like a link on the sidebar)? I only just discovered that it's
> possible to look at bugs by category, component or keyword rather than
> sea
David Gerard wrote:
> On 14 February 2011 17:40, Jay Ashworth wrote:
>
>> If you don't know what version you're using, the bug report will be next
>> to useless, particularly if it's fire and forget.
>
> Any bug system has to capture everything possible, obviously.
Including private or semi-pri
On Mon, Feb 14, 2011 at 1:48 PM, Mark A. Hershberger
wrote:
> Bugzilla is a huge impediment to problem reporting for lay people. Even
> technically trained ones, like myself, look at the UI and groan. I want
> to do as much as possible to make problem reporting easier while still
> retaining som
phoebe ayers writes:
> Fascinating! I didn't know this existed either. To answer Mark's
> question, I'm interested in facilitating more user participation in
> bug-collecting. Using Bugzilla confuses the heck out of me, but mostly
> because I don't do it very often!
Bugzilla is a huge impediment
Diederik van Liere writes:
> I am not following this line of reasoning: how can adding guidance /
> instructions on how to write a good bug report turn people away?
I don't think it would … as long as it is simply guidance and not a
required field.
If we pre-fill the textarea, for example, with
On 14 February 2011 17:40, Jay Ashworth wrote:
> If you don't know what version you're using, the bug report will be next
> to useless, particularly if it's fire and forget.
Any bug system has to capture everything possible, obviously.
> If anyone on this thread hasn't already read Simon 'put
- Original Message -
> From: "Diederik van Liere"
> "If you know which version you are using or you have other information
> that you think might be helpful please add it as well.
> You can also describe the problem in your own words and not sticking
> to the abovementioned questions."
I
ers,
-- jra
- Original Message -
> From: "Diederik van Liere"
> To: "Wikimedia developers"
> Sent: Sunday, February 13, 2011 10:53:48 PM
> Subject: Re: [Wikitech-l] How users without programming skills can help
> Dear James, Amir and fellow wikimedia devs,
On Sun, Feb 13, 2011 at 5:28 PM, MZMcBride wrote:
> Mark A. Hershberger wrote:
>> Perhaps we could recruit some people from the he.wikipedia.org community
> to
>> take problems reported (via the localized interface?) and reproduce
> them or
>> act as a "translator" between developers and bug repor
* Daniel Friesen [Sun, 13 Feb 2011 20:16:53
-0800]:
> Actually our "users" could be anyone who reads Wikipedia and notices
> there's something wrong with what MediaWiki is doing or thinks there
is
> something about the ui we need to fix.
>
> They don't even have to be as advanced as a Firefox us
On 14 February 2011 04:16, Daniel Friesen wrote:
> Actually our "users" could be anyone who reads Wikipedia and notices
> there's something wrong with what MediaWiki is doing or thinks there is
> something about the ui we need to fix.
A few of these come into OTRS, specifically the "technical i
Maybe i am not expressing myself clear, i am not talking about adding
checkboxes, radiobuttons or pulldown menus,
I am saying that we could add the following text to the textarea field
which contains the actual bugreport:
"Please describe the steps to take to reproduce the problem:"
"What is the ex
2011/2/14 Diederik van Liere :
> I am not following this line of reasoning: how can adding guidance /
> instructions on how to write a good bug report turn people away?
It's very simple, really: a form with a lot of fields may turn people
away. I know that it turns me away. How many people are lik
I am not following this line of reasoning: how can adding guidance /
instructions on how to write a good bug report turn people away?
In a previous life, I have studied the factors that shorten the time
required to fix a big. Bugreports that contain steps to reproduce are a
significant predictor to
On Mon, Feb 14, 2011 at 2:46 AM, Diederik van Liere wrote:
> So maybe we can paste these 5 steps (or something similar) in the initial
> form used to file a bugreport.
>
> This would increase the quality of bugreports and make it easier for bug
> triaging.
>
Increase the quality perhaps, but also
That's exactly my point :)
Most Firefox bugreporters are ordinary users so if they are able to report a
bug then Mediawiki users can do it as well because they are basically the
same group of Internet users. And again, my suggestion is not hard, it's
about giving ordinary people a number of things
Actually our "users" could be anyone who reads Wikipedia and notices
there's something wrong with what MediaWiki is doing or thinks there is
something about the ui we need to fix.
They don't even have to be as advanced as a Firefox user... they could
be a random "human" who doesn't even know th
Dear James, Amir and fellow wikimedia devs,
I understand your concern and I am not suggesting that we should force a
user to enter all Bugzilla fields but add those 5 questions as a guideline
in the free-text form. Reporters can use it when they feel uncertain what
information we are looking for b
On 2/13/2011 8:46 PM, Diederik van Liere wrote:
> I think we can draw some inspiration from Mozilla's use of Bugzilla and
> particular the format they are encourage users when submitting a bugreport:
>
> 1) Steps to reproduce
> 2) Expected result
> 3) Actual result
> 4) Reproducible (by bugreporter
I think we can draw some inspiration from Mozilla's use of Bugzilla and
particular the format they are encourage users when submitting a bugreport:
1) Steps to reproduce
2) Expected result
3) Actual result
4) Reproducible (by bugreporter): always / sometimes
5) Version information, extensions inst
Mark A. Hershberger wrote:
> Perhaps we could recruit some people from the he.wikipedia.org community
to
> take problems reported (via the localized interface?) and reproduce
them or
> act as a "translator" between developers and bug reporters?
There is already some infrastructure for this kind of
On Sun, Feb 13, 2011 at 4:40 PM, Mark A. Hershberger wrote:
> "Amir E. Aharoni" writes:
> > he.wikipedia has a page for collecting bug reports, but since it's not
> > really structured, it's not really maintained.
>
> Perhaps we could recruit some people from the he.wikipedia.org community
> to ta
"Amir E. Aharoni" writes:
> he.wikipedia has a page for collecting bug reports, but since it's not
> really structured, it's not really maintained.
Perhaps we could recruit some people from the he.wikipedia.org community
to take problems reported (via the localized interface?) and reproduce
them
> 2011/2/14 Mark A. Hershberger :
>> Also, at some point I want to provide a better way — better than just
>> the complicated and confusing native Bugzilla interface — for collecting
>> bug reports.
Oh, and of course, as much i love Bugzilla (really!), it has a very
serious problem: It only works
2011/2/14 Mark A. Hershberger :
>
> I promise I don't have anything more to write today
Actually, i enjoyed reading this string of emails from The 'Meister.
> Also, at some point I want to provide a better way — better than just
> the complicated and confusing native Bugzilla interface — for coll
I promise I don't have anything more to write today, but MZ pointed out
I neglected to finish my thought here:
> Also, at some point I want to provide a better way — better than just
> the complicated and confusing native Bugzilla interface — for collecting
> bug reports. Having the input of a n
Diederik van Liere writes:
> I think one way that non technical people can help is by trying to
> replicate bugs, if they follow the steps as described in the bugreport
> Do you get the same malfunction or not. That would be a great help as
> it weeds out invalid bugreports
THIS! People familia
37 matches
Mail list logo
