For the MinnowBoard we added new components under the existing BSPs and Firmware products.

* BSPs -> bsps-meta-minnow 
* Firmware -> minnowboard-firmware 
* Firmware -> minnowboard-uefi-firmware 

Do we want to copy this for the MinnowBoard-Max or create a new product specifically? I can see how either approach makes sense. I wanted to check before creating anything since removing products is a pain.

Darren and I talked: 

BSPs -> intel-corei7-64
Firmware -> minnowmax-edk2

There is a platform field, that needs a "MinnowBoard Max" entry.

We may eventually need to move intel-corei7-64 to a specialized BSP, but we'll cross that road when we get there.

So the adds appear in platform and Firmware 

Thanks,

Thank you Stephen. That plan sounds good to me. I'm going to assume that platform field means hardware field. If that isn't correct please let me know ASAP.

Yes

Additions are completed. I've made Darren Hart the default assignee and CCed Stephen by default. The QA Contact is currently blank.

Please check and move to verified state if all is as expected.

We need an item to log Hardware errors.  Darren suggested that it be a in the Infrastructure group and called Product and the component would be MinnowBoard-MAX unless you have a different suggestion.  I am using the BSP and Firmware ones now!  Thanks!!

I'm inclined to make Hardware a new top level classification. Hardware issues don't really fit anywhere in the current schema in my opinion. Infrastructure is for the systems that support Yocto Project.

So the top level classifications would be:

Yocto Project Components 	Host different projects in Yocto, like ADT, BSP, and Swabber
Infrastructure 	Yocto Infrastructure bugs, including building tool, website, bugzilla itself.
Build System & Metadata 	Including building system Bitbake, Hob, and security issues.
Documentation 	All defects related with Yocto documentations, like handbook, PRD, SDK etc.
QA/Testing 	Defects related to QA and Testing.
Runtime 	Defects related to the installation, booting or operation of runtimes.
(new*) Hardware                 Defects related to phyical hardware components.

Then we'd add a new product and component like:

Hardware -> MinnowBoard Max -> hw-minnowmax

The hw- prefix for hardware components allows for sorting and report generation like the bsps- prefix does for BSPs components.

Does that sound good?

Darren and I agree that it does sound like a good plan.

Thanks,

Added as planned. I made the capitalization match the website. MinnowBoard MAX (http://www.minnowboard.org/meet-minnowboard-max/)

I set Scott G. as the default assignee and Stephen J. default CC. No QA Contact.

Which versions and milestones do we want for this hardware?

I think milestones should match any other part of the Yocto Project but versions should be related to the lifecycle of the hardware.

Right now, there are 2 versions of the board - single core (1C) and dual core (2C).  Also The current boards are all A0, but soon we will start getting A1 revisions of the board. (Mid May)  Production might be on A1 or A2. 

There are also 3 lures we are testing (Lures are add on daughter boards).
The JTAG Lure (ITP support)
The Calamari Lure (Low speed I/O)
The Sea Cat Lure (High speed I/O)

Not sure if we want these as components and to be tracked or not:

We will most likely ignore milestones or use Q1, Q2, Q3, Q4, Future.

Thanks,

All requested changes made. I've added the Lures for now. If you decide not to use them they are easy to remove as long as no bugs are assigned to them.