From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 46109 invoked by alias); 26 Apr 2017 18:54:05 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 46088 invoked by uid 89); 26 Apr 2017 18:54:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=sk:contrib, project's, bless, central X-HELO: mail-wm0-f47.google.com Received: from mail-wm0-f47.google.com (HELO mail-wm0-f47.google.com) (74.125.82.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 26 Apr 2017 18:54:03 +0000 Received: by mail-wm0-f47.google.com with SMTP id u65so59099443wmu.1 for ; Wed, 26 Apr 2017 11:54:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=azSZ2ezVj3pOzx4dWcZcJPzyr+j9jNuN6UeDQhXAW/Q=; b=Ogcenhyrw8kgpF9sga8tsfFaRR2//PuagLc7/E94Ab21ENkt/3LKOiHgpdpURqhNIz gfbSTXk4zhSOGB71uTUpkV2lsjO5nAhi+rfUGzZrm+zH6tKQXbystbdFdXSgoiUDV0Sr rJKoQDhjV03X3GNeT6atj/DS9cqrJ8X9d+TJYHot3fF3yzfn9LY6kUt2PvDhH8HZq2dL Gubd+wPIVmOjI9WJwtfiej4Q+HbWTy2BAo+Zskp37//TO7qNWpGtJKa8Cwim8Stjk9zu H8yR+PEM5GCKzQ2UfZ82eofwoULnuBUFklRFgjWHRQPmoMxiZytaaLkfI3l7mKreYp6+ JLMg== X-Gm-Message-State: AN3rC/685cy9BX9sqooFWGm85Rcesm7mNcKdihX3Mr1Mfjma7If4loR0 B0WMi+k5uYEYCbia+Oy/oA== X-Received: by 10.28.5.72 with SMTP id 69mr2023563wmf.59.1493232843522; Wed, 26 Apr 2017 11:54:03 -0700 (PDT) Received: from [192.168.0.102] ([37.189.166.198]) by smtp.gmail.com with ESMTPSA id 7sm45609wrs.69.2017.04.26.11.54.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 11:54:02 -0700 (PDT) Subject: Re: updating bugzilla entries in sourceware.org To: Carlos O'Donell , "Jose E. Marchesi" References: <87h91b442l.fsf@gnu.org> <90431ae6-250a-cab9-88ff-1c39d2a55b4a@redhat.com> Cc: overseers@sourceware.org From: Pedro Alves Message-ID: <0a68400b-3c1f-f82d-b674-2d6eaa7c2c99@redhat.com> Date: Wed, 26 Apr 2017 18:54:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <90431ae6-250a-cab9-88ff-1c39d2a55b4a@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-q2/txt/msg00034.txt.bz2 On 04/26/2017 04:54 PM, Carlos O'Donell wrote: > On 04/26/2017 10:49 AM, Jose E. Marchesi wrote: >> >> Hi. I hack in binutils, GDB, and other projects hosted in sourceware >> with my work account jose.marchesi@oracle.com. >> >> I can add comments to bugzilla entries, but I can't modify the status >> (nor other fields) of issues reported by others. >> >> Is there a way I could do that? I need to be able to mark the issues I >> fix as fixed. > > Pedro, > > I've already fixed Jose's account, but this information is only on the > glibc side here: > > https://sourceware.org/glibc/wiki/Bugzilla%20Procedures Nice page! I may well steal/adapt it for GDB when I have a chance. > ~~~ > B0. The bug tracker is Bugzilla on sourceware.org. New users do not have > the editbugs group access which means that while they can create bugs > they cannot edit any aspects of the bug once created. This is done to > avoid spammers modifying existing bugs. If you need the ability to edit > bugs please request it on libc-alpha@sourceware.org or on IRC freenode > at #glibc, the bugzilla admins and senior members of the community can > grant this access once they know you're not a spammer. > ~~~ > > Do we need something similar on the gdb wiki? Yes, I think so. For now I put it on GDB's version of the contribution checklist: https://sourceware.org/gdb/wiki/ContributionChecklist I wonder whether we have somewhere a central place that includes information relevant to all products that the single bugzilla instance holds, not just glibc and gdb. (binutils, cygwin, elfutils, systemtap, etc.) Then all the different projects could reference it. There's the sourceware.org website of course, though that's not very convenient to edit. Does sourceware.org have a "sourceware" wiki? Or we could create such a page in one of the project's wikis and bless it as "cross project page". Anyway, just an idea that crossed my mind, there's not really that much information that I'm off hand thinking we'd put there. Thanks, Pedro Alves