[dpdk-ci] DPDK lab meeting agenda items 2018-07-31

[Jeremy Plsek]

Hi all,

We would like to discuss the following issues (which we did not get
into in the last meeting):

* Talk about finalizing the policies and procedures document that was
sent out as part of the minutes from the last meeting.
* How will the feature request process work? We would like to propose
that we create a new project in bugs.dpdk.org and use that as the
public-facing portal to track bugs and feature requests at a high
level. UNH-IOL will decide in which order to work on feature requests
and bug fixes, with input from the group. UNH-IOL may make
improvements to the dashboard over time as we see fit, but the group
must approve any changes that result in more vendor-specific
information being made publicly available through the dashboard before
it is made live.
* What will the process be for making the relative numbers for each
vendor public? Here are the scenarios that we are envisioning:
  - A vendor may choose to make results for a device all public or all
private.
  - A vendor may choose to make results public starting at date X.
  - A vendor may choose to make future results private leaving current
results public (to support experimental changes on a platform).
  - Anything missing from this list?


Functionality added/bugs fixed in the past 2 weeks:

* (from DPDK 2018-07-17 meeting) Added a way for members to provide
additional information about their hardware and setup. This is done by
vendors sending us a PDF of this information. Once we upload the PDF,
the "Environment Info" becomes a link to the PDF.
* Results not counted towards the overall result are now grayed out
and have a tooltip to make it more apparent that the results are not
part of the overall result.
* Fixed an issue where old patchsets would show up as incomplete when
a new environment was added.
* Added server-side and client-side caching of the home page and patchset view.


What we are working on right now:

* Adding the ability of getting the test logs produced by Jenkins from
the dashboard.
* Using the patchworks API for getting meta information instead of
storing that information in our database.

--
Jeremy Plsek
UNH InterOperability Laboratory