Merge pull request #2845 from Microsoft/Ecnassianer-patch-1-1

removed the task list

Author: keveleigh

MRTK-vNext.md

@@ -53,46 +53,6 @@ Following the feedback we’ve received both internally and through current cons
  * All testing components / scripts / prefabs / scenes should only be retained in the dev branch.  The master branch should only contain the “ToolKit” and working examples.  Master is for consumers only.
  * Simulator options need to be provided as another device. This will also form the template for new MR/XR/VR devices / SDKs.
 
-## Fringe thoughts (dumping ground for ideas :D)
-
- * Defining headset gameplay, allowing for sitting / standing or free roaming play.
-Has to be easy enough to enable single projects to handle both behaviors
- * Defining headset movement, is it free roam, shifting or teleporting?
- * With Teleporting specifically, is it cursor based or zone based (something we don’t have).  After watching the Rick and Morty retrospective, they struggled with this and movement space, something an SDK should be able to provide a starter experience for.
- * Adding interaction mechanics to objects in the scene easily. Is it grabbable, moveable, altered by gravity etc.
- * Helpers for 3d’ifying scene objects, 2 sided drawing or best practices
- * Examples, Examples, Examples – Ensuring our examples are bigger than current based off the latest examples scene that came from VRTK which was well received. (showed ALL interaction options within a small house)
- * Videos – a YT / FB video channel with educational snippets dedicated to MRTK 
-
- 
-## Proposed Tasks
-
-To ensure we have a smooth transition, we need several key tasks to be completed, to ensure a smooth transition and ensure we limit (as much as possible) any future breaking changes:
-
-1. Build the new frontend architecture, to enable both existing users and new to start building from, comprising of an Initial set interactable component prefabs / components:
-
- * Grabbing
- * Touching
- * Basic interaction
- * Teleporting
-
-2. A single example scene to demonstrate the use of the new components
-
-3. Short video demonstration of example
-
-Followed up with further front end components.
-This will enable users to start using the new style approach for building new solutions.
-
-Either in parallel (or following), we should focus on building the new underlying Multi-vr framework and stitching components together.
-
-1. Define the underlying interfaces for the Multi-vr approach which abstracts the work Stephen has started in the Input system
-2. In a feature branch, align the existing input and interaction systems to adopt the new interfaces
-3. Update the current MR implementation to the new interfaces
-
-It will be key to further understand any gaps we currently have in the toolkit to align to this new approach.
-
-Once ready, the above prefabs/components will be updated to use the new underlying framework with little to no impact on their designed scenes.
- 
 # Reference Material
 
 ## Notable components in VRTK