All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: dev@dpdk.org
Subject: Minutes of Technical Board Meeting, 2022-07-13
Date: Mon, 16 Jan 2023 10:46:05 -0500	[thread overview]
Message-ID: <f7t8ri28oua.fsf@redhat.com> (raw)

Members Attending: 6
* Aaron Conole (chair)
* Hement Agarwal
* Maxime Coquelin
* Nathan Southern
* Stephen Hemminger
* 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

* DPDK Userspace Event updates
** CfP submissions are coming in.  More expected within the next week.
** Remote presenters can be accommodated (but not preferred, although
   remote speakers doing pre-recorded is preferred in that case)
** Remote attendance is an option - access to all sessions isn't clear
   at the moment.  First day stuff (hackathon, TB meetings, etc. aren't
   recorded) TBD, but likely will not be accessible to remote attendees.
** Some complimentary passes have been approved for qualified individuals
** Sponsorship packages were approved
** Some travel / transportation recommendataions are forthcoming to the
   website

* LF server backup
** Nathan submitted request
** Last message from Johnson @ gowdy.net is that the ticket
   is in process
** Are any additional ticket requests? - Seems no
** No ETA for completion
** Thomas says when it should be available we can do some testing and
   see if we missed anything.

* Tech writer update
** Discussion with a candidate between Thomas, Bruce, and Nathan
** Candidate represents a group, which was a surprise
** Asked for a proposal, but the proposal did not have a breakdown, just
   a flat payment for 3 months.
** Group wants hourly information, and an "out" in case the work isn't
   sufficient.
** Thomas concern is that the plan is to work "full time" but we are
   probably not able to absorb full time work.  Better if they would work
   something like 1 wk/month because that is probably closer to the workload
   we estimate.
** Maybe if they are able to split the work in small tasks we can work out a
   schedule, but the current proposal doesn't have that.
** Need an audit of work to do to generate tasks list.
** Do we pay for that?  Discussion
*** Probably do, this is work and we are asking them to do it.
*** Need to have a bigger discussion about how to come up with such an estimate,
    etc.
*** Maybe other projects have some data that we can use for coming up with an
    estimate?
*** Q: Has LF paid for this work before?  If so, what is the rate, etc.?

-- Discussing backlog --

* Security process
** Nothing new

* UNH CI / Testing
** Presented the gov board status
** UNH Git caching issue
*** Shallow clone should be sufficient for git pulls at UNH
*** Two solutions - git cache being out of sync is a rare case anyway
*** Maybe with self-retest this isn't an issue
** Question is UNH still on their schedule?
** There is a question about using UNH with OPI, doing some kind of global API
   on top of DPDK.  There is a need for a lab, and the suggestion is UNH.
** Thomas is monitoring the discussion
** Not sure about whether the teams would/could overlap

* Doc maintenance
** Need to see what will happen with tech writer candidate

* Bugzilla status
** Waiting on responses
** BZ doesn't seem overwhelmed, but needs maintenance


                 reply	other threads:[~2023-01-16 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7t8ri28oua.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.