#fdio-vpp: VPP Weekly
Meeting started by edwarnicke at 16:03:24 UTC
(full logs).
Meeting summary
- Agenda Bashing (edwarnicke, 16:05:52)
- https://wiki.fd.io/view/VPP/Meeting#Agenda
(edwarnicke,
16:05:59)
- Getting Involved (alagalah, 16:10:19)
- edwarnicke Sharing "Getting involved"
page (alagalah,
16:10:48)
- https://wiki.fd.io/view/Main_Page#Get_Involved
Getting Involved (alagalah,
16:11:06)
- edwarnicke implores folks to proliferate
channels but please document them. (alagalah,
16:11:58)
- alagalah preference is keep convention of
#fdio- be kept for official projects, and ##fdio- for anything else
but... its just a convention (alagalah,
16:12:52)
- mailman hasn't been behaving and we have
reverted from mailman3 to mailman2 (alagalah,
16:13:16)
- https://lists.cloudfoundry.org/archives/
CF mailer lists (alagalah,
16:13:56)
- https://lists.cloudfoundry.org/archives/list/cf-dev@lists.cloudfoundry.org/
(alagalah,
16:14:11)
- edwarnicke notes that this looks like mailman3
which isn't working for fd.io (alagalah,
16:14:33)
- searchability is good. (tfherbert,
16:14:42)
- https://wiki.fd.io/view/Project_Proposals
Project Proposal (alagalah,
16:15:11)
- Consumability (alagalah, 16:16:43)
- Upstreaming .. we have afredette tfherbert from
RedHat who maybe able to give us insight on upstreaming ... and
potentially if folks on from Canonical could make themselves known
... (alagalah,
16:17:25)
- tfherbert afredette Committed to making VPP
work with CentOS et al but not 100% on the process (alagalah,
16:19:41)
- ACTION: afredette
(RedHat) to find out process/checklist for upstreaming RPM package.
Next week. Email pointers to RTM good enough (alagalah,
16:20:35)
- call for volunteers to getting rpms building as
part of verify/merge (edwarnicke,
16:25:08)
- call for volunteers to get rpms pushed to yum
repos are part of merge (edwarnicke,
16:25:22)
- call for volunteers to get deb packages working
well on Ubuntu 15.10 (upstart -> systemd, uio_igb ->
uio-pci-generic (edwarnicke,
16:26:23)
- dmarion CLANG works (alagalah,
16:28:05)
- DaveBarach describes gcc 5.2 issues
(edwarnicke,
16:28:05)
- we need docs for "vpp developers" "vpp api
users (like control plane)" "vpp deployers (people who just want to
install and run it)" (edwarnicke,
16:37:48)
- probably both a control plane and a data plane
section at hackathon? (tfherbert,
16:38:56)
- https://gerrit.fd.io/r/#/c/327/
- tcp/udp checksum disabling patch mentioned (edwarnicke,
16:46:49)
- https://github.com/01org/hyperscan
(KeithWiles,
16:48:04)
- joelhalpern points out we would be doing he
world a service by talking about SFC SFF and SF correctly as we look
at NSH (edwarnicke,
16:53:34)
- joelhalpern and edwarnicke spend some time
agreeing emphatically about other subtleties ;) (edwarnicke,
16:53:54)
- https://www.openhub.net/p/fdio
-> commit velocity documentation (edwarnicke,
16:54:23)
- Very interested in the NETLINK project
(alagalah,
16:55:25)
- : I agree on packaging first+1 (tfherbert,
16:58:16)
- https://wiki.fd.io/view/Mature_Release_Process
<- link to mature release processes (edwarnicke,
16:59:25)
- alagalah asks about how we number
versions (edwarnicke,
17:02:49)
- alagalah suggests sematic versioning
(edwarnicke,
17:03:20)
- https://datasift.github.io/gitflow/Versioning.html
<- semantic versioning explained (edwarnicke,
17:04:41)
- other suggestions involved YY.MM
versioning (edwarnicke,
17:04:56)
- edwarnicke No, I wasn't advocating it. I twas
seeing Relase 1.0.0 on the Mature Relase Process and had
questions (alagalah,
17:05:53)
Meeting ended at 17:08:26 UTC
(full logs).
Action items
- afredette (RedHat) to find out process/checklist for upstreaming RPM package. Next week. Email pointers to RTM good enough
Action items, by person
- afredette
- afredette (RedHat) to find out process/checklist for upstreaming RPM package. Next week. Email pointers to RTM good enough
People present (lines said)
- alagalah (44)
- edwarnicke (42)
- collabot` (12)
- KeithWiles (9)
- tfherbert (8)
- ashyoung (6)
- mdgray (4)
- cdl (2)
- joelhalpern (1)
- afredette (1)
- DaveBarach (1)
- cj (0)
Generated by MeetBot 0.1.4.