Planning

[maicol07]

@bocajthomas @zZHorizonZz we can use this discussion to plan the new work/something else that isn't already an issue.

We also have a roadmap/to-do list project where you can add new things to do (or ideas): To-do list/Roadmap

[bocajthomas]

plans to add this fork to host platforms? e.g: https://www.jsdelivr.com/

[maicol07]

When we'll tag a release with some content yes!

[zZHorizonZz]

@maicol07 I should have some time possibly starting next week. How should we approach this? Should we release the npm package so it can then be used for React, or what do you think needs to be done before releasing?

[maicol07]

Well, first of all I have to merge the latest upstream changes, then I'd like to add something new before releasing it. In the meantime you can use the official package (when we will release this it should be a simple switch)

[zZHorizonZz]

Alright, I have set up the repo, so currently it automatically generates the lit wrapper components from it and creates/updates PRs with the changes. It is using the original repo for now, but if the repo structure stays the same, we should be able to just switch the source repo URL and also the source library.

[maicol07]

Yes, I'd like to be as faithful as possible to the original repo

[zZHorizonZz]

I'm not sure how we plan on releasing though. I think I will wait on that for the release of the main package. I have used the @material-web-community/material-web-react for name not sure if we can get that on npm perhaps trough organization?

[maicol07]

I don't know, we can also release the wrappers independently from the main package.
Yes, we can use that name, I've just registered it on npm. I'm sending the invites now