Open fulldecent opened 7 years ago
What parts of the phrasing do you feel need clarification?
Maybe I am reading it wrong, but extra information could be included such as:
If the package provides a root-level directory for web server files (e.g. index.php), it MUST be named public/.
If the package provides a root-level directory for PHP source code files (e.g. class definitions), it MUST be named src/.
Would a PR that fixes this be in scope to be merged?
Why in the world would you call the directory "src"? It makes no sense what so ever! There is no source code what so ever. There is PHP application code, which has nothing to do with source code.
Class definitions are classes, why not just call it what it is, "classes". There is no need to get clever about it.
Please clarify the difference between /public and /src.
A common setup is to use one index.php file to route requests to other parts of the project. Please address this setup specifically in the documentation.