Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove fast-components-msft package and move to @microsoft/fluentui #3542

Closed
chrisdholt opened this issue Jul 22, 2020 · 0 comments · Fixed by #3553
Closed

Remove fast-components-msft package and move to @microsoft/fluentui #3542

chrisdholt opened this issue Jul 22, 2020 · 0 comments · Fixed by #3553
Assignees
Labels
area:dev-ops Pertains to build, CI, and other dev-ops work chore Maintenance or non-code work closed:done Work is finished

Comments

@chrisdholt
Copy link
Member

This issue exists to track the removal of fast-components-msft from the FAST repo in coordination with microsoft/fluentui#14071.

For over a year now, we've been syncing regularly with several of the folks involved with the FluentUI effort in an effort to continually find opportunities to align and converge. We're also an active part of the W3C Open UI effort. While we've always had a desire to converge from a code standpoint, previous requirements and deltas in implementation made it difficult to do so with our now deprecated/archived React implementation. As we've made the shift to focus solely on web components, we believe now is a great time to partner on the FluentUI effort and provide a Web Component offering built on FAST.

The package will move over to the Fluent UI repo without any changes. Initially, we'll continue to publish under the existing namespace until we can land a new package name for the Fluent namespace. You can read more about our long term goals and the details of the move at the issue linked above.

@chrisdholt chrisdholt added chore Maintenance or non-code work status:in-progress Work is in progress labels Jul 22, 2020
@chrisdholt chrisdholt self-assigned this Jul 22, 2020
@chrisdholt chrisdholt pinned this issue Jul 22, 2020
@EisenbergEffect EisenbergEffect added the area:dev-ops Pertains to build, CI, and other dev-ops work label Jul 23, 2020
@chrisdholt chrisdholt unpinned this issue Jul 30, 2020
@EisenbergEffect EisenbergEffect added closed:done Work is finished and removed status:in-progress Work is in progress labels Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-ops Pertains to build, CI, and other dev-ops work chore Maintenance or non-code work closed:done Work is finished
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants