1. EMI is partially funded by the European Commission under Grant Agreement RI-261611 Open Source Software and the ScienceSoft Initiative Alberto DI MEGLIO, CERN EGI/EMI Conference 2012 26/03/2012

2. EMI INFSO-RI-261611 What is the problem? What is ScienceSoft? Expected benefits and opportunities Content 27/03/2012EGI/EMI Conference, Munich2

3. EMI INFSO-RI-261611 EMI: European Middleware Initiative – 3-year project (5/2010-4/2013) to support and evolve grid middleware from ARC, gLite, dCache and UNICORE Sustainability for EMI mainly means: – How will the middleware be supported when the project ends (financial aspect)? – What happens of the technical coordination activities among partners and between developers and users (collaborative aspect)? General context: EMI 27/03/2012EGI/EMI Conference, Munich3

4. EMI INFSO-RI-261611 The problem is not limited to EMI, but shared by many scientific projects and communities having similar continuity and sustainability issues The issue of how to enable sustainability is being discussed with developers and users since September 2011 Valuable input, feedback, requirements and criticism have been collected Investigation 27/03/2012EGI/EMI Conference, Munich4

5. EMI INFSO-RI-261611 Operating Systems Cloud “Market analysis” 27/03/2012EGI/EMI Conference, Munich5 Cloud IaaS Grid HPC Grid Services Applications User interfaces, portals, etc Desktop Comp. Developers Users Service providers Platform integrators Research communities Academic and Research Institutes Commercial companies Funding bodies HorizontalVertical

6. EMI INFSO-RI-261611 Lack of continuity in support, development, coordination of software Non-optimal communication between users and developers Lack of consistent real usage information Limited access to other users experience Limited or complex ways of finding what exists already No way of influencing the production of software Lack of visibility of the software activities No way of assessing the user “market” Top 8 reported problems 27/03/2012EGI/EMI Conference, Munich6

7. EMI INFSO-RI-261611 Most software we deal with is generically “open source” – It uses an OSI licenses, but there are many such licenses, not all cross-compatible – Source code is available, but from many different public or institutional repositories – Limited cross-contributions, often the software requires specific scientific as well as computer engineering knowledge This is not enough to be a “community” Software 27/03/2012EGI/EMI Conference, Munich7

8. EMI INFSO-RI-261611 Three main “business models”: – Publicly funded projects Our main model so far, funds from EC or other public agencies – Community funded open source projects Funded (usually in effort) by the members for their own needs or through the provision of paid services (SourceForge, GitHUB, Drupal, OpenStack, etc.) – Sponsored open source projects Funded (in money and effort) by commercial companies as a business driver (Apache, Eclipse, etc.) OS Software Models 27/03/2012EGI/EMI Conference, Munich8

9. EMI INFSO-RI-261611 Does a solution exist? 27/03/2012EGI/EMI Conference, Munich9 Apache, Eclipse, Drupal, OpenStack Fedora, EPEL, Debian, etc. GitHub, SourceForge OuterCurve, Polarsys, GENIVI, OpenMama, NanoHub, CyberSKA Technology Operating Systems Services, tools Vertical/Community Services, tools

10. EMI INFSO-RI-261611 ScienceSoft 27/03/2012EGI/EMI Conference, Munich10 Information Services Users Developers

11. EMI INFSO-RI-261611 Software, services and people catalogs – Tagging, taxonomies, technical metrics Generation of statistics on: – Usage, deployment, geographical distribution Honour system – Who likes what and why, rating system, peer reviews Citation system to allow software to be referenced in papers – Like DOI for papers Examples of Information 27/03/2012EGI/EMI Conference, Munich11

12. EMI INFSO-RI-261611 More information about software and its usage – Categorization, usage and technical metrics – Assessment of costs, resource optimization – Supporting evidence for funding requests – Software licenses adoption and compliance, compatibility checks – More visibility for developers, more information and transparency for users – Peer-reviewed information Benefits 27/03/2012EGI/EMI Conference, Munich12

13. EMI INFSO-RI-261611 Marketplace for products, services, people – Match demand and offer, commercial support Links to technical services: – Support, testing, deployment – Provided by users to users or by third-parties (including commercial companies) Platform integration support (third-party) – Definition and sharing of community-specific profiles or software stacks – Deployment using cloud or grid technologies Example of Services 27/03/2012EGI/EMI Conference, Munich13

14. EMI INFSO-RI-261611 Support for creation of customized community and group portals – By technical interests, scientific domain, etc. – Coordination, collaboration and discussion tools Support for organization of technical events Examples of Services 27/03/2012EGI/EMI Conference, Munich14

15. EMI INFSO-RI-261611 Most of the required functionality exists – But it’s available only in separate, disconnected pieces The value proposition is the aggregation and integration of the functionality – Provide immediate benefits to users – Lower the implementation cost and time as much as possible Implementation principle 27/03/2012EGI/EMI Conference, Munich15

16. EMI INFSO-RI-261611 27/03/2012EGI/EMI Conference, Munich16 Community tools and services (source code repos, image repos, testbeds, etc.) Software inventory and metrics Web and collaboration tools Software management procedures Event management Deployment and engineering services Source code repositories The brands and projects show here have not officially endorsed in any way ScienceSoft and are used as examples of possible functionality providers

17. EMI INFSO-RI-261611 Format: – Open community effort incubated by EMI, but meant to be an independent community effort – Not a “project”, not “EMI 2” Name and slogan: – ScienceSoft: Open Software for Open Science Domain name registered: – sciencesoft.org Web site: – http://sciencesoft.orghttp://sciencesoft.org Current Status 27/03/2012EGI/EMI Conference, Munich17

18. EMI INFSO-RI-261611 Catalogues: products, services, skills, institutes, companies Marketplace: match needs and offers, sell skills and products, commission new services and software Citation system: can the DOI concept be applied? Collaboration: across projects, domain and communities, openness Main Roles 27/03/2012EGI/EMI Conference, Munich18

19. EMI INFSO-RI-261611 4 phases – Concept, Design, Implementation, Operations Concept phase: – January 2012 to June 2012 – Discuss, share ideas, pros and cons, decide whether there is something worth pursuing or not Design should not start later than June Current status 27/03/2012EGI/EMI Conference, Munich19

20. EMI INFSO-RI-261611 ScienceSoft Contributors: – Organizers, Editors, Developers Community Members: – Individuals – Project Managers – Collaboration Managers – Institutes/Companies Managers Collaboration 27/03/2012EGI/EMI Conference, Munich20

21. EMI INFSO-RI-261611 http://sciencesoft.org/join Join 27/03/2012EGI/EMI Conference, Munich21