[2.0] Plugin selection
Posted: Wed Mar 05, 2014 9:40 pm
As proposed by Garvin here, we might want to discuss the plugin selection for 2.0 from scratch and in a seperate thread.
We'll have to think about plugins which should be
a) “default bundled” (proposed tag: [db])
b) “default enabled” (proposed tag: [de])
in 2.0. I guess this means a) shipped with the core and b) active after installation. Keep in mind that (as far as I remember) in 2.0 it will be possible to install plugins upon (first) installation which are not actually part of the core but in Spartacus.
I guess we might also want to discuss plugins which might be removed from the core and/or not activated on installation to keep it tidy. Let's tag those [da] (“de-activate”).
YL
We'll have to think about plugins which should be
a) “default bundled” (proposed tag: [db])
b) “default enabled” (proposed tag: [de])
in 2.0. I guess this means a) shipped with the core and b) active after installation. Keep in mind that (as far as I remember) in 2.0 it will be possible to install plugins upon (first) installation which are not actually part of the core but in Spartacus.
I guess we might also want to discuss plugins which might be removed from the core and/or not activated on installation to keep it tidy. Let's tag those [da] (“de-activate”).
YL