bug tracking - alert project - fossa2011

21
Clara Pezuela, ATOS BECAUSE, YOU DON’T HAVE TO WORRY!

Upload: fossa-free-open-source-software-academia-conference

Post on 18-Nov-2014

467 views

Category:

Technology


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Bug tracking - alert project - fossa2011

Clara Pezuela, ATOS

BECAUSE, YOU DON’T HAVE TO WORRY!

Page 2: Bug tracking - alert project - fossa2011

Table of Contents

� Project context

� Project objectives

� Research challenges

� Project solution

� Target users

� Expected impact

� Project sustainability

� Project info

Page 3: Bug tracking - alert project - fossa2011

Project context

� Many developers working together on the same code

� Using communication tools (mail, chat, forums)

� Lack of awareness of others’ work� Lack of awareness of others’ work

� No native English

� Diverse skills and expertise

� Many users using the code and reporting bugs

� Frequent duplicated bug reports

� Bug not well explained

� Not properly assigned to the right developer

Page 4: Bug tracking - alert project - fossa2011

Project context

� As consequence: a bug that may require a simple modification takes long time in resolution due to the lack of coordination among developers

� Open Source communities experiment this continuouslycontinuously

� The problem is extensive to any group of developers working in a collaborative development environment

ALERT will improve the coordination among developers in Open Source communities by providing methods and tools

based on context-aware notification, event-driven processing and real-time interactions

Page 5: Bug tracking - alert project - fossa2011

Project objectives

� O1: Efficient modeling of the more reactive coordination− R1.1: ALERT ontologies

− R1.2: Conceptual model of an (re)active collaboration platform

� O2: Efficient management of the awareness of team members− R2.1: Model for declarative specification of alerts

− R2.2: Intelligent, pattern-based engine− R2.2: Intelligent, pattern-based engine

� O3: Efficient management of information− R3.1: Module for integration of information from structured sources

− R3.2: Module for extracting knowledge from unstructured sources, semi-automatic annotation and summarization

− R3.3: Interaction highway set of services

� O4: Personalized and task-based access to information− R4.1: Module for capturing explicitly or implicitly the interest/expertise

− R4.2: Module for capturing relevant information for the task at hand

� O5: Pilot, evaluate and impact the ALERT system in three important open source communities ( OW2 (Petals), KDE and Morfeo)

Page 6: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

-- How to coordinate and maintain How to coordinate and maintain awarenessawareness of community activities?of community activities?The information and interactions relating to the bug were located in multiple artefacts with

no links. Thus, a duplicate bug was filed.

Page 7: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

-- How to coordinate and maintain How to coordinate and maintain awarenessawareness of community activities?of community activities?The information and interactions relating to the bug were located in multiple artefacts with

no links. Thus, a duplicate bug was filed.

Page 8: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

-- How to How to interpret (understand) interpret (understand) communication?communication?There is a lack of coherence that hinders developers in making sense of communications from

others, or that produces unintended information filtering or misunderstandings.

Page 9: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

-- How to How to interpret (understand) interpret (understand) communication?communication?There is a lack of coherence that hinders developers in making sense of communications from

others, or that produces unintended information filtering or misunderstandings.

Page 10: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

--How to identify expertise? How to identify expertise? The bug was assigned to/noticed first by someone

without expertise in the area of the bug

Page 11: Bug tracking - alert project - fossa2011

Research challenges

Bob asks about Nepomuk

Mike confirms Mike reports on forum

Mike links to 253312

Dirk asks Andreas how to fix bug

Andreas suggests Mike’s fixJohn reports a bug

12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct

Bob notices the bug

Bob asks for explanation

John replies …

IRC

1st Aug 25th Aug 1st Sep

Disc 1

253312

253320

Disc 2

Bob posts problem on mailing list

Alice also reports problems

Mike files bug

Bob asks to check …

Alice posts …

Dirk files bug, posts details

Dirk asks on IRC

Lora discusses bug

Dirk posts a fix

Andreas remarks …

Dirk asks for explanation

Dirk applies Mike’s fix

IRC

IRCIRC

--How to identify expertise? How to identify expertise? The bug was assigned to/noticed first by someone

without expertise in the area of the bug

Page 12: Bug tracking - alert project - fossa2011

How will the ALERT system address the identified challenges?

INTERPRETATIONINTERPRETATIONINTERPRETINTERACTION

Information source 1

Information source 2 I.s. 3

I.s. n

continuous push of

changes

AWARENESSAWARENESS

INTERPRETATIONINTERPRETATION

TASK ASSIGNMENTTASK ASSIGNMENTAUTOMATIC ASSIGNMENT

CREATE AWARENESS

INTERPRETINTERACTION

HIGHWAY

Developer 1

Developer 2

Developer m

complex

subscriptions

preferred

information

Page 13: Bug tracking - alert project - fossa2011

Project solution: conceptual architecture

Page 14: Bug tracking - alert project - fossa2011

Project solution: conceptual architecture

Knowledge

extractor from

structured source

Create, store and

manage the semantic

ally-enriched info

Knowledge extractor

from unstructured

source

Discover interesting

situations

identify developers

and create/update

their profiles

enable developers to

describe situations

relevant for notification

execute actions related

to the detected

situations

Specify needs and

provide support

Suggest the best

developer for a bug

Page 15: Bug tracking - alert project - fossa2011

Target users

� Initially the project was conceived to improve the bug resolution in Open Source communities

� The analysis of the potential markets has provided a new target market: the software industryindustry

� Research community will also benefit from project results (publications, documentation, concepts, etc)

Page 16: Bug tracking - alert project - fossa2011

Expected impact (I)

� Open Source communities may benefit from ALERT in:

� Obtaining a better integration of issue information

sources

� Obtaining an enhanced understanding of issues in the � Obtaining an enhanced understanding of issues in the

software and the relationships between them

� Improving the coordination by correctly allocating

issues to teams and identifying developers with the

expertise to resolve them

Page 17: Bug tracking - alert project - fossa2011

Expected impact (II)

� Software industry may benefit from ALERT in:

� A better management of developers’ teams

� Alternative open source tools to traditional proprietary software development management toolstools

� Improve the maintenance of code in high demanding software systems

Page 18: Bug tracking - alert project - fossa2011

Project sustainability

� Build a community of interest around the ALERT portal

� Looking for contributors to evolve the software after the end of the project

� Offering advance services over the delivered � Offering advance services over the delivered components

� Keeping alive the publication of news, blogs about project partners

Page 19: Bug tracking - alert project - fossa2011

Sustainability Plan

Community

building

� will have a place to obtain useful information, download the components, find the right partner for support and maintenance… etc.

Users

� will sponsor an specific site where their own components are shown, a new marketing channel to announce their organization and services, a new channel to obtain new clients….

Project Partners

Page 20: Bug tracking - alert project - fossa2011

Project info

� Project contact: [email protected]

� Project web site: www.alert-project.eu

� Twitter: @alertfp7

� Linkedin: ALERT-project� Linkedin: ALERT-project

� Newsletter:

http://www.alert-project.eu/newsletter/subscriptions

Page 21: Bug tracking - alert project - fossa2011

www.alert-project.eu