OWF12/Alert project workshop


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

OWF12/Alert project workshop

  1. 1. ALERT in Open World Forum 2012 Paris October 12, 2012
  2. 2. How Automation &Notifications can help software development teams focus on building beautiful code
  3. 3. Agenda #AlertOWF12 Overview of ALERT Project ALERT Project ValueReal Use Cases of ALERT’s VALUE for: KDE Open Source Community Companies and the Forge market Petals Open Source Community Conclusions and Q&A Debate
  4. 4. ALERT ProjectLjiljana Stojanovicfrom FZI
  5. 5. ALERT IdentityALERT Active support and reaL-time coordination based on Event pRocessing in open source software developmenTFACTS Start 01 October 2010 Duration 30 months Total Budget 4,019,835.00 € EC Funding 2,948,856.00 € Consortium 9 Partners ALERT will improve the coordination among developers in Open Source communities by providing methods and tools based oncontext-aware notification, event-driven processing and real-time interactions
  6. 6. ALERT PartnersFZI Germany (Coordinator)URJC SpainAtos SpainCIM SerbiaCorvinno HungaryICCS GreeceIJS SloveniaKDE e.V. GermanyLinagora France
  7. 7. Why ALERT? Bob asks about Nepomuk Bob notices the bug Mike links to 253312 Mike confirmsJohn reports a Bob asks for explanation Dirk asks Andreas how to fix bugbug John replies … Mike reports on forum Andreas suggests Mike’s fix 1st Aug 25th Aug 1st Sep 12th Sep 16th Sep 20th Sep 24th Sep 28th Sep 3rd Oct 7th Oct 22nd Oct IRC Disc 1253312 253320 Bob posts problem on mailing list Alice also reports problems IRC IRC Mike files bug Disc 2 Bob asks to check … Alice posts … Dirk files bug, posts details Dirk asks on IRC Dirk asks for explanation Lora discusses bug Dirk applies Mike’s fix Dirk posts a fix Andreas remarks …
  8. 8. What is ALERT? Information source 1 Information source 2 I.s. 3 I.s. n continuous push of changes INTERPRET INTERACTION HIGHWAY CREATE AWARENESS AUTOMATIC ASSIGNMENT complex preferredsubscriptions information Developer 2 Developer 1 Developer m
  9. 9. Main Innovations (I)KNOWLEDGE EXTRACTION (from structured sources) Source Code Management Supported Systems CVS, SVN, GIT, Mercurial, Bazaar Bug Tracking Systems Supported Systems Bugzilla, Mantis, JIRAEXTRACTION OF COMMUNITY KNOWLEDGE Artifacts, community members and cross-linking of them Metadata includes a) references to code, files, packages, error traces, other bug reports and discussions, and (b) semantic conceptsDYNAMIC VISUALIZATION key descriptors of the project evolution
  10. 10. Main Innovations (II)KNOWLEDGE EXTRACTION (from unstructured sources) Semi-automatic construction of ontology related to computer science and software development Automatic methods for extending the ontology with domain specific terminology Annotation of text using Annotation ontology concepts using information from structured sources (references to bugs, methods, classes, …) Bug duplicate detection based on semantic information and meta data Searching based on various conditions e.g., keywords, people, products, classes, methods, time, …
  11. 11. Main Innovations (III)EFFICIENT MANAGEMENT OF RELEVANT INFORMATION Automatic Identification of developers across information sources Capturing of their competence using metrics of their activity Real-Time recommendations of developers, issues and components by combining developer competence and extracted
  12. 12. Main Innovations (IV)EFFICIENT MANAGEMENT OF THE AWARENESS OF TEAMMEMBERS enables interesting parties to be notified based on their interests/expertise as soon as something relevant happens graphical editor and model for specification of notification patterns enables representing the context during which (re)active behavior is relevant and the situations in which it is required Intelligent, pattern-based engine correlates, aggregates, and filters events in order to provide triggers for relevant notifications Action service provides different types of real-time notifications
  13. 13. ALERT Value PropositionOliver Barretofrom ATOS
  14. 14. ALERT actors1. Usersinteracting and using applications and systems2. Dev, Comm & Collaboration Toolsallowing interaction, communication, reporting and development processes3. Developerscoding, collaborating andsolving bugs
  15. 15. #FocusedCoding#CodeTogether _
  16. 16. ALERT is an Open Source project thataims to improve coordination,knowledge and bug resolutionprocesses in collaborative ordistributed environments by providingmethods and tools for SoftwareDevelopment Companies, Open SourceCommunities and Developers
  17. 17. Video
  18. 18. Automation & Notifications Talent Monitoringto find possible duplicates or related issues Improve task assignment & triageand notify relevant facts to developers processes on OSS Communities: assignwhen they occur developers based on skills , expertise and participationLive Project & Team Statusmore realistic picture of projects and Social Codingparticipation with info from multiple Automatically Create & Showsources developers profile Faster Team Interaction Reduce Time solving Bugs with Automation & Notification tools improve performance solving bugs and to keep developers updated searching for possible solutions Development Tools integrate sensors & help coders Multiple Data Sources concentrate on development instead gathers relevant info from multiple of manual repetitive tasks data sources (ITS, BTS, code repositories, blogs, forums, portals, eMail, etc.)
  19. 19. ALERT’s Value Proposition
  20. 20. Significantly reduce the amount of time spent by developers on solving issues, investigating and searching different sources for possible solutions with the automation & notification engine and data-collector sensors…… and create a new environment that helpcompanies reduce corporate legacycollaboration tools and embrace Web 2.0 tools.
  21. 21. ALERT provides Analysis tools to stay on top of the Project Status and Team’s Contribution… managers, teammanagers and evendevelopers can have anoverview of the project’sstatus
  22. 22. ALERT provides automated profile creation of expertise, skills and project contribution… for developers to show off and also formanagement and recruiting purposes
  23. 23. Social Coding: Companies such asAtlassian, Github, Geeknet orMasterBranch (a place fordevelopers to show off theirexpertise on the social coding trend)Talent Recruiting Firms: Companiessuch as LinkedIn or Monster, oreven software companies (a placefor companies that need to hiredevelopers to find real andspecialized talent)IT Sponsors: companies sponsoringOpen Source Tools such as Oracle,Ubuntu, etc. (integrating ALERT withOSS tools aiming to help teams &developers become more efficient)
  24. 24. Show a real Use Case: ALERT inthe ATOSClara Pezuelafrom ATOS
  25. 25. We are BIG, butwe love Open Source !!!
  26. 26. Innovation is part of the Atos DNA • Continuous improvement of development processes • Become a great place to work in and help ‘talent’ work on right places and projects • Embrace automation tools, web 2.0 and social media communication channels, reduce bureaucracy and draft the path to become a zero email corporation
  27. 27. detection of similar bugreports and improve team’sperformance when solving bugs andsearching for possible solutionshelp development teammanagers with more realistic Focused onpicture of the participation of teammembers on projects Processprovide effective Improvementinteractions betweenteams avoiding duplication of taskand reducing communication tools usewith automated events and notificationtools
  28. 28. help measure developers’ talent skills and work contributions on projects with no overhead work that can build a more accurate asset resource of skilled developers help developers concentrate on development making more easier the searching ofFocused on information in projects The Team help developers have access to centralized information sources, collaboration and notifications tools that reduces time spent on unproductive tasks in a more integrated manner with their current development tools and IDEs.
  29. 29. Show a real Use Case: ALERT inthe KDE Open SourceCommunityDario Freddi &Stuart Jarvisfrom KDE
  30. 30. A Big Community... KDE software users: millions
  31. 31. A Big Community... Commits: 2000-2500 weekly
  32. 32. A Big Community... Active developers: 200 weekly
  33. 33. A Big Community... Commits: Over 100 000 annually
  34. 34. ...With Issues Last week: 274 issues resolved
  35. 35. ...With Issues Last week: 284 issues reported
  36. 36. ...With Issues Total issues: 250 000
  37. 37. ...With Issues Open issues: 21 420
  38. 38. ...With Issues Open issues: 107 per developer
  39. 39. ...With Issues Known duplicate issues: 20%
  40. 40. ...And FragmentationIssue discussion: in issue tracker
  41. 41. ...And FragmentationIssue discussion: in developers mail lists
  42. 42. ...And FragmentationIssue discussion: in users mail lists
  43. 43. ...And FragmentationIssue discussion: in user forum
  44. 44. The Big Picture Do issues go to the right person?
  45. 45. The Big Picture Can new developers find a task?
  46. 46. The Big Picture Does our community grow or shrink?
  47. 47. The Big Picture Does a change cause issues? º
  48. 48. The Big Picture Does our software get better or worse?
  49. 49. The Developer PerspectiveDario Freddi, developer, KDESolid Project
  50. 50. The Developer PerspectiveSolid abstracts awayhardware libraries
  51. 51. The Developer PerspectiveSolid abstracts awayhardware librariesUsed widely in KDE software
  52. 52. Interaction Across TeamsSolid touches lots of other areas in KDE
  53. 53. Interaction Across TeamsHow do you know who to contact?
  54. 54. Confused UsersNot familiar with theunderlying technology
  55. 55. Confused UsersNot familiar with theunderlying technologyUnsure where to reportissues
  56. 56. Confused UsersNot familiar with theunderlying technologyUnsure where to reportissuesMay report againstthe wrongsoftware
  57. 57. Inefficient DevelopmentHow do non-Solid developers get help...
  58. 58. Inefficient Development...with Solid related issues?
  59. 59. Inefficient DevelopmentHow do Solid developers find issues...
  60. 60. Inefficient Development...reported in the wrong place?
  61. 61. The SolutionAided duplicate identification toclean up our issue tracker
  62. 62. The SolutionAided single view of information on anissue from many sources
  63. 63. The SolutionAssistance finding the right developerto help to solve any issue
  64. 64. The SolutionHelp finding issues you can fix, evenwhen reported in the wrong place
  65. 65. The SolutionOverviews and alerts on trends inactivity, issue solving and introduction
  66. 66. The SolutionA chance to improve the way we workand make KDE software better
  67. 67. ALERT as a resource toimprove softwaredevelopmentJesús M. González- Barahonafrom Libresoft/URJC
  68. 68. Items to be discussed How can Alert be used Alert as a componentAlert complementing a software forge
  69. 69. How can ALERT be used?Standalone (via its own user interface, via scripts or APIs)In combination with forges, IDEs (linking or embedding)As a component of larger systems (in the background, in the foreground)
  70. 70. Standalone (UI)
  71. 71. Standalone (REST API)
  72. 72. In combination (forge, IDE)Annotating the forge with: links / pop-ups to Alert embedded information from Alert notifications from AlertComplementing the IDE with: plugin for searching Alert information plugin for providing complementary information in the IDE
  73. 73. As a component
  74. 74. As a component Imagine a dashboard integratingImagine a information fromdebugging many sourcessystem including Alert...embedding Alertuser interface
  75. 75. Complement to a forgeAnnotate every ticket with relevantinformation potential duplicates tickets suggested for fixing developer comment for fixing commitNotify developers events of interest suggested bugs to fix areas of code being changed
  76. 76. Complement to a forge (ii) Convert the forge in an active system Interacting with developers Providing notifications to stakeholders Allowing for detailed custimization (e.g.: Im interested in...)
  77. 77. Complement to a forge (iii) Improve developer... productivity awareness knowledge allocation
  78. 78. How can Alert be used?Standalone (via its own user interface, via scripts or APIs)In combination with forges, IDEs (linking or embedding)As a component of larger systems (in the background, in the foreground)
  79. 79. Show a real Use Case: ALERT inthe LINAGORA Open SourceCommunityLaurent Lacotefrom Linagora
  80. 80. ALERT and the open source communities What is it good for? 1) The Petals use-case 2) From Petals to LINAGORA 3) Stay ALERT, youre on a gold mine!
  81. 81. Petals use-case General thoughts on communitiesSpecific issues of Petals community Expected benefits of ALERT Evaluation plan
  82. 82. What are Open Source communities? numerousBazaar gathering people with various skills, whoinvest more or less of their time in a project anduse different methodologies and tools. What could be ALERT useful for?
  83. 83. The initial case: Petals, orthe difficult life of adetective.- for Users- for Developers Developers
  84. 84. What will it be tomorrow?“Dont fret, dear Petals community member, thesystem stays ALERT for you!”- aggregation system- notification system Lets see how it will change our life!
  85. 85. 1. Creates Before ALERT 8. Sets #1000 as duplicate Bug #1000 and closes it. Jira Bug Tracking System Developer 5. Finds Solution for Bug #1000 in old bug #600User 3. Notification on 2. Creates new post is sent new post #CCC 4. Suggests Nabble relationship Forum with bug #600 6.Confirms that solution in 7. Notification on update #600 is working for #1000 is sent
  86. 86. With ALERT 6. Sets #1000 as duplicate 1. Creates #1000 and closes it. 3. Checks #600, finds solution... Jira Bug Tracking System 4. And confirms that it works. Developer 2. Sends similarity alert to User (& maybe Developer)User ALERT Because you dont have to worry ;) 5. Sends notif of update on issue #1000 to Developer Nabble Forum 6.Confirms that solution in 7. Notification on update #600 is working for #1000 is sent
  87. 87. “Hey, whats the deal? Only 2 steps less? Its notworth our time!”Really?- globally faster processing- significant gain in users autonomy- much room for further improvement Imagine the power with expanding ALERT database and future versions!
  88. 88. Whats here today:- custom notification system- similarity detection post-creation- developer profilesWhats here tomorrow:- notification models- tight integration with major ITS: tackle theduplicate before its even actually created!- ...
  89. 89. “Ok, its nice, but are you sure it works?”We dont know for sure yet, but eager to set ourevaluation plan in motion!- variety of profiles- 4 steps testing: hands-on, teaching, use-cases,free use- predefined tests + feedback form. Objective: confirm ALERTs potential, give quality feedback for v2!
  90. 90. From Petals to LINAGORA Linagora activities overviewALERT as development bread-and-butter ALERT as a stepping stone for R&D
  91. 91. In one word? Jack-of-all-trades- Editor of professional solutions - OBM, open source equivalent to Exchange. - LinPKI suite to ensure the security of your system. - LinShare to collaborate efficiently on documents. - Petals, to build a decentralized, service-oriented IS.- Open Source Software Assurance - Hundreds of software covered. - Legal and technical support. - Redistribution to communities.- Training and consulting - >150 topics, from administration to development. - Official certifications support.
  92. 92. A few more infos- 400 000 OBM users.- Constant growth since creation.- Many major public administrations and privateindustries. LINAGORA ensures the success of all your open source projects!
  93. 93. “So, how could you use ALERT?”- Better human resource management - very various profiles - many are contributing individually. - very flexible task attribution. >>> Allow everyone to be given tasks fitting their attributions, skills and desires.- Better internal communication >>> Stay informed only on useful topics for you. >>> Need help? Know who to ask to!- Better collaboration with communities >>> Easier search for information on an issue. >>> Facilitates the contributions.
  94. 94. “I heard about gold mine. Where?”- Internal use - as demonstrated before.- Extend ALERT - develop connectors or new features for a price! - help configure it or adapt infrastructure.- Teach ALERT - how to use ALERT. - how to design efficient workflows. - how to optimize contributions to the other tools.
  95. 95. “Ok, Im interested. Whats the nextstep?”- Try it! - First beta release available by end of October in our web site- Stay in touch! - follow us on Twitter or LinkedIN - give us feedback! - keep posted with blog RSS!
  96. 96. Your Turn for Q&A
  97. 97. Ask our Team:#AlertOWF12
  98. 98. Thank You !!! ALERT Team follow us on twitter @alertfp7 visit our websiteThis project is partially funded by EC FP7 (Project # 258098) www.alert-project.eu