Re: [Wireshark-dev] Code of Conduct for our community
I agree, The samba one is much more comfortable. On Thu, Aug 6, 2020 at 3:07 AM Richard Sharpe wrote: > > On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier wrote: > > > > All, > > > > As discussed in the last Remote Developer Den meeting I see a Code of > > Conduct (CoC) as helpful for our community. > > Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. > > I would suggest the following alternative approach that the Samba team > seems to have adopted: > > https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely > > As far as I can recall, there have been no instances of the behavior > the Contributor Covenant seems to protect against, so what is the > point here? > > Is someone saying that Wireshark is bad because of harassment on the lists? > > > I propose that we adopt the "Contributor Covenant" version 2 [1] for our > > community. > > This is a well established CoC with a good scope (including code review, > > mailing lists, ask.wireshark.org, Sharkfest). > > > > The instance to handel reports should be a team consisting of 3 or 5 well > > accepted community members (not only core > > devs). The email address to reach them should be an alias or so > > (repo...@wireshark.org). > > We should have a wiki page where the team members are listed (similar to > > node.js [2]). > > > > [3] gives a nice overview of CoC and is a good starting point to read. [4] > > is a scientific paper discussing some aspects > > of different CoC. > > > > So, what's your opinion? Any concerns? Any suggestions? > > > > Cheers > > Uli > > > > [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html > > [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md > > [3] https://opensource.guide/code-of-conduct/ > > [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf > > > > > > ___ > > Sent via:Wireshark-dev mailing list > > Archives:https://www.wireshark.org/lists/wireshark-dev > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Code of Conduct for our community
On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier wrote: > > All, > > As discussed in the last Remote Developer Den meeting I see a Code of Conduct > (CoC) as helpful for our community. Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. I would suggest the following alternative approach that the Samba team seems to have adopted: https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely As far as I can recall, there have been no instances of the behavior the Contributor Covenant seems to protect against, so what is the point here? Is someone saying that Wireshark is bad because of harassment on the lists? > I propose that we adopt the "Contributor Covenant" version 2 [1] for our > community. > This is a well established CoC with a good scope (including code review, > mailing lists, ask.wireshark.org, Sharkfest). > > The instance to handel reports should be a team consisting of 3 or 5 well > accepted community members (not only core > devs). The email address to reach them should be an alias or so > (repo...@wireshark.org). > We should have a wiki page where the team members are listed (similar to > node.js [2]). > > [3] gives a nice overview of CoC and is a good starting point to read. [4] is > a scientific paper discussing some aspects > of different CoC. > > So, what's your opinion? Any concerns? Any suggestions? > > Cheers > Uli > > [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html > [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md > [3] https://opensource.guide/code-of-conduct/ > [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Capturing 10GbE on a Linux laptop?
On Wed, Aug 5, 2020 at 8:56 AM Jasper Bongertz wrote: > > Hi Richard, > > I know there are some USB-C 10G network adapters (and the ProfiShark 10G, of > course), but I haven't tested any of them. I have tested one or two of them. They run warm to hot but seem to work. In my tests I used NVMe and at that time only had 1TB spare on the laptop I was using (on a second NVMe card), but it was fast enough for about 500-600MB/s. Now you can get 4TB NVMe or even 8TB NVMe (although you would pay $849 for 4TB.) However, you need Thunderbolt 3 and it seems that very few Linux laptops have that. System 76 has one or two (the Adder WS, for example.) The Librem laptops do not. Lenovo has one on it P51 and two on the P53. I used a NetGear GS110EMX to generate the traffic (with multiple devices plugged into it and mirroring all traffic to the 10GBe port(s).) > Writing that much data to disk is > something I do with small portable servers (about the size of a small shoe > box) > with a FPGA based capture card. NVMe can handle it ... -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Capturing 10GbE on a Linux laptop?
Hi Richard, I know there are some USB-C 10G network adapters (and the ProfiShark 10G, of course), but I haven't tested any of them. Writing that much data to disk is something I do with small portable servers (about the size of a small shoe box) with a FPGA based capture card. Cheers, Jasper Sunday, August 2, 2020, 7:03:05 PM, you wrote: > Hi folks, > Last year using my Cubro EX2+ I managed to capture around 600MB/s on > my Lenovo P51 laptop. > My P51 has a Thunderbolt 3 interface and has two 1TB NVMe storage > devices that are capable of 2+GBps write speeds. > I was aggregating multiple 1GbE interfaces into one of the 10GbE > interfaces and then using a 10GbE to Thunderbolt 3 adapter. > I had two Windows laptops and two OSX 10 laptops driving the load and > interestingly the Apple laptops were generating more load than the > Windows laptops via SMB2. > My question is: Is there a Linux laptop out there that can handle that > load. I have looked at System 76 and Librem but it does not seem they > are capable of handling the load. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Code of Conduct for our community
All, As discussed in the last Remote Developer Den meeting I see a Code of Conduct (CoC) as helpful for our community. I've always felt comfortable and welcome in the Wireshark community. But I'm a white old man so my view may have some bias. I propose that we adopt the "Contributor Covenant" version 2 [1] for our community. This is a well established CoC with a good scope (including code review, mailing lists, ask.wireshark.org, Sharkfest). The instance to handel reports should be a team consisting of 3 or 5 well accepted community members (not only core devs). The email address to reach them should be an alias or so (repo...@wireshark.org). We should have a wiki page where the team members are listed (similar to node.js [2]). [3] gives a nice overview of CoC and is a good starting point to read. [4] is a scientific paper discussing some aspects of different CoC. So, what's your opinion? Any concerns? Any suggestions? Cheers Uli [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md [3] https://opensource.guide/code-of-conduct/ [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
