Note: Do not edit this page yourself unless asked to.
FreeBSD Developer Summit: Quality Assurance Testing Group
(Add the exact date and time of your working group here.)
Overview
The intents for the workgroup are to talk about which QA services/processes we have right now and if we need to improve any of them as well as create new QA services for the project. It would be good to have people from different teams so src, ports, doc and probably releng and people that currently work/maintain the existing systems.
If you would like to participate, contact the working group chairs below and CC devsummit@. You will be then added to this page. Please include a list of things you want to talk about or the areas you are interested in. This helps us in planning the session and to bring people together with common interests.
It is possible to bring in people who cannot attend in person via video conference or chat tools. Notes during the session will be published later on for the whole community to see what we discussed.
Goals
In particular, we would like to cover the following topics. This is not an exhaustive list and if you feel there is something missing that you want to talk about, contact one of the session chairs and we will include your topic here. Note that the numbering of the topics does not represent an ordering or importance indication of any kind, but rather a reference to the second table with the “topic of interest” column.
Topics
| # | Topic Description |
|---|---|
| Ports QA | Exp-runs (pre commit buildtests for ports infrastructure and important ports) Ports QAT (post commit buildtest) Redports (pre commit buildtest) Pointyhat (package building; failing build triggers mail) Additional processes: INDEX breaks, portscout, distfile availability checker |
| Source QA | Tinderbox (regular buildtest of head) Coverity (static analysis, status?) |
| Doc/www QA | Manual build tests (pre commit build test) textproc/igor (automatic proofreading) Automatic post commit build test Linkchecker (manual) |
Note: General presentations about work you have done that does not require further discussions should be submitted for the FreeBSD Developer Summit track at EuroBSDcon (see general developer summit page).
Attending
In order to attend you need register for the developer summit as well as by email for the session and be confirmed by the working group organizer. Follow the guidelines described on the main page or what you received by email. For questions or if in doubt ask the session chairs.
Please do NOT add yourself here. Your name will appear automatically once you received the confirmation email. You need to put your name on the general developer summit attendees list though.
| # | Name | Username / Affiliation | Topics of Interest | Notes |
|---|---|---|---|---|
| 1 | IonMihaiTetcu | itetcu | chair | |
| 2 | BernhardFroehlich | decke | chair | |
| 3 | UlrichSpoerlein | uqs | Coverity, clang static analyzer | |
| 4 | PáliGáborJános | pgj | ||
| 5 | DaichiGoto | daichi | ||
| 6 | ErwinLansing | erwin | ||
| 7 | MarekVavrusa | erwin@'s guest | CZ.nic | |
| 8 | GlebSmirnoff | glebius | ||
| 9 | Joerg Sonnenberger | NetBSD | pgj@'s guest | |
| 10 | EdwardTomaszNapierala | trasz@ | automatic testing frameworks | |
| 11 | BeatGaetzi | beat |
Results
(Add a list or attach slides detailing the achieved results here.)