I would like to discuss our best practice suggestion for the folder containing the packages delivered with the distribution.
I originally used Source in my first experiment, Karsten suggested Sources but we talked about something with Packages in it, so now splash uses DistributionPackages and the example uses LocalPackages. Additionally ProjectPackages or BundledPackages could work as well. To have this written down a short poll to take a decision:
There was a poll here that unfortunately didn’t show voters and so was not good to use, but that original poll ended in src, we redid the poll to make sure we can separate team member votes, therefore the original poll has been removed now.
IMPORTANT LOOK FURTHER DOWN FOR POLL WITH PUBLIC VOTERS
Seems we have a preference for DistributionPackages finally so that will be the officially documented way.
Since this is a composer concept (of directory package repository) I don’t see why it’s necessary to come up with a best practice other than a description of the concept, and where to use the name you might choose.
It’s more of a documentation task of the concept “Mono repository” and how you (in general) organize a Flow project in terms of version control etc.
I’m strongly in favor of “DistributionPackages” since it is the most “correct” name - it’s the directory for the packages that come with the distribution itself. LocalPackages sounds like they could be only for local development or something along these lines.
I’m voting for Source: everytime I see a repository out there in the wild with a reasonable number of files in the root and I’m interested in the code I scan this directory for a src directory to look into.
This is (naming it src) the most common way in software development I would say.
I had another think about this, and decided that - for me - what @sorenmalling and @mstruebing said overrules the “correctness” of DistributionPackages. “Source” will be better understood by the majority, so changing my vote.
ED: Ironically, that makes “LocalPackages” come out ahead, which I like the least of the three
And then you run a composer install and then you are good to go? So, to keep “in sync” with other structures I would say that src is the correct usage, instead of coming up with a new convention. Then your repository will basically look like
As this is only to become a documented best practice, we could still change it at a late date, but for now seems “src” is the preferred path name. @mficzel would you change splash at some point? I will change my example repository.