• strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of image_attach_views_handler_field_attached_images::pre_render() should be compatible with views_handler_field::pre_render($values) in /kunden/96976_23554/relaunch/sites/all/modules/image/contrib/image_attach/image_attach_views_handler_field_attached_images.inc on line 111.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of date_plugin_display_attachment::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 33.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • strict warning: Declaration of date_handler_field_multiple::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/date/date_handler_field_multiple.inc on line 171.
  • strict warning: Declaration of views_handler_filter_term_node_tid::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/views/modules/taxonomy/views_handler_filter_term_node_tid.inc on line 303.
  • strict warning: Declaration of date_api_filter_handler::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 553.
  • strict warning: Declaration of date_api_filter_handler::options() should be compatible with views_object::options() in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 553.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method view::load() should not be called statically in /kunden/96976_23554/relaunch/sites/all/modules/views/views.module on line 879.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 24.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 25.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 26.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 28.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 29.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 30.
  • warning: Attempt to modify property of non-object in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_plugin_display_attachment.inc on line 31.
  • warning: Creating default object from empty value in /kunden/96976_23554/relaunch/sites/all/modules/date/includes/date_api_filter_handler.inc on line 37.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 557.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /kunden/96976_23554/relaunch/sites/all/modules/date/date_api_sql.inc on line 558.
Diskussionsbeitrag von Avanti in der aktuellen ak-Ausgabe

Radikale Linke und solidarische Moderne

Seine öffentliche Beachtung verdankt das ISM nicht dem Anspruch, "Denkfabrik" zu sein, sondern der Tatsache, dass es von prominenten VertreterInnen der SPD, der Grünen und der Linkspartei ins Leben gerufen wurde, namentlich vor allem von Andrea Ypsilanti, Sven Giegold und Katja Kipping. "Die gemeinsame Suche nach Alternativen ist ein entscheidender Beitrag dazu, dass aus der ... gesellschaftlichen Mehrheit wieder eine politische Mehrheit in demokratischen Wahlen wird", heißt es im Gründungsaufruf des ISM.

Es geht also um die ideologische und diskursive Vorbereitung einer künftigen rot-rot-grünen Regierung. Während dieses Projekt für SPD und Grüne tatsächlich eine Linksverschiebung wäre, müsste dafür in der Linkspartei vor allem der innerparteiliche Widerstand gegen die Orientierung auf Regierungsbeteiligungen (und gegen die dafür notwendige inhaltliche Rechtsverschiebung) überwunden werden.

Die objektive Funktion des ISM besteht in diesem symbolischen Dammbruch für Rot-Rot-Grün. Sie drückt sich schon in der Schwammigkeit des Gründungsaufrufs aus. In ihm werden zwar viele richtige Fragen aufgeworfen, aber belastbare Positionierungen fehlen weitgehend. Darin geht es viel um Diskurs und Ideologie, aber "Interessen", "Kräfteverhältnisse" oder "Klassen" tauchen nicht einmal als Begriffe auf. Die schüchterne Kapitalismuskritik reduziert sich allein auf Fragen der Verteilung; eine Problematisierung der gesellschaftlichen Macht des Kapitals unterbleibt.

Das Konzept der Bewegungs-partei ist grundfalsch

Noch viel offensichtlicher ist dieses schwammige Herumlavieren in der Haltung zu Kriegsbeteiligungen, der Gretchenfrage für eine rot-rot-grüne Koalition auf Bundesebene. Das ISM will eine "gerechte Welt ..., in der Konflikte friedlich gelöst werden" und fragt: "Wie könnte ein nicht-militärisches Verständnis von Sicherheit aussehen?" - das ist die gesamte Positionierung zu Krieg und Frieden auf sechs Seiten Grundsatztext.

Eine Position gegen militärische Auslandseinsätze der Bundeswehr? Wenigstens ein Bekenntnis zur deutlichen Reduktion von Rüstungsausgaben? Fehlanzeige. In das Gründungspapier der ISM sind bereits die Hintertürchen eingeschrieben, durch die die Beteiligten schlüpfen können, wenn es um die Beteiligung an der Regierungsmacht geht.

Die Bewegungen und die radikale Linke haben dagegen ein vitales Interesse an einer Linkspartei, die an der Frage von Krieg und Frieden, in der Sozialpolitik oder in anderen Fragen der "Staatsräson" linke Standpunkte nicht verlässt, um an die Fleischtöpfe der Macht zu gelangen. Dies vor allem deshalb, weil jedes Abrücken von diesen zentralen Prinzipien die Glaubwürdigkeit und Mobilisierung nicht nur der Linkspartei, sondern der Linken insgesamt beschädigt. Im ISM versammeln sich nun gerade nicht diejenigen Strömungen, die sich in dieser Frage besonders links positionieren.

Im Entwurf der Linkspartei für ihr neues Programm findet sich der bemerkenswerte Satz: "Sie (DIE LINKE, ak) wird sich an keiner Regierung beteiligen, die Privatisierungen vornimmt, Sozial- oder Arbeitsplatzabbau betreibt. Darüber hinaus wird sich DIE LINKE auf Bundesebene nicht an einer Regierung beteiligen, die Kriege führt und Kampfeinsätze der Bundeswehr im Ausland zulässt, die Aufrüstung und Militarisierung vorantreibt."

Unsere Solidarität sollte denjenigen in der Linkspartei gehören, die diesen Anspruch auch dann noch verteidigen, wenn rechnerische Mehrheiten Rot-Rot-Grün möglich machen, aber die Zustimmung zu oder die Duldung von Kriegseinsätzen der Bundeswehr zum Prüfstein der "Regierungsfähigkeit" erhoben wird. Jetzt schon die Bedingungen der Zusammenarbeit auszuhandeln - und sei es auch als intellektuelles Projekt der Diskursbeeinflussung - ist leider das Gegenteil davon und untergräbt diese Abwehrkräfte.

Dabei hängen wir keineswegs der Illusion an, die Linkspartei solle eine "Bewegungspartei" werden, sondern finden dieses Konzept im Gegenteil grundfalsch. Die Unabhängigkeit der Bewegungen, ihre sowohl von linken Wahlparteien als auch von revolutionären Organisationen klar unterschiedene Eigenlogik muss auf jeden Fall erhalten und verteidigt werden. Bewegungen sind Orte, an denen organisierte Linke unterschiedlicher Strömungen, radikale und moderate, mit unorganisierten "Bewegten" zusammenkommen und an denen das notwendige Moment der Spontaneität zur Geltung kommt. Der Versuch, diese Vielfalt und diese Logik in einer Partei abzubilden, muss scheitern und würde die Bewegungen zerstören.

Natürlich kann der Druck auf die Linkspartei zur Regierungsbeteiligung immens groß werden, sowohl aus den Reihen der FunktionärInnen, die Posten und (die Illusion von) Gestaltungsspielraum vor Augen haben, als auch von vielen WählerInnen, die erwarten, dass mögliche politische Mehrheiten genutzt werden, um wenigstens einen Teil ihrer Interessen umzusetzen. Dennoch bleibt es richtig, sich diesem Druck zu widersetzen (der ja letztlich nichts anderes ist als die Integrationskraft der bürgerlich-kapitalistischen Demokratie) und immer wieder zu erklären, dass reale Veränderungen nur von "unten", also durch starke und radikale Bewegungen, durchsetzbar sind.

"Doppelherrschaft" ist eine Option revolutionärer Politik

Für uns ist die Debatte um das ISM noch aus einem ganz anderen Grund relevant: Einer der fünf VorstandssprecherInnen ist Thomas Seibert, prominenter Aktivist der Interventionistischen Linken (IL). Zwar sagt er, dass er "nicht als Vertreter der IL im ISM" sei, aber dennoch wurde die IL durch die Übernahme der Sprecherfunktion fälschlicherweise in die Nähe des ISM gerückt.

Es geht jedoch um mehr als dieses kleine Ärgernis, nämlich um sehr grundsätzliche strategische Fragen: Um die Frage von Reform und Revolution, um das Verhältnis von (radikalen) Linken zum Staat und zu Regierungsbeteiligungen, um Bewegung, Partei und Parlamentarismus. Und diese Fragen muss eine radikale Linke - völlig unabhängig vom ISM - tatsächlich beantworten können, wenn sie gesellschaftlich handlungsmächtig werden will.

So fordert Thomas Seibert z.B., dass die ",Machtfrage` in der außerparlamentarischen Linken breit diskutiert wird - und zwar nicht im Sinne einer ,Übernahme` der Macht, sondern präzise um das Verhältnis von gegenstaatlicher oder staatsferner Macht einerseits, staatlicher oder staatsnaher Macht andererseits". (ak 547) Das sei eng verbunden mit Vorstellungen einer "Doppelherrschaft" in der "strategischen Verbindung einer ,regierenden` und einer ,kämpfenden` Linken" sowie der These, dass unter den Bedingungen des Empire "die überkommene Entgegensetzung von Reform und Revolution definitiv nicht mehr sinnvoll" sei. (Luxemburg 1/2010)

In unserem Verständnis bezeichnet der Begriff der "Doppelherrschaft" eine Option revolutionärer gesellschaftlicher Transformation (Nicos Poulantzas spricht z.B. von einer "radikalen Transformation des Staatsapparats", verbunden mit der "Entfaltung von Formen der direkten Demokratie" und Selbstverwaltung, betont dabei allerdings die gemeinsame Zielsetzung als Kampf gegen den kapitalistischen Staat). Allerdings sind immer noch andere Formen revolutionärer Veränderung denkbar, beispielsweise der Zusammenbruch bzw. die aktive Zerstörung des bürgerlichen Staates, verbunden mit dem Aufbau alternativer Institutionen und Formen revolutionärer Gegenmacht, von denen wir uns nicht vorschnell und undiskutiert verabschieden sollten.

In jedem Fall kann von "Doppelherrschaft" nur dann die Rede sein, wenn es unsere Seite des Doppels - also die Stärke der außerparlamentarischen Linken in ihren Organisationen und in den Bewegungen - als reale, irgendwie ebenbürtige Gegenmacht überhaupt gibt. Das Zusammenspiel von Bewegungen und Linken im Staatsapparat im Sinne der "Doppelherrschaft" (also mit starken transformatorischen Zügen hin zum revolutionären Bruch) ist angewiesen auf die Existenz starker sozialer Bewegungen und starker revolutionärer Parteien bzw. Parteiströmungen - beides ist aktuell in der BRD nicht gegeben

Poulantzas betont diesen Punkt: "Auf alle Fälle ... setzt die Verwirklichung dieses Weges und ihrer Ziele sowie die Verbindung beider Vorgehensweisen, durch die der Etatismus und die sozialdemokratische Sackgasse verhindert werden sollen, eine entscheidende und kontinuierliche Unterstützung durch eine Massenbewegung voraus, die sich auf breite Volksbündnisse gründet. Wenn es diese entfaltete und aktive Bewegung ... nicht gibt und wenn es der Linken nicht gelingt, diese Bewegung hervorzurufen, wird nichts die Sozialdemokratisierung dieses Experiments verhindern können." (1)

Ohne den starken Druck von Bewegungen läuft gar nichts

Wer versucht, Erfahrungen des Zusammenspiels von sozialen Bewegungen und Regierungsprojekten in Lateinamerika (Venezuela, Bolivien) auf die kapitalistischen Metropolen zu übertragen, erliegt einer fatalen Fehleinschätzung. Entscheidend ist nämlich, dass ein realer Transformationsprozess in Gang gesetzt wird - also eine "Ausweitung effektiver Brüche" (Poulantzas ) innerhalb des Staatsapparats als Folge einer Veränderung der Kräfteverhältnisse. Dies ist angesichts der relativen Schwäche der radikalen und außerparlamentarischen Linken und der sozialen Kämpfe in Deutschland eine völlige Illusion. Es gibt weder starke soziale Bewegungen noch starke revolutionäre Kräfte in den Parlamenten, da wohl weder SPD oder Grüne noch die Mehrheit der Linkspartei ernsthaft als solche bezeichnet werden können.

Daher wird das ISM - sollte es über die symbolische Koalitionsvorbereitung hinaus überhaupt nennenswerten Einfluss auf die Programmatik der drei Parteiführungen nehmen - bestenfalls auf eine neue sozial-ökologische Regulation des Kapitalismus hinsteuern und damit nicht mehr als ein modernisiertes sozialdemokratisches Projekt betreiben. Das kann vielleicht "links" genannt werden, wird für antikapitalistische, revolutionäre Politik aber keine Spielräume eröffnen, sondern tendenziell eher kontraproduktiv wirken.

Auch das Hoffen auf krisenhafte Zuspitzungen wird daran kaum etwas ändern; im Gegenteil ist zu befürchten, dass rot-rot-grüne Regierungen ohne eigene Substanz und ohne den starken Druck von Bewegungen nicht einmal sozialreformistisch sein werden. Wir haben in Berlin oder Brandenburg bereits gesehen, welche Kräfte sich in der Linkspartei durchsetzen, wenn es um eine Regierungsbeteiligung geht. Schließlich werden es erneut die "linken Parteien" sein, die soziale Einschnitte, Kriegseinsätze etc. durchsetzen werden. Wenn dies geschieht, dann dürfen wir nicht zu Komplizen dieser Politik geworden sein, sondern müssen vielmehr eigene Aktions- und Organisierungsangebote formulieren.

Thomas Seibert schlägt vor, das Verhältnis von sozialen Bewegungen, außerparlamentarischer und parlamentarischer Linken nicht harmonisierend, sondern "unvermeidlich konfliktiv" (ak 547) zu denken, nämlich so, dass die Akteurinnen und Akteure "getrennt bleiben, je ihrer eigenen Logik folgen - und sich trotzdem aufeinander abstimmen". (ak 548) Das klingt wie die Fortsetzung des richtigen und von uns explizit geteilten Konzepts der "strategischen Bündnisorientierung", nach dem Bündnisse und Koalitionen mit AkteurInnen sowohl der radikalen wie der moderaten Linken nicht nur notgedrungen und auf Zeit geschlossen werden sollten, sondern die Dauerhaftigkeit und die bewusste Bejahung dieser Bündnisorientierung die Voraussetzungen für die Schaffung gesellschaftlicher Gegenmacht sind.

Diese Überlegung geht aber einen entscheidenden Schritt darüber hinaus, indem bei Thomas Seibert - trotz der Anerkennung der Konflikte und notwendigen Widersprüche - die inhaltlichen Unterschiede zwischen radikaler und moderater Linker verwischt werden. Es sind nicht nur die "Modi" von "Spontaneität, Kalkül und Autonomie", deren jeweilige Betonung uns unterscheidet.

Wir haben uns nicht beliebig oder zufällig für das Projekt der linksradikalen Organisierung entschieden. Der ausschlaggebende Unterschied bleibt das Bekenntnis zur Notwendigkeit des Bruchs mit dem Kapitalismus und seiner - in welcher Form auch immer vollzogenen - revolutionären Überwindung. Das ist keine Frage des Modus, sondern der Analyse.

"Machtfrage" muss für die radikale Linke immer bedeuten, reale Gegenmacht aufzubauen, um die ökonomische und politische Macht des Kapitals zu brechen. Dazu gehört zu allererst, diese Gegenmacht nicht mit Regierungsmacht zu verwechseln. Denn die Macht des Kapitals ist ja ebenfalls nicht von der konkreten Parteienzusammensetzung der nächsten Bundesregierung abhängig.

Avanti - Projekt undogmatische Linke, Mai 2010

Links

Soziale Kämpfe

Bremen

Berlin

Hamburg

Geschlechterverhältnisse

Antifaschismus

Bundesweit

International

Kiel

Hannover

Antira

Klima

Uni

Avanti

Krieg

Hamburg; Bundesweit

Frankfurt / bundesweit

Bundestweit