Closed madeleineostoja closed 6 years ago
Worth noting: transferring a repo via Github maintains redirects for Bower and co, so no problems there
I don't see any issues here, and definitely all for bringing together in one home 👍
Cool, will start migrating
Putting a hold on this until we figure out what the deal with JS elements is. If we're going to rebuild them all in JS (ie: not using Polymer, or living dangerously and jumping straight to Polymer 3), then I motion to make simpla-elements a monorepo of them, as well as the webcomponents.org listing catalogue.
Decided to do this anyway
@seaneking as in a monorepo or just moving into separate repos?
Oh never mind - see they're already transferred over. Down the track when / if we do all JS, I'd still be keen for a monorepo approach 👍
Ha yeah just transferring, can't exactly do a monorepo w/ Bower
And from our discussions sounds like all-JS is still a way off, sooo...
Now that Simpla is becoming a community driven project, it makes a lot of sense for everything to have one home, rather than half the project spread over the simplaio org and the SimplaElements org.
Makes contributing more straightforward, and cleans up the ecosystem. Maybe once the project is 100% NPM we could even look at a monorepo approach. But that's a discussion for another day.
What do we think?Transfers
Other tasks
Notes
Do we want to split simpla-richtext-behavior into a general JS module, since it's not actually tied to Simpla?
Do we want to bundle simpla-element-behavior into the core library?