==================================
#fedora-meeting: Fedora QA Meeting
==================================


Meeting started by jlaska at 16:00:20 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2009-11-30/qa.2009-11-30-16.00.log.html
.



Meeting summary
---------------
* Gathering in the lobby  (jlaska, 16:00:44)
  * LINK:
    https://www.redhat.com/archives/fedora-test-list/2009-November/msg01223.html
    (jlaska, 16:05:27)

* Previous meeting follow-up  (jlaska, 16:05:41)

* Enhancing release criteria  (jlaska, 16:08:42)
  * next step ... of taking all that feedback and working it into the
    pages  (jlaska, 16:15:27)
  * send another reminder to the list by say tomorrow  (jlaska,
    16:15:34)
  * hackfest session at FUDCon to finalize  (jlaska, 16:15:49)
  * ACTION: adamw to offer some guidance on how to handle
    hardware/local_configuration specific bugs  (jlaska, 16:16:11)

* Security Policy/Test_Plan  (jlaska, 16:17:00)
  * LINK:
    https://www.redhat.com/archives/fedora-devel-list/2009-November/msg01745.html
    (jlaska, 16:17:33)
  * there's vague consensus that we should have package defaults that
    are 'very secure' and then per-spin  customization for less security
    (if desired)  (jlaska, 16:23:03)
  * no-one has really stepped up and said 'yeah there's a plan and we're
    doing it here'  (jlaska, 16:23:17)
  * skvidal drafted a change policy and sent to fesco mailing list last
    week  (jlaska, 16:23:42)
  * next step ... file a FESCO ticket asking fesco to look into the
    issue and help us move towards a security policy  (jlaska, 16:31:47)
  * ACTION: adamw will reach out to FESCO for guidance on defining a
    security policy  (jlaska, 16:32:53)

* F-12 QA retrospective  (jlaska, 16:35:05)
  * LINK:
    https://www.redhat.com/archives/fedora-test-list/2009-November/msg01126.html
    (jlaska, 16:35:12)
  * LINK: https://fedoraproject.org/wiki/Fedora_12_QA_Retrospective
    (jlaska, 16:36:11)
  * Next steps ... I plan to organize the feedback into related groups
    to make it easier to see trends/problem_areas  (jlaska, 16:39:57)

* AutoQA Updates  (jlaska, 16:41:49)
  * kparal has a few autoqa patches out for review - adding --help and
    --dry-run options to all watchers  (jlaska, 16:45:32)
  * kparal plans to contribute to the 'Getting started' use case once
    changes are in  (jlaska, 16:46:03)
  * kparal some progress on integrating rpmguard, more work remains
    (jlaska, 16:47:24)
  * Wwoods accepted kparal's local autoqa harness patch ... tests can
    now be launched on your local system to facilitate test
    development/integration  (jlaska, 16:49:30)
  * wwoods improved support for running 'noarch' tests - tests like
    rpmlint, which don't need to run on  the same arch as the target
    package/tree  (jlaska, 16:53:49)
  * wwoods updated repoinfo to reflect the fact that there's no ppc
    rawhide anymore  (jlaska, 16:54:01)
  * wwoods plans ... some FUDCon prep work and helping kparal integrate
    rpmguard  (jlaska, 16:54:42)
  * thanks to help from abadger1999, autoqa-israwhidebroken is now
    packaged.  I sent a link to the branch to autoqa-devel.  If folks
    are happy, I can merge that into master  (jlaska, 16:56:40)

* Open Discussion - <your topic here>  (jlaska, 16:59:08)
  * LINK: http://loupgaroublond.blogspot.com/2009/11/glogg.html
    (adamw, 16:59:40)

* Open Discussion - Glögg as the official drink of QA  (jlaska,
  17:00:07)
  * LINK:
    http://www.mostphotos.com/preview/150009/grogg-drink-ice-glas-red.jpg
    ?  (jlaska, 17:01:19)
  * LINK:
    http://www.drunkenblog.com/drunkenblog-archives/i/oh_glogg_youdevil.jpg
    (jlaska, 17:01:42)
  * LINK: http://www.acatinthekitchen.com/photo/advent/glogg.jpg
    (adamw, 17:01:59)

* Open Discussion - FUDCon travel plans  (jlaska, 17:03:36)

* Open Discussion - FUDCon travel plans  (jlaska, 17:04:45)

Meeting ended at 17:08:26 UTC.




Action Items
------------
* adamw to offer some guidance on how to handle
  hardware/local_configuration specific bugs
* adamw will reach out to FESCO for guidance on defining a security
  policy




Action Items, by person
-----------------------
* adamw
  * adamw to offer some guidance on how to handle
    hardware/local_configuration specific bugs
  * adamw will reach out to FESCO for guidance on defining a security
    policy
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* jlaska (115)
* adamw (53)
* wwoods (27)
* poelcat (25)
* kparal (15)
* nirik (14)
* skvidal (14)
* Oxf13 (10)
* Viking-Ice (7)
* zodbot (3)
* tk009 (2)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot