Repository naming (loopback, loopback-next)

[bajtos]

At the moment, we have the following two "main" repositories on GitHub:

• https://github.com/strongloop/loopback hosts the original code base for versions 0.x to 3.x.
• https://github.com/strongloop/loopback-next hosts the new TypeScript code base for the version 4.x

I feel it's time to rethink the repository names to better reflect the current status of 3.x and 4.x versions:

• 3.x is in LTS mode and will go EOL next year
• 4.x is no longer "next", it's the current version

What new name should we pick for loopback repository? Few options that come to my mind: loopback3, loopback-legacy.

What new name to pick for loopback-next? I am reluctant to use loopback, I am concerned it will break all existing URLs. I am proposing to use loopback-core instead.

@strongloop/loopback-maintainers @strongloop/loopback-next thoughts?

[clayrisser]

loopforward 😆

[dhmlau]

I don't have strong preferences.

• For loopback, loopback3 or loopback-legacy seems good to me. loopback-legacy might be more suited in the sense that LB2 and LB3 (i guess there's a LB1 release) also share the same code base.
• For loopback-next, I'm good with loopback-core.

[jannyHou]

• For loopback 2 and 3, I am ok with loopback-legacy, or just stay with loopback to save the URL changing effort.

• For loopback 4, loopback-core is good to me. Some other ideas:

  • loopback-ts to imply it's written in TypeScript.
  • loopback4 to be straightforward.

[raymondfeng]

I’m -1 to rename loopback-next to loopback-core, which does not reflect all packages in the monorepo.

If I have to pick one, loopback-ts is acceptable.

[bajtos]

• loopback4 won't work when we release 5.0 version (and later 6.0, etc.)
• I can see how loopback-core can be problematic, considering the variety of packages hosted in this monorepo.
• loopback-ts is not great, but I can live with it. When I think about it, I like loopback-next more than loopback-ts.

[bajtos]

How about the name loopback-framework for the monorepo?

[rahulrkr08]

Some thoughts :)

• loopback-stacks
• loopback-platform

[nabdelgadir]

• For LoopBack 3: I like loopback-legacy.
  • I feel like we shouldn't keep it as loopback because it might be hard for a newcomer to know that it's not the current version.
• For LoopBack 4: +1 to loopback-framework

[b-admike]

My votes go to loopack-legacy for loopack repo and loopback-framework/loopback-ts/loopback-platform for lb-next monorepo.

[agnes512]

My votes:

• Loopback3: loopback-legacy
• Loopback4: loopback-framework