I think we need to split this discussion to distinct topics:
This answer is sort of a brain dump
1. Renaming of Resource and Object entities
- Resource is a persisted entity
- Object is a DTO, used internally in the “Resource bounded context”, it’s not part of the public API and should be easy to rename.
Object Storage is a really common naming in the cloud industry, so I can understand why we have the current name. Not sure if File === Resource is exact in this context. By ex. in our case a Video === File !== Resource, because a Video is compose by multiple Resource. A big file can also be splited in multiple Resources.
Who say naming is hard
2. Package naming (understand product name)
I see this one as the most complex, and need discussion, because we will communicate on the product (Fluid, TypoScript, CR, Form, …) and this is the visible part of our Iceberg for the outside world
But in this discussion we have so hidden gems, like did we rename Fluid to something else and split more with the T3 universe ?
Basically we have two option use simple work (Template, Media, Content Repository, Form, …) all under the Neos umbrella / namespace. Or invent fancy name for all our technologies. I’m in favor of simplicity here, and found the simple “word” the most effective.
If I remember correctly the state of the last discussion, we agree on Neos is the Vendor, so all namespace should start with
Personally I will try to avoid
\Neos\Neos in favor of
\Neos\Core for the core CMS feature. Fine to have
\Neos\Flow\. For the media package,
\Neos\Media\MediaBrowser in two distinct package.
What about create one thread per discussion before this one start to be out of control ?