From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 84E6AA0509; Tue, 5 Apr 2022 17:56:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 246D540F35; Tue, 5 Apr 2022 17:56:14 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 44AB440DF6 for ; Tue, 5 Apr 2022 17:56:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649174171; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=LwnjDGx63m6OEAd0mkeI4aJZWmJj5Jg0CqRWi7o202A=; b=P6paLH7ADIdf2069DZ6IFYw2J/BE6CFmr27daIwavcYzljQMxo+6pZhAn5jFAxsEDuLtAH ZwBY3GeO0k1xn9xK9Mr8YYdBAonKj0lPAt0RKkztPdJmpBch0wngnvNJ8K+mB+5IUGsyuY ljPPeVXdclzjUsR81D/8j3vyZtuSjJI= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-442-NiL5ZpuVN3ecZlEQNN7aJA-1; Tue, 05 Apr 2022 11:56:10 -0400 X-MC-Unique: NiL5ZpuVN3ecZlEQNN7aJA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 40A0D3C23FA0 for ; Tue, 5 Apr 2022 15:56:10 +0000 (UTC) Received: from RHTPC1VM0NT (unknown [10.22.17.196]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 24CFB4047D3D for ; Tue, 5 Apr 2022 15:56:10 +0000 (UTC) From: Aaron Conole To: dev@dpdk.org Subject: Minutes of tech-board meeting: 2022-01-12 Date: Tue, 05 Apr 2022 11:56:09 -0400 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Members Attending: - Aaron Conole - Bruce Richardson - David Marchand - Ferruh Yigit - Hemant Agrawal - Honnappa Nagarahalli - Jerin Jacob - Kevin Traynor - Konstantin Ananyev - Maxime Coquelin - Olivier Matz - Thomas Monjalon NOTE: The Technical Board meetings take place every second Wednesday on https://meet.jit.si/DPDK at 3 pm UTC. Meetings are public, and DPDK community members are welcome to attend. Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes 1/ Update for hiring a technical writer Bruce asked for a review of the requirements from last year to make sure they are still up-to-date. We are waiting on Jim St. Leger to also vet the requirements. Open questions: i. Is this an editorial role? ii. How much of the DPDK libraries / code should they be expected to learn? iii. Tech writer should be expected to lead documentation efforts across the project? iv. Should they also be expected to work on website doc? This may be scope creep. Requirements documentation to be linked to the community. 2/ Documentation We need an introductory description of DPDK. Thomas to start on it. 3/ Community Lab - SoW 2022 Planning Lincoln presented a community lab retrospective. Slides available at: https://docs.google.com/presentation/d/1Ii3RBy-MDcw-Bk1eSRC3FnqxLpOXGDnw8VTAZVugD_4/edit#slide=id.g108b683f31d_0_7 There is also a rudimentary planning doc: https://docs.google.com/document/d/1l38GZwaMuIu8hq3kMjoAHDU_LanXXTt-LYS4y7Sv4t8/edit Lab answered questions from the tech board: i. Is the Lab currently running tests against LTS branches? Yes, see dashboard ii. Is there any thoughts on improving reliability in 2022? One issue that popped up in 2021 is that much of the maintenance got deferred for other development work, so the idea is to make that maintenance and technical debt to be an item in 2022. iii. Is it still a goal to document the testing? Many of the tests are documented, but documentation can always improve. Need to add it to the SoW if it should be a tracked goal. iv. Having test reproducibility w.r.t. Docker? The idea is that the docker containers will be made available to the community and we should have some kind of criteria when choosing when to pull them. v. Trending graph for performance over time - does it make sense to add this as a goal for 2022? Need to discuss. The lab needs guidelines when deciding on priorities - what is more valuable day-to-day, etc. Tech board members to add any items / requests to doc directly or through Lincoln/Aaron. 4/ Traffic Generator lib/example Bruce is looking for early feedback / discussion about having a traffic generator library in DPDK. The idea is to have a library and sample app so that developers don't need to rely on external projects. Thomas asks, "what is the value?" Response: The biggest value is always keeping an up-to-date generator available in tree. Existing projects like pktgen/t-rex are not kept up to date, or use forked versions of DPDK. What is the goal? Is it meant to be illustrative or compete with existing solutions? No decisions made, just open questions.