New folder structure

[ihostage]

I propose the next folder structure:

├─ java
│  ├─ chatroom
│  ├─ compile-di
│  ├─ dagger2
│  ├─ ebean
│  ├─ fileupload
│  ├─ forms
│  ├─ grpc
│  ├─ hello-world
│  ├─ jpa
│  ├─ pekko-cluster
│  ├─ rest-api
│  ├─ starter
│  ├─ streaming
│  └─ websocket
└─ scala
   ├─ anorm
   ├─ chatroom
   ├─ compile-di
   ├─ fileupload
   ├─ forms
   ├─ grpc
   ├─ hello-world
   ├─ isolated-slick
   ├─ log4j2
   ├─ macwire-di
   ├─ rest-api
   ├─ secure-session
   ├─ slick
   ├─ starter
   ├─ streaming
   ├─ tls
   └─ websocket

[ihostage]

@mkurz WDYT?

[mkurz]

@mkurz WDYT?

We can do that. This samples repo was put together from single github repos (each samples lived in its own repo...).
However, is there a bigger plan why you want to do that? Is it "just" to better organize things or do you have something else in mind?

[mkurz]

Also if we do that we should not forget to update everything in https://github.com/playframework/play-samples/tree/main/.github (like scala-steward buildRoots, etc.)

[ihostage]

We can do that. This samples repo was put together from single github repos (each samples lived in its own repo...). However, is there a bigger plan why you want to do that? Is it "just" to better organize things or do you have something else in mind?

The main reason to me is to better organize and simplify maintaining, you are right. Current folder names have a duplicate context information that it's an example and it's a Play example. But I know it, because It's a play-samples repo, that why I want to drop play- prefix and -example postfix in folder names and group by language. Yes, this removing can drop this context for users, who download examples and java/dagger2 and other folders already look not related with Play. But this case I propose to solve by other approach (#569)

My goal, that this repo should be used only maintainers and no one else. The common user should download an archive and just play with it 😄

[mkurz]

👍