Andre Klapper aklap...@wikimedia.org wrote:
I don't know your specific usecase - maybe the shared saved search named
My CC'd Bugs might work (or not) which you could enable on
https://bugzilla.wikimedia.org/userprefs.cgi?tab=saved-searches (see
Marcin Cieslak wrote:
Andre Klapper aklap...@wikimedia.org wrote:
I don't know your specific usecase - maybe the shared saved search named
My CC'd Bugs might work (or not) which you could enable on
https://bugzilla.wikimedia.org/userprefs.cgi?tab=saved-searches (see
On Sat, Nov 9, 2013 at 6:51 PM, Nathan Larson
nathanlarson3...@gmail.com wrote:
Why not make assigning bugs work sort of like FlaggedRevs -- as a new user,
you can make changes, but the changes won't take effect until they're
reviewed and approved? After a bureaucrat sees that you're behaving
On Thu, 2013-11-07 at 12:06 -0500, C. Scott Ananian wrote:
I'm a little puzzled here: this whole discussion is because new owners want
to have the bug actually assigned to them, instead of just commenting, I'm
working on this in the bug?
Let's look at the github model -- there's no
On Sat, 2013-11-09 at 09:40 -0500, C. Scott Ananian wrote:
More agressive use of tagging (or something like it) would help here.
Tagging: For the records, Bugzilla offers
1) static global keywords in the Keywords field (see the list of
keywords at
On Sat, 2013-11-09 at 10:22 -0400, MZMcBride wrote:
I'll just reiterate what I said previously: it would be wonderful to do a
full evaluation/audit of the current Bugzilla inputs and figure out which
we can eliminate or make smarter (e.g., only display under certain
conditions).
Just to
On Sat, Nov 9, 2013 at 1:24 AM, Matthew Flaschen mflasc...@wikimedia.orgwrote:
Assignment is useful to me for multiple reasons, but the most important
are:
1. Marking things I'm definitely going to work on (while trying to avoid
cookie-licking). Importantly, I can unmark myself as assigned,
And to be clear, I'm not advocating turning off assignment entirely for all
projects and everyone. What I am advocating is that we (begin the process
of) 'turning off' a large number of unused bugzilla features for most
users, to reduce confusion and help encourage understanding of the workflow.
On Sat, Nov 9, 2013 at 9:40 AM, C. Scott Ananian canan...@wikimedia.orgwrote:
On Sat, Nov 9, 2013 at 1:24 AM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
Assignment is useful to me for multiple reasons, but the most important
are:
1. Marking things I'm definitely going to work on
C. Scott Ananian wrote:
And to be clear, I'm not advocating turning off assignment entirely for
all projects and everyone. What I am advocating is that we (begin the
process of) 'turning off' a large number of unused bugzilla features for
most users, to reduce confusion and help encourage
I don't think assignment is the main usecase for editbugs. Things like
marking as duplicate are.
Requiring people to ask is a barrier (especially when it's essentially
unknown who to ask). I wouldn't be surprised if we lose otherwise useful
contributors because they are too shy to ask or just
Why not make assigning bugs work sort of like FlaggedRevs -- as a new user,
you can make changes, but the changes won't take effect until they're
reviewed and approved? After a bureaucrat sees that you're behaving
responsibly, or after you've made a certain number of changes that have
been
On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote:
In order to get somewhere with this discussion, it would be useful to
know the current practice of other free software projects, using
Bugzilla or not. As a newcomer, can I assign bugs to myself in GNOME,
KDE, Ubuntu, Debian... etc?
In case
On Fri, Nov 8, 2013 at 6:52 AM, Andre Klapper aklap...@wikimedia.orgwrote:
On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote:
In order to get somewhere with this discussion, it would be useful to
know the current practice of other free software projects, using
Bugzilla or not. As a
Again, as far as I'm concerned, we're solving a non-problem. Yes, in
theory it would be nice if everyone easily got all permissions to
everything. But bugzilla is not set up with the antivandal features needed
to make that work. Instead, we should aim to make it possible for
newcomers to easily
On Thu, Nov 7, 2013 at 9:06 AM, C. Scott Ananian canan...@wikimedia.orgwrote:
I'm a little puzzled here: this whole discussion is because new owners want
to have the bug actually assigned to them, instead of just commenting, I'm
working on this in the bug?
Let's look at the github model --
On Fri, Nov 8, 2013 at 2:09 PM, Steven Walling steven.wall...@gmail.comwrote:
On Thu, Nov 7, 2013 at 9:06 AM, C. Scott Ananian canan...@wikimedia.org
wrote:
I'm a little puzzled here: this whole discussion is because new owners
want
to have the bug actually assigned to them, instead of
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Maybe Dan Garry could chime in here as well.
___
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling steven.wall...@gmail.comwrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Maybe Dan
On Fri, Nov 8, 2013 at 2:31 PM, Chad innocentkil...@gmail.com wrote:
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling
steven.wall...@gmail.comwrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes
On Fri, Nov 8, 2013 at 2:14 PM, Steven Walling steven.wall...@gmail.com wrote:
On Fri, Nov 8, 2013 at 2:12 PM, Chad innocentkil...@gmail.com wrote:
Not all teams have drank the Mingle Kool-Aid yet ;-)
That includes mine. :) Chad: does Platform really depend on bug assignment?
Yes.
Rob
On 11/08/2013 11:09 PM, Steven Walling wrote:
I would be okay just turning off assignment.
I don't support turning off assignment. A large number of MediaWiki
projects use only Bugzilla (which is also the only open source tracker
the WMF uses). Even for stuff WMF engineers work on, there
On 11/06/2013 04:54 PM, Chad wrote:
How about we make editbugs self-granting? That is, if you've got editbugs
you can give it to others (like we did with Coder a few years ago). It works
pretty well, scales infinitely, and tends to protect itself against abuse.
I agree with the others that the
On 11/06/2013 04:24 PM, MZMcBride wrote:
Quim Gil wrote:
On 11/06/2013 07:24 AM, Petr Bena wrote:
So that's why suddenly I started receiving these email requests :D
No, you are getting suddenly these emails from a group of students at
http://foss.amrita.ac.in because a mentor told them to do
On Wed, Nov 6, 2013 at 10:04 PM, Rob Lanphier ro...@wikimedia.org wrote:
I like the idea of giving everyone who has editbugs the right to give
other people the editbugs permission. That's certainly worth a try
assuming it's possible to configure.
I want to underscore this again. I think
On Thu, 07 Nov 2013 17:33:14 +0100, Chad innocentkil...@gmail.com wrote:
On Wed, Nov 6, 2013 at 10:04 PM, Rob Lanphier ro...@wikimedia.org wrote:
I like the idea of giving everyone who has editbugs the right to give
other people the editbugs permission. That's certainly worth a try
assuming
On 07/11/13 16:28, Quim Gil wrote:
The issue is the extra step for newcomers vs the risk of many extra
steps for a few etablished contributors if someone decides to abuse the
feature, as it happened in the past. And my point is that I personally
don't believe that such barrier is diminishing the
I'm a little puzzled here: this whole discussion is because new owners want
to have the bug actually assigned to them, instead of just commenting, I'm
working on this in the bug?
Let's look at the github model -- there's no assignment at all. I just
file a bug, maybe make some comments on it to
Let's look at the github model -- there's no assignment at all. I just
file a bug, maybe make some comments on it to say I'm working on it, and
some time later I submit a pull request referencing the bug and saying, I
fixed it. That seems to work fine for collaboration, and offers no
On Thu, 2013-11-07 at 08:33 -0800, Chad wrote:
On Wed, Nov 6, 2013 at 10:04 PM, Rob Lanphier ro...@wikimedia.org wrote:
I like the idea of giving everyone who has editbugs the right to give
other people the editbugs permission. That's certainly worth a try
assuming it's possible to
On Nov 7, 2013 6:27 PM, Andre Klapper aklap...@wikimedia.org wrote:
For the records: Currently 14744 Wikimedia Bugzilla users have editbugs
permissions (so this is something to do via an SQL command instead of me
clicking myself to death in Bugzilla's web interface).
I also generally support
C. Scott Ananian wrote:
Maybe we should be turning off bugzilla features instead of trying to
'fix' them. The whole 'file a bug in bugzilla' process is already far too
complicated with a dozen fields which are either irrelevant or just
confusing to newcomers. Can we just hide all this cruft
On Thu, Nov 7, 2013 at 6:02 PM, Jeremy Baron jer...@tuxmachine.com wrote:
Also, what is the current method for marking bad users and making sure they
don't get promoted? Like CentralAuth's lock.
Spammers can have their account set to disabled by any BZ admin.
They'll get a disabled message
Hi.
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the capabilities of new users as a knee-jerk response to prior
Bugzilla-related vandalism. There are further details at
https://bugzilla.wikimedia.org/40497.
Increasingly new users are making manual requests to be
So that's why suddenly I started receiving these email requests :D
On Wed, Nov 6, 2013 at 2:24 PM, MZMcBride z...@mzmcbride.com wrote:
Hi.
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the capabilities of new users as a knee-jerk response to prior
On 6 November 2013 13:24, MZMcBride z...@mzmcbride.com wrote:
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the capabilities of new users as a knee-jerk response to prior
Bugzilla-related vandalism. There are further details at
On Wed, Nov 6, 2013 at 5:24 AM, MZMcBride z...@mzmcbride.com wrote:
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the capabilities of new users as a knee-jerk response to prior
Bugzilla-related vandalism. There are further details at
I don't want anything to stand in the way of good users
Perhaps something similar to autoconfirmed as Thehelpfulone suggested, i.e.
X total edits across all Wikimedia projects (or on a single Wikimedia
project), and account was created Y days ago. There are details to work
through with that (e.g.
Pre-emptive send wins again. That was meant to be I don't want anything to
stand in the way of good users filing bug reports, but we need to be aware
of the previous issues that led to the current situation.
Dan
On 6 November 2013 15:45, Dan Garry dga...@wikimedia.org wrote:
I don't want
I like the idea of more liberally (and perhaps automatically) giving out
the right. As it stands, I'm not even sure who can give out editbugs other
than Andre. In any case I understand it to be a very small number who can.
For a start it would be nice if pretty much any active developer could.
On Wed, Nov 6, 2013 at 7:38 AM, Rob Lanphier ro...@wikimedia.org wrote:
On Wed, Nov 6, 2013 at 5:24 AM, MZMcBride z...@mzmcbride.com wrote:
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the capabilities of new users as a knee-jerk response to prior
On Wed, Nov 6, 2013 at 7:54 AM, Chad innocentkil...@gmail.com wrote:
How about we make editbugs self-granting? That is, if you've got editbugs
you can give it to others (like we did with Coder a few years ago). It
works
pretty well, scales infinitely, and tends to protect itself against
In general: I am happy to change Bugzilla settings, whatever is agreed
on in the end.
On Wed, 2013-11-06 at 07:38 -0800, Rob Lanphier wrote:
On Wed, Nov 6, 2013 at 5:24 AM, MZMcBride z...@mzmcbride.com wrote:
Our Bugzilla installation at https://bugs.wikimedia.org/ currently
restricts the
On 11/06/2013 11:16 AM, Andre Klapper wrote:
Bugzilla does not allow centrally reverting all actions by a specific
person: https://bugzilla.mozilla.org/show_bug.cgi?id=735213
Luckily, though, it does track actions by user. As a result, I was able
to revert the vandalism. But it does seem like
On 11/06/2013 07:24 AM, Petr Bena wrote:
So that's why suddenly I started receiving these email requests :D
No, you are getting suddenly these emails from a group of students at
http://foss.amrita.ac.in because a mentor told them to do so. We have
explained the right process to them (asking in
Rob Lanphier wrote:
We tried reversing it several times, and each time were rewarded with an
arduous cleanup task. We gave up trying after months. So, calling it
kneejerk is simply wrong. We had a determined vandal who may still be
among us, and will likely exploit whatever loophole we open up.
Quim Gil wrote:
On 11/06/2013 07:24 AM, Petr Bena wrote:
So that's why suddenly I started receiving these email requests :D
No, you are getting suddenly these emails from a group of students at
http://foss.amrita.ac.in because a mentor told them to do so. We have
explained the right process to
On Wed, Nov 6, 2013 at 4:18 PM, MZMcBride z...@mzmcbride.com wrote:
Rob Lanphier wrote:
We can certainly do something different than what we're doing, though. It
should be easy to get editbugs; just not so easy that a vandal can get it.
Okay, let's. I proposed reverting the settings change.
48 matches
Mail list logo
