Re: Introduction and Scientific Computing Workstream for the EWG
- In reply to: Kyle Taylor : "Introduction and Scientific Computing Workstream for the EWG"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 01 Apr 2024 14:07:13 UTC
Hello Kyle, I lead the advocacy and communications for the Foundation. I love learning about new users! Can we schedule a call to learn a little more about how you are using FreeBSD? If so, share your availability and I’ll send a calendar invite. Thanks and I look forward to talking! Kim Kim McMahon Senior Director, Advocacy, Marketing, and Community FreeBSD Foundation Email: kim@freebsdfoundation.org <mailto:kim@freebsdfoundation.org> LinkedIn <https://www.linkedin.com/in/kimmcmahonco/> X (Twitter) <https://twitter.com/kamcmahon> Website <https://kimmcmahon.io/> M: +1-303-570-2454 Schedule a meeting with me! <https://calendly.com/kmcmahonco> > On Apr 1, 2024, at 7:00 AM, Kyle Taylor <kyle.a.taylor@gmail.com> wrote: > > Hey Morning All - > > My name is Kyle Taylor. I'm a software engineer working in precision agriculture in Colorado (US). I work on microservices design and machine learning and drone / satellite imagery analysis for companies out of St. Louis and Kansas City. I'm a FreeBSD user (and advocate) and I'm new to the enterprise working group. Looking to help out where I can. > > I reviewed the notes from the last call and think there are several workstreams you all are pursuing that are spot-on and align with work in enterprise scientific computing: OCI support (podman); Bhyve management and orchestration; FreeBSD CUDA/OpenCL support, in particular. Might pro-offer better coverage in ports for Python 3.11/3.12 (or native anaconda) and statistics software for stan/pytorch/xgboost/catboost as well. > > Anyway, I appreciate the work folks are doing for enterprise compute. I plan on attending the calls for the EWG where I can. If there are other folks here pursuing work with FreeBSD for scientific computing, I'd be interested in giving some time to pursuing this as its own workstream under the EWG. > > Thanks - Kyle > > > > >