Add opinion of SchumacherFM

Milestone/2/index.md

@@ -30,6 +30,7 @@ voting:
 * gperriard (-)
 * ajbonner(+)
 * brenbl(-)
+* SchumacherFM(+)
 *
 
 ### Solution 2
@@ -51,6 +52,7 @@ voting:
 * gperriard (+)
 * ajbonner (-)
 * brenbl (-)
+* SchumacherFM (-)
 *
 
 ### Solution 3
@@ -123,5 +125,5 @@ maderlock: I'm with avstudnitz. There are parts of the current integration that
 
 ajbonner: First thing, I don't like the idea of trying to support magento 1 & 2 within the same tool. As mentioned magento 2 fixes a lot of the problems that make composer integration hard and I think it will needlessly complicate the codebase. I feel there should be a composer installer for mage 1, and a version for mage 2, they can share some code, but they ultimately should be two different projects. As per the above comments, I can't see Magento 1 going anywhere anytime soon. I know my company wont adopt magento 2 anytime soon and large e-tailers are not going to be able/want to move quickly to mage2. Composer and composer installer offer such big wins for managing dependencies that it would be a shame too if development simple ceased or slowed down for it in favour of mage 2. So I hope that the problems that exist within composer installer can be looked at as it will benefit more people in the medium term that work that benefits mage 2.
 
-
+SchumacherFM: +1 for ajbonner