Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

On 09/21/16 22:29, Kinney, Michael D wrote:
> Hello,
> 
> The domain name for the Tianocore Bugzilla server has been updated.
> 
> Please use the following link to access the server and for issue
> references in commit emails.
> 
>   https://bugzilla.tianocore.org
> 
> Please let me know if there are any issues using this link.

Thank you for the update; it seems to work well for me!
Laszlo

>> -Original Message-
>> From: Laszlo Ersek [mailto:ler...@redhat.com]
>> Sent: Friday, September 2, 2016 3:48 AM
>> To: Kinney, Michael D <michael.d.kin...@intel.com>
>> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>; Justen, Jordan L
>> <jordan.l.jus...@intel.com>
>> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
>>
>> Hi Mike,
>>
>> On 07/06/16 20:52, Kinney, Michael D wrote:
>>> Laszlo,
>>>
>>> Good timing.  I was going to send a status update today.
>>>
>>> We are working diligently to get Bugzilla online for all bugs.  There
>>> are a few logistics that are still being worked this week related to
>>> an email list for bug state changes that Jordan is helping with and
>>> setting up tianocore domain name for the Bugzilla server.
>>
>> May I ask if / how the tianocore domain name for the Bugzilla server is
>> coming along?
>>
>> Thanks!
>> Laszlo

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Kinney, Michael D]

Hello,

The domain name for the Tianocore Bugzilla server has been updated.

Please use the following link to access the server and for issue
references in commit emails.

  https://bugzilla.tianocore.org

Please let me know if there are any issues using this link.

Mike

> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: Friday, September 2, 2016 3:48 AM
> To: Kinney, Michael D <michael.d.kin...@intel.com>
> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>; Justen, Jordan L
> <jordan.l.jus...@intel.com>
> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
> 
> Hi Mike,
> 
> On 07/06/16 20:52, Kinney, Michael D wrote:
> > Laszlo,
> >
> > Good timing.  I was going to send a status update today.
> >
> > We are working diligently to get Bugzilla online for all bugs.  There
> > are a few logistics that are still being worked this week related to
> > an email list for bug state changes that Jordan is helping with and
> > setting up tianocore domain name for the Bugzilla server.
> 
> May I ask if / how the tianocore domain name for the Bugzilla server is
> coming along?
> 
> Thanks!
> Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

Hi Mike,

On 07/06/16 20:52, Kinney, Michael D wrote:
> Laszlo,
> 
> Good timing.  I was going to send a status update today.
> 
> We are working diligently to get Bugzilla online for all bugs.  There 
> are a few logistics that are still being worked this week related to 
> an email list for bug state changes that Jordan is helping with and 
> setting up tianocore domain name for the Bugzilla server.

May I ask if / how the tianocore domain name for the Bugzilla server is
coming along?

Thanks!
Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

On 07/19/16 21:57, Kinney, Michael D wrote:

> We have edk2-devel mailing list today for patch submissions/review and
> design/implementation discussions.
> 
> The commit messages in the future should include a link to the Bugzilla
> issue(s) the patch addresses.

I agree.

> If there are lively discussion on edk2-devel on root causing a bug
> or discussions on where and how the bug should be fixed in code, then
> the Bugzilla entry can include gmane links to those edk2-devel
> threads.

I agree.

Furthermore, I suggest:

- whenever a patch series is posted to edk2-devel, for (partly or
completely) fixing a bug, the cover letter of that series be linked in
the BZ,
- when patches are committed, the commit range also be noted on the BZ.

When someone tries to look over the bug from the distance of a month or
so, they can easily find all versions of the patch series, with the
review comments, and the commits too.

Thanks!
Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

On 07/19/16 19:59, Michael Zimmermann wrote:
> how will this work side-by-side with the mailing list?
> It kinda sounds like a mailing list replacement, and you probably don't
> want to have separate mailing list topics and bugzilla reports about the
> same thing.

Bugzilla and mailing list work very well together.

A bugzilla entry is (should be) focused on a specific bug or feature,
for a specific product, component, package. Some discussion can and
should occur in it, attachments can be uploaded, etc., but all comments
have to pertain to the bug or feature in question. The BZ entry also
carries a whole lot of metadata, which is great for queries (the
simplest query is likely "what am I responsible for at the moment").

The mailing list is much more free-form. It frequently happens that the
discussion initially takes place on the list, and when a bug clearly
emerges, a BZ entry is opened. The mailing list supports multi-party
discussion much better than Bugzilla, through the threading of emails.

As Mike mentions, patches are submitted to the list. While Bugzilla can
accept patch attachments, display them as colorized diffs, and even
track some level of review for them, it's vastly inferior to reviews
done on the mailing list.

... I can't produce more (or any) "formal" guidelines for choosing
between Bugzilla and the mailing list, but in my experience they become
clear with use.

Thanks
Laszlo

> On Tue, Jul 19, 2016 at 7:24 PM, Kinney, Michael D
> <michael.d.kin...@intel.com <mailto:michael.d.kin...@intel.com>> wrote:
> 
> Laszlo,
> 
> Thanks for the feedback.  A few responses embedded below.
> 
> I agree there are many ways to organize this content inside Bugzilla
> and that we can refine the products/components/fields as we use it.
> 
> Mike
> 
> > -Original Message-
> > From: Laszlo Ersek [mailto:ler...@redhat.com <mailto:ler...@redhat.com>]
> > Sent: Wednesday, July 6, 2016 12:53 PM
> > To: Kinney, Michael D <michael.d.kin...@intel.com 
> <mailto:michael.d.kin...@intel.com>>
> > Cc: edk2-devel@lists.01.org <mailto:edk2-devel@lists.01.org>
>     <edk2-de...@ml01.01.org <mailto:edk2-de...@ml01.01.org>>
> > Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative 
> events
> >
> > On 07/06/16 20:52, Kinney, Michael D wrote:
> > > Laszlo,
> > >
> > > Good timing.  I was going to send a status update today.
> > >
> > > We are working diligently to get Bugzilla online for all bugs.  There
> > > are a few logistics that are still being worked this week related to
> > > an email list for bug state changes that Jordan is helping with and
> > > setting up tianocore domain name for the Bugzilla server.
> > >
> > > I see many developers have created accounts on the Bugzilla server
> > > that is in a test mode right now.  Thank you to everyone who has done
> > > that already!  If you have not done so, please go to the following
> > > link and create an account.
> > >
> > > https://tianocore.acgmultimedia.com
> > >
> > > Also, please enter some sample bugs and feature requests and review
> > > the fields.  Please send feedback if you would like to see any changes
> > > to the fields.
> > >
> > > I will send updates as tasks are completed as I also want to see us
> > > move to Bugzilla ASAP.  This is my highest priority task right now.
> >
> > I skimmed the "new bug page" (with the advanced fields shown) for
> > TestProduct -- from a cursory look, it's fine.
> >
> > Other than that, why is "Feature Requests" a separate product from "EDK2
> > - Main Trunk"? Same for "UEFI Security Issues". I think feature requests
> > and security issues should not be separate products. They should be
> > orthogonal to any product. In the RH Bugzilla at least, these "traits"
> > are represented by Keywords.
> 
> Security issues are in a separate product so we can associate then with
> the "infosec" group for evaluation in the UNCONFIRMED state and support
> the filtering of email contents if a security issue is embargoed for a
> period of time.  I am working on the detailed process that will be used
> for these types of issues and will update tianocore web pages with the
> details for both normal bugs and security issues.
> 
> I am working through a few details today to reduce the number of
> p

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

On 07/19/16 19:24, Kinney, Michael D wrote:
>> -Original Message-
>> From: Laszlo Ersek [mailto:ler...@redhat.com]
>> Sent: Wednesday, July 6, 2016 12:53 PM
>> To: Kinney, Michael D <michael.d.kin...@intel.com>
>> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
>> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

>> Also, the multi-selection is not flexible enough to express dependencies
>> between packages (BZ cloning is).
> 
> Not sure I understand what you mean here.  Can you provide an example?

For example, assume that the UEFI spec defines a new protocol, and we'd
like to build something upon it in OvmfPkg. The protocol definition will
go into MdePkg, so on the new bug, the package will have to be ticked.
The reference implementation (a new DXE_DRIVER module) might go into
MdeModulePkg -- the second package to be ticked. The client code belongs
to OvmfPkg, which would be the third package to be ticked for the same
Bugzilla entry.

Instead, these could be three separate BZs, each filed for a separate
component (MdePkg, MdeModulePkg, OvmfPkg), and their dependencies would
be expressed through the "Blocks" BZ fields (each such relationship sets
the "Depends" field of the other BZ as well). Hence, the OvmfPkg BZ
would depend on both the MdePkg and the MdeModulePkg BZs, and the
MdeModulePkg BZ would depend on the MdePkg BZ.

BZ cloning is not a requirement, it just saves some typing, and it adds
another "hint" hat the BZs are related to the same larger bug or feature
group.

(Because, "Blocks" and "Depends" can stand for other kinds of dependency
as well. For example, FooPkg has two maintainers, and one of them is on
vacation, but it is known that he plans to refactor a good chunk of a
driver in FooPkg. The other maintainer of FooPkg would like to implement
a small addition to that driver, but it's just not right (although
perhaps possible) to implement that small addition before the larger
refactoring happens. In this case, Blocks / Depends are also fully
appropriate, but what they express is a different kind of dependency
(i.e., not "same feature group"), so cloning doesn't apply.)

In the MdePkg -> MdeModulePkg -> OvmfPkg example, the MdePkg bug would
be cloned for MdeModulePkg, then either the MdePkg or the MdeModulePkg
bug could be cloned for OvmfPkg. Cloning creates a new bug, sets
Blocks/Depends automatically, sets the "Clone Of" field on the new bug,
and appends the number of the new bug to the "Clones" field of the
original bug. (A bug may have several clones.) Finally, the last missing
link could be added manually (with Blocks / Depends) between (MdePkg or
MdeModulePkg) and OvmfPkg.

The best part is that Bugzilla can display BZs that are linked together
through dependencies in a graph-like view.

... I do understand that practically the same can be done if we express
packages as entries in a multi-selection box, not as components. The
three BZs can be opened the same way, their dependencies / clone
relationships can be set up the same way, we'd just tick exactly one
package line in the multi-selection box in each BZ.

My point was that if we simply tick all three of MdePkg, MdeModulePkg,
OvmfPkg on the same BZ, then "what depends on what" is not expressed in
Bugzilla.

Thanks!
Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Kinney, Michael D]

Hi Michael,

We have edk2-devel mailing list today for patch submissions/review and 
design/implementation discussions.

The commit messages in the future should include a link to the Bugzilla 
issue(s) the patch addresses.

If there are lively discussion on edk2-devel on root causing a bug or 
discussions on where and how the
bug should be fixed in code, then the Bugzilla entry can include gmane links to 
those edk2-devel threads.

I expect we will refine the commit message requirements and Bugzilla issue 
entry requirements as we use it.

Mike

From: Michael Zimmermann [mailto:sigmaepsilo...@gmail.com]
Sent: Tuesday, July 19, 2016 10:59 AM
To: Kinney, Michael D <michael.d.kin...@intel.com>
Cc: Laszlo Ersek <ler...@redhat.com>; edk2-devel@lists.01.org 
<edk2-de...@ml01.01.org>
Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

how will this work side-by-side with the mailing list?
It kinda sounds like a mailing list replacement, and you probably don't want to 
have separate mailing list topics and bugzilla reports about the same thing.

Thanks
Michael

On Tue, Jul 19, 2016 at 7:24 PM, Kinney, Michael D 
<michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>> wrote:
Laszlo,

Thanks for the feedback.  A few responses embedded below.

I agree there are many ways to organize this content inside Bugzilla
and that we can refine the products/components/fields as we use it.

Mike

> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com<mailto:ler...@redhat.com>]
> Sent: Wednesday, July 6, 2016 12:53 PM
> To: Kinney, Michael D 
> <michael.d.kin...@intel.com<mailto:michael.d.kin...@intel.com>>
> Cc: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org> 
> <edk2-de...@ml01.01.org<mailto:edk2-de...@ml01.01.org>>
> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
>
> On 07/06/16 20:52, Kinney, Michael D wrote:
> > Laszlo,
> >
> > Good timing.  I was going to send a status update today.
> >
> > We are working diligently to get Bugzilla online for all bugs.  There
> > are a few logistics that are still being worked this week related to
> > an email list for bug state changes that Jordan is helping with and
> > setting up tianocore domain name for the Bugzilla server.
> >
> > I see many developers have created accounts on the Bugzilla server
> > that is in a test mode right now.  Thank you to everyone who has done
> > that already!  If you have not done so, please go to the following
> > link and create an account.
> >
> > https://tianocore.acgmultimedia.com
> >
> > Also, please enter some sample bugs and feature requests and review
> > the fields.  Please send feedback if you would like to see any changes
> > to the fields.
> >
> > I will send updates as tasks are completed as I also want to see us
> > move to Bugzilla ASAP.  This is my highest priority task right now.
>
> I skimmed the "new bug page" (with the advanced fields shown) for
> TestProduct -- from a cursory look, it's fine.
>
> Other than that, why is "Feature Requests" a separate product from "EDK2
> - Main Trunk"? Same for "UEFI Security Issues". I think feature requests
> and security issues should not be separate products. They should be
> orthogonal to any product. In the RH Bugzilla at least, these "traits"
> are represented by Keywords.

Security issues are in a separate product so we can associate then with
the "infosec" group for evaluation in the UNCONFIRMED state and support
the filtering of email contents if a security issue is embargoed for a
period of time.  I am working on the detailed process that will be used
for these types of issues and will update tianocore web pages with the
details for both normal bugs and security issues.

I am working through a few details today to reduce the number of products.

* "Test Product" will be removed.  This was just to evaluate before going live.
* I have renamed to "Tianocore Feature Requests".  This is to cover feature
  requests not only for EDK II code/tools/docs, but also for things like
  the web site, wiki pages, dev process, testing process, release process,
  etc.
* I am going to remove "UDK" and update "EDK2" to add a field to identify
  both where the issue was observed (EDK2 trunk, UDK 2015, UDK 2014, etc).
  and where the issue need to be fixed (EDK2 trunk, UDK 2015, UDK 2014, etc).

>
> Regarding the "EDK2 - Main Trunk" product, I see three components, Code,
> Documentation, and Test. I think "component" should correspond to any
> entity in the edk2 tree that has a well defined set of maintainers --
> currently, top level 

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Michael Zimmermann]

how will this work side-by-side with the mailing list?
It kinda sounds like a mailing list replacement, and you probably don't
want to have separate mailing list topics and bugzilla reports about the
same thing.

Thanks
Michael

On Tue, Jul 19, 2016 at 7:24 PM, Kinney, Michael D <
michael.d.kin...@intel.com> wrote:

> Laszlo,
>
> Thanks for the feedback.  A few responses embedded below.
>
> I agree there are many ways to organize this content inside Bugzilla
> and that we can refine the products/components/fields as we use it.
>
> Mike
>
> > -Original Message-
> > From: Laszlo Ersek [mailto:ler...@redhat.com]
> > Sent: Wednesday, July 6, 2016 12:53 PM
> > To: Kinney, Michael D <michael.d.kin...@intel.com>
> > Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
> > Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative
> events
> >
> > On 07/06/16 20:52, Kinney, Michael D wrote:
> > > Laszlo,
> > >
> > > Good timing.  I was going to send a status update today.
> > >
> > > We are working diligently to get Bugzilla online for all bugs.  There
> > > are a few logistics that are still being worked this week related to
> > > an email list for bug state changes that Jordan is helping with and
> > > setting up tianocore domain name for the Bugzilla server.
> > >
> > > I see many developers have created accounts on the Bugzilla server
> > > that is in a test mode right now.  Thank you to everyone who has done
> > > that already!  If you have not done so, please go to the following
> > > link and create an account.
> > >
> > > https://tianocore.acgmultimedia.com
> > >
> > > Also, please enter some sample bugs and feature requests and review
> > > the fields.  Please send feedback if you would like to see any changes
> > > to the fields.
> > >
> > > I will send updates as tasks are completed as I also want to see us
> > > move to Bugzilla ASAP.  This is my highest priority task right now.
> >
> > I skimmed the "new bug page" (with the advanced fields shown) for
> > TestProduct -- from a cursory look, it's fine.
> >
> > Other than that, why is "Feature Requests" a separate product from "EDK2
> > - Main Trunk"? Same for "UEFI Security Issues". I think feature requests
> > and security issues should not be separate products. They should be
> > orthogonal to any product. In the RH Bugzilla at least, these "traits"
> > are represented by Keywords.
>
> Security issues are in a separate product so we can associate then with
> the "infosec" group for evaluation in the UNCONFIRMED state and support
> the filtering of email contents if a security issue is embargoed for a
> period of time.  I am working on the detailed process that will be used
> for these types of issues and will update tianocore web pages with the
> details for both normal bugs and security issues.
>
> I am working through a few details today to reduce the number of products.
>
> * "Test Product" will be removed.  This was just to evaluate before going
> live.
> * I have renamed to "Tianocore Feature Requests".  This is to cover feature
>   requests not only for EDK II code/tools/docs, but also for things like
>   the web site, wiki pages, dev process, testing process, release process,
>   etc.
> * I am going to remove "UDK" and update "EDK2" to add a field to identify
>   both where the issue was observed (EDK2 trunk, UDK 2015, UDK 2014, etc).
>   and where the issue need to be fixed (EDK2 trunk, UDK 2015, UDK 2014,
> etc).
>
> >
> > Regarding the "EDK2 - Main Trunk" product, I see three components, Code,
> > Documentation, and Test. I think "component" should correspond to any
> > entity in the edk2 tree that has a well defined set of maintainers --
> > currently, top level Pkg directories. When a feature or bugfix affects
> > several components, then the original bug is cloned for the other
> > component(s) -- see the "Clone This Bug" link -- and then the bug
> > dependencies are adjusted as necessary.
> >
> > (In the GitHub issue tracker, we have "labels" for the top Pkg
> > directories, plus a few orthogonal labels (e.g. Feature, Udk-,
> > UdkOnly).)
> >
> > Hm... I'm just noticing the custom Package box. When I hover over it, it
> > says "A custom Multiple-Selection Box field in this installation of
> > Bugzilla". I think I understand the idea, but it might mix well with

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Kinney, Michael D]

Laszlo,

Thanks for the feedback.  A few responses embedded below.

I agree there are many ways to organize this content inside Bugzilla
and that we can refine the products/components/fields as we use it.

Mike

> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: Wednesday, July 6, 2016 12:53 PM
> To: Kinney, Michael D <michael.d.kin...@intel.com>
> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
> 
> On 07/06/16 20:52, Kinney, Michael D wrote:
> > Laszlo,
> >
> > Good timing.  I was going to send a status update today.
> >
> > We are working diligently to get Bugzilla online for all bugs.  There
> > are a few logistics that are still being worked this week related to
> > an email list for bug state changes that Jordan is helping with and
> > setting up tianocore domain name for the Bugzilla server.
> >
> > I see many developers have created accounts on the Bugzilla server
> > that is in a test mode right now.  Thank you to everyone who has done
> > that already!  If you have not done so, please go to the following
> > link and create an account.
> >
> > https://tianocore.acgmultimedia.com
> >
> > Also, please enter some sample bugs and feature requests and review
> > the fields.  Please send feedback if you would like to see any changes
> > to the fields.
> >
> > I will send updates as tasks are completed as I also want to see us
> > move to Bugzilla ASAP.  This is my highest priority task right now.
> 
> I skimmed the "new bug page" (with the advanced fields shown) for
> TestProduct -- from a cursory look, it's fine.
> 
> Other than that, why is "Feature Requests" a separate product from "EDK2
> - Main Trunk"? Same for "UEFI Security Issues". I think feature requests
> and security issues should not be separate products. They should be
> orthogonal to any product. In the RH Bugzilla at least, these "traits"
> are represented by Keywords.

Security issues are in a separate product so we can associate then with
the "infosec" group for evaluation in the UNCONFIRMED state and support
the filtering of email contents if a security issue is embargoed for a 
period of time.  I am working on the detailed process that will be used
for these types of issues and will update tianocore web pages with the
details for both normal bugs and security issues. 

I am working through a few details today to reduce the number of products.

* "Test Product" will be removed.  This was just to evaluate before going live.
* I have renamed to "Tianocore Feature Requests".  This is to cover feature
  requests not only for EDK II code/tools/docs, but also for things like
  the web site, wiki pages, dev process, testing process, release process, 
  etc.
* I am going to remove "UDK" and update "EDK2" to add a field to identify
  both where the issue was observed (EDK2 trunk, UDK 2015, UDK 2014, etc).
  and where the issue need to be fixed (EDK2 trunk, UDK 2015, UDK 2014, etc).

> 
> Regarding the "EDK2 - Main Trunk" product, I see three components, Code,
> Documentation, and Test. I think "component" should correspond to any
> entity in the edk2 tree that has a well defined set of maintainers --
> currently, top level Pkg directories. When a feature or bugfix affects
> several components, then the original bug is cloned for the other
> component(s) -- see the "Clone This Bug" link -- and then the bug
> dependencies are adjusted as necessary.
> 
> (In the GitHub issue tracker, we have "labels" for the top Pkg
> directories, plus a few orthogonal labels (e.g. Feature, Udk-,
> UdkOnly).)
> 
> Hm... I'm just noticing the custom Package box. When I hover over it, it
> says "A custom Multiple-Selection Box field in this installation of
> Bugzilla". I think I understand the idea, but it might mix well with
> searching. The Advanced Search page allows filtering for Package only in
> the Custom Search section, which I find a bit unwieldy.
> 
> Also, the multi-selection is not flexible enough to express dependencies
> between packages (BZ cloning is).

Not sure I understand what you mean here.  Can you provide an example?

> 
> On the positive side, the Package box is available on the Enter Bug page
> as well, after showing the Advanced Fields.
> 
> ... Just trying to apply my experience with the RH bugzilla; it may not
> be a perfect fit, of course. If we end up with something different here,
> I'll be happy to learn it. :) I'm not suggesting that the above remarks
> be addressed ASAP, "or else". :) I think the fields can be tweaked (the
> database can be converted) later on as well; I wouldn't like to cause
> any delays.
> 
> Thanks!
> Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

On 07/06/16 20:52, Kinney, Michael D wrote:
> Laszlo,
> 
> Good timing.  I was going to send a status update today.
> 
> We are working diligently to get Bugzilla online for all bugs.  There 
> are a few logistics that are still being worked this week related to 
> an email list for bug state changes that Jordan is helping with and 
> setting up tianocore domain name for the Bugzilla server.
> 
> I see many developers have created accounts on the Bugzilla server
> that is in a test mode right now.  Thank you to everyone who has done
> that already!  If you have not done so, please go to the following
> link and create an account.
> 
>   https://tianocore.acgmultimedia.com
> 
> Also, please enter some sample bugs and feature requests and review
> the fields.  Please send feedback if you would like to see any changes
> to the fields.
> 
> I will send updates as tasks are completed as I also want to see us 
> move to Bugzilla ASAP.  This is my highest priority task right now.

I skimmed the "new bug page" (with the advanced fields shown) for
TestProduct -- from a cursory look, it's fine.

Other than that, why is "Feature Requests" a separate product from "EDK2
- Main Trunk"? Same for "UEFI Security Issues". I think feature requests
and security issues should not be separate products. They should be
orthogonal to any product. In the RH Bugzilla at least, these "traits"
are represented by Keywords.

Regarding the "EDK2 - Main Trunk" product, I see three components, Code,
Documentation, and Test. I think "component" should correspond to any
entity in the edk2 tree that has a well defined set of maintainers --
currently, top level Pkg directories. When a feature or bugfix affects
several components, then the original bug is cloned for the other
component(s) -- see the "Clone This Bug" link -- and then the bug
dependencies are adjusted as necessary.

(In the GitHub issue tracker, we have "labels" for the top Pkg
directories, plus a few orthogonal labels (e.g. Feature, Udk-,
UdkOnly).)

Hm... I'm just noticing the custom Package box. When I hover over it, it
says "A custom Multiple-Selection Box field in this installation of
Bugzilla". I think I understand the idea, but it might mix well with
searching. The Advanced Search page allows filtering for Package only in
the Custom Search section, which I find a bit unwieldy.

Also, the multi-selection is not flexible enough to express dependencies
between packages (BZ cloning is).

On the positive side, the Package box is available on the Enter Bug page
as well, after showing the Advanced Fields.

... Just trying to apply my experience with the RH bugzilla; it may not
be a perfect fit, of course. If we end up with something different here,
I'll be happy to learn it. :) I'm not suggesting that the above remarks
be addressed ASAP, "or else". :) I think the fields can be tweaked (the
database can be converted) later on as well; I wouldn't like to cause
any delays.

Thanks!
Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Kinney, Michael D]

Laszlo,

Good timing.  I was going to send a status update today.

We are working diligently to get Bugzilla online for all bugs.  There 
are a few logistics that are still being worked this week related to 
an email list for bug state changes that Jordan is helping with and 
setting up tianocore domain name for the Bugzilla server.

I see many developers have created accounts on the Bugzilla server
that is in a test mode right now.  Thank you to everyone who has done
that already!  If you have not done so, please go to the following
link and create an account.

https://tianocore.acgmultimedia.com

Also, please enter some sample bugs and feature requests and review
the fields.  Please send feedback if you would like to see any changes
to the fields.

I will send updates as tasks are completed as I also want to see us 
move to Bugzilla ASAP.  This is my highest priority task right now.

Thanks,

Mike


> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Laszlo 
> Ersek
> Sent: Wednesday, July 6, 2016 2:19 AM
> To: Kinney, Michael D <michael.d.kin...@intel.com>
> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
> 
> (addressing Mike due to
> <http://thread.gmane.org/gmane.comp.bios.edk2.devel/13285>)
> 
> Mike,
> 
> On 05/23/16 20:33, Mangefeste, Tony wrote:
> > Folks,
> >
> > I'm ramping up work on deploying the Bugzilla server for our
> > community.  A few things you will begin to see, and your comments are
> > appreciated on the below.
> >
> > 1. I'm going to send updates to the list.  I'm going to add the tag
> > [INFO] to the subject line to pass down information to the community.
> > This is going to include some information related to bugzilla, or
> > anything else community related.
> >
> > 2. Our bugzilla server is being hosted by ACG Multimedia.  They are a
> > vendor contracted by Intel, managed by me, and they own the physical
> > hardware that is hosting the server.  Data submitted to our community
> > bugzilla server does not reside on Intel machines, and as such only
> > content pertaining to Tianocore should be added to our server.
> >
> > 3. The server URL is (https://tianocore.acgmultimedia.com).  At this
> > time I'd like to ask all maintainers to please logon and create an
> > account.  I will use this information to assign package maintainers
> > to specific security groups, email and such.
> >
> > 4. Feel free to submit issues, but for now, it is *not yet live*.
> > I'm working on it in real time, and anticipate making a broader
> > announcement to the community on June 6, 2016.
> >
> > The big ask right now pertains to maintainers.  Please create your
> > accounts, with secure passwords.  Everyone else may create their
> > account, but please do not load the database with issues right now.
> >
> > Lastly, please wind down usage of Github Issues!
> >
> > More incoming. Tony
> 
> may I ask how the Bugzilla server is coming along? GitHub doesn't send
> emails about in-place comment edits, and I've just been burned by that.
> I'd like to move over to Bugzilla ASAP.
> 
> Thanks!
> Laszlo
> ___
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Laszlo Ersek]

(addressing Mike due to
)

Mike,

On 05/23/16 20:33, Mangefeste, Tony wrote:
> Folks,
> 
> I'm ramping up work on deploying the Bugzilla server for our
> community.  A few things you will begin to see, and your comments are
> appreciated on the below.
> 
> 1. I'm going to send updates to the list.  I'm going to add the tag
> [INFO] to the subject line to pass down information to the community.
> This is going to include some information related to bugzilla, or
> anything else community related.
> 
> 2. Our bugzilla server is being hosted by ACG Multimedia.  They are a
> vendor contracted by Intel, managed by me, and they own the physical
> hardware that is hosting the server.  Data submitted to our community
> bugzilla server does not reside on Intel machines, and as such only
> content pertaining to Tianocore should be added to our server.
> 
> 3. The server URL is (https://tianocore.acgmultimedia.com).  At this
> time I'd like to ask all maintainers to please logon and create an
> account.  I will use this information to assign package maintainers
> to specific security groups, email and such.
> 
> 4. Feel free to submit issues, but for now, it is *not yet live*.
> I'm working on it in real time, and anticipate making a broader
> announcement to the community on June 6, 2016.
> 
> The big ask right now pertains to maintainers.  Please create your
> accounts, with secure passwords.  Everyone else may create their
> account, but please do not load the database with issues right now.
> 
> Lastly, please wind down usage of Github Issues!
> 
> More incoming. Tony

may I ask how the Bugzilla server is coming along? GitHub doesn't send
emails about in-place comment edits, and I've just been burned by that.
I'd like to move over to Bugzilla ASAP.

Thanks!
Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] [RFC] Email tags for Bugzilla and administrative events

[Mangefeste, Tony]

The server had a bit of a hiccup, but it's back :)

> -Original Message-
> From: Laszlo Ersek [mailto:ler...@redhat.com]
> Sent: Monday, May 23, 2016 2:57 PM
> To: Mangefeste, Tony <tony.mangefe...@intel.com>
> Cc: edk2-devel@lists.01.org <edk2-de...@ml01.01.org>
> Subject: Re: [edk2] [RFC] Email tags for Bugzilla and administrative events
> 
> On 05/23/16 20:33, Mangefeste, Tony wrote:
> > Folks,
> >
> > I'm ramping up work on deploying the Bugzilla server for our
> > community.  A few things you will begin to see, and your comments are
> > appreciated on the below.
> >
> > 1. I'm going to send updates to the list.  I'm going to add the tag
> > [INFO] to the subject line to pass down information to the community.
> > This is going to include some information related to bugzilla, or
> > anything else community related.
> >
> > 2. Our bugzilla server is being hosted by ACG Multimedia.  They are a
> > vendor contracted by Intel, managed by me, and they own the physical
> > hardware that is hosting the server.  Data submitted to our community
> > bugzilla server does not reside on Intel machines, and as such only
> > content pertaining to Tianocore should be added to our server.
> >
> > 3. The server URL is (https://tianocore.acgmultimedia.com).  At this
> > time I'd like to ask all maintainers to please logon and create an
> > account.  I will use this information to assign package maintainers to
> > specific security groups, email and such.
> 
> At first the server threw different error messages at me ("Forbidden"
> and something about not finding "Auth.pm" or similar). Ultimately I managed
> to enter my email address, but the confirmation email doesn't seem to
> arrive. (It might arrive later I guess.)
> 
> > 4. Feel free to submit issues, but for now, it is *not yet live*.
> > I'm working on it in real time, and anticipate making a broader
> > announcement to the community on June 6, 2016.
> >
> > The big ask right now pertains to maintainers.  Please create your
> > accounts, with secure passwords.  Everyone else may create their
> > account, but please do not load the database with issues right now.
> >
> > Lastly, please wind down usage of Github Issues!
> 
> We have live tickets where we're communicating with users. I think I
> shouldn't abort that communication immediately.
> 
> If the GitHub issue tracker can be convinced to reject new issues (with a
> pointer to this mailing list message), that could allow for an easier 
> transition.
> (I.e., minimize the number of tickets that are severed in half by the
> bugtracker switch-over.)
> 
> Looking forward to using Bugzilla!

We will migrate the issues from GitHub to BZ, before we shut it down! 

> 
> Thanks!
> Laszlo
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel