Create a monorepo for custom controls (or reuse UI elements)

[petermuessig]

Brainstorm about the name for the monorepo - naming suggestions:

ui5-cc
ui5-reuse
ui5-lab-2.0 😄

[petermuessig]

@marianfoo @marcelschork @vobu

[mauriciolauffer]

IMO, a monorepo for community driven controls/libs isn't a good idea. It seems to be a good idea for it tries to concentrate everything in one place. However, it makes quick changes harder (search/replace may affect more than expected), publishing slower (somebody else will need to review/approve the PR) and CI/CD pipelines more complex.

An awesome-list would be better. That said, if we go with a monorepo, ui5-cc seems fine :)

[marcelschork]

I'm also more into the direction of a decentralized approach and providing a yeoman template consumable via easy-ui5 that brings a standardized project setup and all the relevant tools for sharing a ui5 reuse module / ui5 control within the ui5-community. I will take care about such a template the next days. (see #3)

I suggest ui5-cc-* for controls and ui5-rm-* for (non-control) modules both as repo and package naming convention.

[vobu]

I suggest ui5-cc-* for controls and ui5-rm-* for (non-control) modules both as repo and package naming convention.

+1 for ui5-cc-* for custom controls, via npm
ui5-rm-* looks too similar to rm -rf ui5 to me 🤣 → ui5-rem-*? ui5-reuse-*? either one is fine for me