Hey,
I am Petr and besides my daily job as a software engineer at @Microsoft, I spend my free time working on petrsvihlik/WopiHost.

What is MS-WOPI?

MS-WOPI is a protocol that facilitates communication between a WOPI host and a WOPI client. A WOPI client is typically Office Online (Office Online Server, formerly known as Office Web Apps) aka Office for the web. A WOPI host can be an arbitrary storage provider.

What is WopiHost?

WopiHost is an implementation of the WOPI protocol. The project contains an abstraction layer that saves the developers from having to know the details of the MS-WOPI protocol and lets them focus on the implementation of their storage provider. The project also contains sample configurations, sample apps, etc.

Why support this project?

I want to build a go-to implementation of WOPI for .NET. There are about five sample implementations of WOPI on GitHub. I'd like to make this library the default choice for anyone who wants to start with the implementation.

What's on the roadmap?

Right now, I'm focusing on things that will enable easier and smoother adoption by the community.

• A lot of documentation improvements (on usage, extensibility, hosting, API reference, etc.)
• Implementing remaining (non-essential) WOPI REST methods
• Resolving bugs
• Plugging the WOPI Validator into the CI pipeline

Longer-term roadmap then contains:

• Improving the architecture
• MS-FSSHTTP support

How passionate am I about WOPI?

• I build this project from the earliest beta versions of .NET Core when abbreviations like DNX, KRE, KVM, and KPM were still cool
• I am a #1 contributor for the ms-wopi tag at StackOverflow.
  
• I established and moderate a Gitter channel for the WOPI community

I'll be very grateful if you consider donating to this project but don't feel obligated to do so. Any kind of support will give me extra motivation to continue! A simple thank you on Twitter will do too ;)