Document how Labs and WCT Processes work about labs-windows HOT 5 OPEN

It'll be good to be clear about the repository within which issues and discussions should be had. I know it's a minor point and they can be moved, it's good to be clear about these things so expectations can be set and met appropriately.

To clarify. Once a Labs PR contains basic functionality it will be merged into main in the Labs repo. Further revision will be done to it there (probably working off forks from main) until it's either ready to move to the main toolkit repo or is abandoned/archived/closed.

from labs-windows.

When is something a new 'feature' vs. an improvement to an existing API and how do those fit in this process? Where do those get discussed if coming from the community?

Is there any historical precedent for this from the toolkit? How was it handled there/then?

from labs-windows.

One thing that will be a really useful reference (both to help set up Labs but also in its early life) would be to take something that was recently added to the main toolkit and extract that back to Labs.
This would:

• Provide a "real" and complete example.
• Show everything that might be needed in a Labs experiment before being promoted.
• Show how/where the things in a Labs experiment move to when they get promoted to the main toolkit.

It doesn't need a full (artificial) development history and can take what's in the Toolkit now.

from labs-windows.

When is something a new 'feature' vs. an improvement to an existing API and how do those fit in this process? Where do those get discussed if coming from the community?

Is there any historical precedent for this from the toolkit? How was it handled there/then?

Since everything minor and major has just been done as PRs in the main repo before, there's not a lot of precedent. Though it was still just a large PR at worst.

I think we have a few options?

1. Copy code into Labs in order to refactor/improve and try out things, collaborate, test, etc... in an easier environment.
2. Since we have labs infrastructure in root hopefully, we could fork and just do more work there before opening a PR.
3. We could leverage more feature type branches for these things?

One thing that will be a really useful reference (both to help set up Labs but also in its early life) would be to take something that was recently added to the main toolkit and extract that back to Labs. This would:

For sure, I was thinking the new GridSplitter refactor may be on this list of candidates. I'm also not too worried about having a variety of experiments in flight by the time we go public in varying states of development too.

from labs-windows.

See initial drafts/proposals for templates/process work in the GridSplitter experiment in #96 (discussion) and #101 (tracking issue).

from labs-windows.