Update Bootstrap to 3.1.1

[moderndeveloperllc]

No description provided.

[Maks3w]

There is no reason for upgrade the library. Developers can upgrade or remove it for his own needs.

[akrabat]

Given that we upgraded Skeleton from 2 to 3, why not go to 3.1?

[Maks3w]

Have sense to have up to date every library?

Jesus, even assets library are most updated than zf2 submodule.

IMO we don't need to change any asset library except if there is a change in the design or is fixing some big bug

[fadoe]

Why don't use Components?

[ArnaudLigny]

https://github.com/components/components + https://github.com/RobLoach/component-installer + https://github.com/components/bootstrap

[Maks3w]

The aim of this repo is provide a skeleton of the project. Something very basic so you can test your installation is working and a couple of examples for help you to start modifying the code.

Add more complexity (like add more package managers) is out of the scope.

[akrabat]

Well... it's supposed to be the start of your project.

[Ocramius]

The repository could be cleaned up by using some bower/npm approach for asset management. That would relieve us from updating the project continuously (which, as you have noticed from the comments above, is quite useless), but the problem is that:

• if we use composer components (which is still a bad practice IMO, until asset management via composer is formalized), then we force people to use composer (the current skeleton doesn't do that)
• it adds up to the requirements to install the skeleton
• it requires more and more learning for the end user
• nodejs + windows is a terrible combo.

So yeah, no real need to upgrade something that is usually deleted anyway by those who want to use bower or other package management systems to handle assets.