Welcome to P4VFS discussions

[jessk-msft]

We are moving our Microsoft P4VFS development chats to GitHub discussions!

Internally at Microsoft, primarily within Xbox Games Studios organisation, we've had many years of collaboration and development on P4VFS. It continues to be an integral part of many of our Xbox studios' workflows. There are many people who have contributed to P4VFS, some of which are also maintainers of this GitHub project.

There is not a dedicated team at Microsoft working on P4VFS. However, many of us are developers working on teams within Xbox Games Studios which rely on P4VFS every day. Generally, our priorities are:

1. Stability and correctness. The P4VFS must behave as expected on all supported platforms. There's a great investment in the unit testing code to verify this.
2. Performance. The hydration performance is top priority. This is the time developers spend "actively waiting" for their editor to load or game to start. The sync time performance is lower priority. With P4VFS, we're not exactly racing for the fasted sync times. Developers often perform sync's while also doing something else, and likewise expect to wait a little bit.
3. New features. Unfortunately, we don't spend as much time as we'd like on new features. Hopefully the GitHub community can help.

Regards,
@jessk-msft