Composer and directory structure

Composer with discussed packages.
Directory structure:
- `features` - for behat scenarios
- `src` - for app logic
- `var` - for compiled templates and cache
- `web` - public directory
My argument would be that we are not going to be able to release a decent
and usable in less than 6 months/1 year, when 5.3 will be almost forgotten
and 5.4 at the end of its life.
Another thing is that I would like to avoid WP's mistake of wanting it to
be as retro compatible as possible, and we all know that WP is bad because
of this.

Target: as many people as possible, but starting with developers and people
in the technology field. If we weren't targeting them, we wouldn't have
gone for the 'modules' solution (non-developers don't even know what this
stuff is!).
On 3 Dec 2014 06:56, "Fabian Fülling" <notifications@github.com> wrote:

> In composer.json:
>
> > +	"name": "vox-project/vox",
> > +	"version": "v0.1",
> > +	"description": "The publishing platform",
> > +	"keywords": [],
> > +	"type": "platform",
> > +	"license": "MIT",
> > +	"authors": [
> > +		{
> > +			"name": "Marco Troisi",
> > +			"email": "hello@marcotroisi.com"
> > +		}
> > +	],
> > +	"minimum-stability": "dev",
> > +	"prefer-stable": true,
> > +	"require": {
> > +		"php": ">=5.3.4",
>
> I would just not go with PHP 5.3 as this is unsupported and old. Yes, many
> servers and - unfortunately devs - run 5.3, but are they the Vox target
> group? What's the target group by the way? :-)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/vox-project/vox/pull/3/files#r21213855>.
>