Re: Feb 19 meeting actions, discussion, notes, and recording

Hi Michael,

I'm not sure I totally follow, but I *think* you're suggesting that the
bhyve manageability workstream from EWG be absorbed into the production
users call.

If so, I personally have no objection to this. As far as funding and any
relationship with the Foundation, since I no longer work at the Foundation
I can't speak to this other than to say I don't have any objection.

---
Greg Wallace


On Fri, Feb 28, 2025 at 2:06 PM Michael Dexter <editor@callfortesting.org>
wrote:

> Greg, All,
>
> Than you for your efforts!
>
> On 2/28/25 8:31 AM, Greg Wallace wrote:
> > # Break it up into a few more focused areas, e.g.
> >  1. Broaden the AD/DNS integration workstream into a SSO WG
> >  2. Break GPU acceleration into its own WG
> >  3. Remove all workstreams where there are existing funded or community
> >     efforts (OpenJDK, Sovereign Tech Agency, bhyve manageability) or
> >     where the scope of the effort is 100% understood and it's simply a
> >     matter of time and persistence (smbfs, GHA)
> > # Other ideas? Let the group know other options you think make sense
>
> As you know, the Production User calls* have identified real-world
> production needs and coordinated funding for new features for inclusion
> in base, that were either greenfield or abandoned via GSoC and other
> efforts.
>
> We currently have a developer available to assess and selectively
> implement some very-specific projects of various sizes:
>
> * A feature audit of bhyve on FreeBSD and illumos
> * Platform spoofing, for lack of a better term, allowing bhyve appear to
> be another hypervisor such as KVM
> * An EDK2 Update
> * Port SeaBIOS to bhyve
> * Revive the UPB libvdsk code
> * Revive the para-virtualized clock code
>
> Are you open to our formalizing some of these and establishing a funding
> mechanism with the EWG and Foundation?
>
> All the best,
>
> Michael Dexter
>
> * https://youtube.com/@callfortesting | https://callfortesting.org
>
>