Project objectives

  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /var/www/projectportal2/sites/all/modules/contribute/views/plugins/views_plugin_style_default.inc on line 24.
  • strict warning: Declaration of calendar_plugin_display_page::options_submit() should be compatible with views_plugin_display_page::options_submit(&$form, &$form_state) in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_plugin_display_page.inc on line 297.
  • strict warning: Declaration of calendar_plugin_display_page::options() should be compatible with views_object::options() in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_plugin_display_page.inc on line 297.
  • strict warning: Declaration of calendar_plugin_display_block::options() should be compatible with views_object::options() in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_plugin_display_block.inc on line 78.
  • strict warning: Declaration of calendar_plugin_display_attachment::options_submit() should be compatible with views_plugin_display_attachment::options_submit(&$form, &$form_state) in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_plugin_display_attachment.inc on line 242.
  • strict warning: Declaration of calendar_plugin_display_attachment::options() should be compatible with views_object::options() in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_plugin_display_attachment.inc on line 242.
  • strict warning: Declaration of date_handler_field_multiple::pre_render() should be compatible with content_handler_field_multiple::pre_render($values) in /var/www/projectportal2/sites/all/modules/contribute/date/date/date_handler_field_multiple.inc on line 185.
  • strict warning: Declaration of calendar_view_plugin_style::options() should be compatible with views_object::options() in /var/www/projectportal2/sites/all/modules/calendar/includes/calendar_view_plugin_style.inc on line 173.
Project objectives

The aim of the ALERT project is to develop methods and tools that improve FLOSS coordination by maintaining awareness of community activities through real-time, personalized, context-aware notification. ALERT will create an active collaboration platform, i.e. a virtual actor would interact with other developers, process and recognize various kinds of interactions, suggest actions on the basis of these and remember and bring past interactions into the developers’ attention, thus enabling developers to work better together. The main objectives of the project are:

  • Efficient modelling of the more reactive coordination in FLOSS development that will improve the awareness of the group work and the responsiveness of individuals.
  • Efficient management of the awareness of team members that will enable interesting parties to be notified based on their interest/expertise as soon as something relevant happens without overloading them, interfering with and slowing down their work.
  • Efficient management of information relevant for FLOSS teams, including the semantic integration of information and its flow between all stakeholders that will support better understanding of the situations which a developer should react on.
  • Personalized and task-based access to information, by allowing developers to focus on activities to be performed to achieve a specific shared task and/or by including information about the presence and activities of other developers in the FLOSS.
  • Pilot, evaluate and impact the ALERT system in three important FLOSS communities (OW2, KDE and Morfeo) and disseminate the results in other FLOSS and relevant research communities.

In order to achieved the above mentioned objectives, following research outcomes will be produced:

  • Set of ontologies that model the conceptual dependencies between community, content and interactions.
  • Conceptual model of an (re)active collaboration platform.
  • Model for declarative specification of alerts.
  • Intelligent, pattern-based engine that can correlate, aggregate, and filter events in order to provide triggers for relevant notifications.
  • Module for integration of information from structured and unstructured sources.
  • Interaction highway set of services (e.g. search, recommendation, visualisation, etc.).
  • Module for capturing explicitly or implicitly the interest/expertise of the developer.
  • Module for capturing relevant information for the task at hand.

Besides, three use cases will be instantiated to address the three relevant aspects in FLOSS coordination: awareness, communication and task assignment.