On Wed, 27 Feb 2013 22:30:38 +0100 Peter Stuge <[email protected]> wrote:
> Tom Wijsman wrote: > > > > We could create a new repo at our Github and start developing. > > > > > > Don't start developing, plz work on bugs instead. > > > > Then who will develop useful tools to handle bugs more efficiently? > > Don't get me wrong: I am not hating on useful tools! That's not an answer to my question. > I am saying that working on tools is orthogonal to working on open > bugs. And I am saying that working on tools that help you work on open bugs is not orthogonal to fixing open bugs, it helps you fix them efficiently. > > his sole two bugs > > Is there a rule in Gentoo that forbids a dev to fix a bug assigned to > someone else? That would make absolutely no sense to me. > > No wonder then, that there are several bugs with no activity for > months after I have committed fixed ebuilds to my overlay and > mentioned that in a comment. Yes, one shall not commit on packages other developers maintain without the permission to do such thing. But let's assume the horribly "attaching a patch" approach (save two files, compare them, bla...)... Can you write me a tool that shows these kinds of bugs, easily submit patches to them and follow up on whether the developer commits them or retires at one or another point? I don't do any of this for my bugs. I could state that working on bugs assigned to someone else is orthogonal to fixing your own bugs. > He has become a developer so why would he not be able to take > neccessary action to close bugs, even if they haven't been assigned > to him? Because it isn't as simple as you make it seem like, as stated above. > - But Peter, you say, don't you see - that would lead to more fixed > bugs! > > Orly? How is that bad? Y u no serious? U mad? > (I'm obviously assuming that all developers (but not infra) are > equally competent, since that's the model taught by recruitment.) Competence is irrelevant to this discussion, competency is to be assumed. Though, since you want to discuss this; note that with the right tools incompetent developers can become more competent, instead of having no clue where to start they can efficiently start on something right away and finish it in a timely matter. > > short term > .. > > long term > > Yes, life is tradeoff. In my experience development of tools is > rather a long term thing, while a day of working on bugs is more > short term. A day short, to be exact. :) What experience are you even talking about? Did you write a tool that handles upon bugs, build logs or something else that applies to the daily Gentoo Dev process? > If there are numerous unactionable bugs then perhaps skip them on > that day, and work on shiny bulk processing tools the next day. So, we need another tool to mark and bulk process unactionable bugs! Or at least plan and write the searches for our lovely Bugzilla to do so, oh, and also CC a ton of people with this madness while we're at it. > Just my 2. But never mind. I guess I'm not supposed to participate > in the bugday anyway. Good for me! :) It's only a day short. The other six days are free to work on tools... With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : [email protected] GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
