Merge branch 'main' into pete-dev

FAQ-License-and-Intent.md

@@ -21,39 +21,53 @@ In general, we won't prevent anything that the license allows, but we do have so
 ### Forking vs Contributing
 
 **Q: Can I fork this project and create a version for another operating system?**
+
 A: Yes, for sure. That's part of why we made this open source. Although we'd also encourage you to work with the developers for that operating system's MIDI 2.0 implementation, if available. For example, on Linux, Takashi and team working on the MIDI 2.0 implementation for ALSA.
 
 **Q: Can I fork this project and create a version for a microcontroller or embedded device?**
+
 A: We'd love to see that and perhaps even participate! Note that there are microcontroller implementations already available from AmeNote and the MIDI Association, but they don't cover all devices, of course. Feel free to ask us if we're aware of any, or to check with the MIDI Association, to see if they know of any, as well.
 
 **Q: Can I fork this project and create another version for Windows?**
+
 A: This is, of course, allowed per the license. But we'd prefer you work with us to make this project better for all musicians, rather than produce a competing or overlapping project. This is true whether you're creating a free version or a paid version.
 
 **Q: Can I fork this project and create another version for older Windows versions?**
-A: Same answer as above, but with the caveat that technically this will be difficult at best as we're using some OS features (updates to USB stack, driver model, etc) that have been made available only in the versions of Windows we support with this project.
+
+A: Same answer as above, but with the caveat that technically this will be difficult at best as we're using some OS features (updates to USB stack, driver model, WinRT device information notification, etc) that have been made available only in the versions of Windows we support with this project.
+
+**Q: Can I fork this project and create an SDK that doesn't rely on WinRT?**
+
+A: Please see previous "Can I fork?" answers for overall approach. Also please note that much of the functionality (like device discovery, hot plug/unplug notifications, auto-reconnect, etc.) build upon WinRT components in Windows. We want to have a great experience for all users, so strongly recommend that these features be retained as core SDK features, not optional add-ons, or features not available in a third-party SDK offering.
 
 ### Plugins
 
 **Q: Can I create and sell transport or other Windows MIDI Services plugins?**
-A: We'd strongly prefer to see all Windows MIDI Services plugins available as free and open source projects. 
+
+A: We'd strongly prefer to see all Windows MIDI Services plugins available as free and open source projects. We're not trying to create a third-party market for plugins, but rather just working to make MIDI better for all Windows users. But we do encourage third-party transports (prototypes of upcoming implementations, or implementations of recognized MIDI standards that we have not yet gotten to), or contributions to the first-party transports. As members of the MIDI Association, we'll also want to make sure that we're not implementing something that is counter to the MIDI standards (in progress or accepted). Let's talk!
 
 ### Application Development
 
 **Q: Can I sell an application which uses Windows MIDI Services**
-A: Of course.
+
+A: Yes. Of course.
 
 **Q: Can I create my own different settings app or tool for Windows MIDI Services?**
-A: Talk with us first. It may make more sense to participate here as an official contributor, be part of the normal distribution, etc.
+
+A: Talk with us first. It may make more sense to participate here as an official contributor, be part of the normal distribution, etc. rather than duplicate efforts.
 
 ### Device Development
 
 **Q: Can I use code from this repo in the development of my own commercial device?**
+
 A: We're happy to see you do this as long as you adhere to the terms of the license
 
 ### Hosting and Distribution
 
 **Q: Can I host the Windows MIDI Services components on my own site/server and distribute them from there.**
+
 A: Unless you are behind a firewall with no internet access, please point customers to the official distribution. Feel free to talk with us about exceptional circumstances.
 
 **Q: What about signing?**
+
 A: Only the official builds from this repo will be signed and distributed by Microsoft. This is especially important for driver signing.

docs/Gemfile.lock

@@ -70,7 +70,8 @@ GEM
     rb-fsevent (0.11.2)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    rexml (3.2.6)
+    rexml (3.2.8)
+      strscan (>= 3.0.9)
     rouge (4.2.0)
     rubyzip (2.3.2)
     safe_yaml (1.0.5)
@@ -80,6 +81,7 @@ GEM
       google-protobuf (~> 3.23)
     sass-embedded (1.69.5-x86_64-linux-gnu)
       google-protobuf (~> 3.23)
+    strscan (3.1.0)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
     unicode-display_width (2.5.0)