Your SlideShare is downloading. ×
ScienceSoft: Open Software for Open Science
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ScienceSoft: Open Software for Open Science

446

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
446
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. ScienceSo  Open  Soware  for  Open  Science  Alberto  Di  Meglio,  Florida  Estrella  –  CERN  Morris  Riedel  -­‐  FZJ  First  Workshop  on  Maintainable  So3ware  Prac7ces  in  e-­‐Science  (So3warePrac7ce12)  Chicago  -­‐  09/10/2012   ScienceSo  is  incubated  by  EMI,  par6ally  funded  by  the  European  Commission  under  Grant  Agreement  RI-­‐261611  
  • 2. Content   • Background  and  context   • Plans  and  current  ac6vi6es   • Next  steps   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   2  
  • 3. EU  eInfrastructures   An  interoperable  Distributed  Compu7ng   Infrastructure  for  Europe   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   3  
  • 4. EMI  in  a  nutshell   •  Collabora6on  of  4   mw  providers   (ARC,  dCache,   gLite,  UNICORE)   •  26  partners   •  24M  EUR   •  3  years   (05/10  –  04/13)   •  55  products   •  2M  SLOC   EMI  INFSO-­‐RI-­‐261611   •  Open  source   09/10/2012   SowarePrac6ce12  -­‐  Chicago   4  
  • 5. EMI  Vision  and  Challenges   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   5  
  • 6. Cri6cal  issues   •  How  to  ensure  technical  coordina6on?   •  How  to  share  informa6on  across  projects  and  across   scien6fic  domains?   •  How  will  the  soware  be  supported  in  the  future?   •  Are  all  products  sustainable?  Are  all  worth  being   sustainable?   •  Anything  that  can  be  exploited  commercially?  How?   •  Is  there  something  else  we  can  use?  Is  it  good?  Does  it   work  as  it  should?  Can  we  contribute  to  it?   •  Who  is  using  the  soware  and  how  does  usage  evolve?   EMI  INFSO-­‐RI-­‐261611   •  Do  users  men6on  the  soware,  acknowledge  its   contribu6on  to  their  research?   09/10/2012   SowarePrac6ce12  -­‐  Chicago   6  
  • 7. Ini6al  discussions   • Other  projects,  communi6es  and  SMEs   shared  the  same  challenges  and  concerns   or  expressed  interest  in  similar  discussions   EMI  INFSO-­‐RI-­‐261611   The  ScienceSo  Steering  Commi?ee  (Dec  2011-­‐Feb  2013)   09/10/2012   SowarePrac6ce12  -­‐  Chicago   7  
  • 8. First  workshop   •  1st  ScienceSo  Workshop  –  CERN,  Feb  2012   –  Original  “Steering  Commidee”  and  other  interested   persons,  33  in  total   –  Helped  streamlining  the  requirements  and  possible   features   •  Overview  document:   –  hdp://cdsweb.cern.ch/record/1451518/files/ scienceso_v1.0.pdf     EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   8  
  • 9. Roadmap   –  Alpha  (March-­‐June  2012):  refinement  of  ideas,   requirements  and  features,  state-­‐of-­‐the-­‐art   –  Design  (July-­‐December  2012):  ini6al  design  and   prototyping   –  Concept  (January-­‐April  2013):  proof-­‐of-­‐concept,   itera6ons  on  features   –  OperaMon  (May  2013  onwards):  community   managed  ac6vi6es   Roadmap:  hdp://scienceso.org/roadmap   EMI  INFSO-­‐RI-­‐261611   18/09/2012   EGI  TF  2012  -­‐  Prague   9  
  • 10. Features   Catalogues   Processed  informaMon   Soware,  people,   what,  where,  who,  how   organiza6ons,  projects,   good/bad,  help,  licensing,   events,  etc.   data  import/export,   no6fica6ons,  etc.   Marketplace   IdenMficaMon  and  citaMon   Communi6es,  services,   Unique  iden6fiers,   incuba6on,   “soographical”  formats,   crowdsourcing,   etc.   EMI  INFSO-­‐RI-­‐261611   consultancy,  etc.   09/10/2012   SowarePrac6ce12  -­‐  Chicago   10  
  • 11. Sustainability   • Create  wider  communi6es  around   worthwhile  soware   • Generate  revenues  by:   –  Enabling  the  provision  of  specialized  soware-­‐ related  services  to  well-­‐iden6fied  groups   •  So3ware  engineering,  consultancy,  specialized   technical  development,  training,  etc.   –  Commercial  incuba6on  support   •  Business  plans,  legal  informa7on,  IP,  licensing,  etc.   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   11  
  • 12. Soware  Iden6fica6on  &  cita6on   • Improve  academic  recogni6on  of  soware   development   • Make  scien6fic  results  fully  reproducible   –  Unique  IDs,  code  runs,  VMs   • Extend  methods  from  publica6ons  and   datasets  (DOI)   • Agree  on  a  format  suitable  for  cita6on   equivalent  to  bibliographical  formats   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   12  
  • 13. State  of  the  art   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   13  
  • 14. Design  and  prototypes   • Func6onality:   –  Web  portal   –  Data  model,  Data  discovery  and  automa6on   –  Comment  and  ra6ng  system,  Subscrip6ons  and   no6fica6ons   –  Informa6on  processing  and  repor6ng   –  Marketplace,  Soware  Iden6fica6on  &  cita6on   • Forums  on  the  ScienceSo  portal  at   hdp://scienceso.org/forum     EMI  INFSO-­‐RI-­‐261611   18/09/2012   EGI  TF  2012  -­‐  Prague   14  
  • 15. First  steps  (technical)   •  Web  site  at  hdp://scienceso.org     –  Based  on  Drupal  (hosted  at  CERN),  features  added  as   modules   –  Easy  to  contribute  features   •  Simple  data  model  defined  for  objects  and   rela6onships   •  Registra6on,  search,  maps   •  OpenID-­‐based  access,  support  for  Facebook,  gmail   (not  yet  public)   •  Automa6on  of  rela6onship  and  data  collec6on  being   EMI  INFSO-­‐RI-­‐261611   discussed   09/10/2012   SowarePrac6ce12  -­‐  Chicago   15  
  • 16. Snapshot   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   16  
  • 17. First  steps  (strategic)   • Crea6on  of  collabora6ons  and  networking   –  Exis6ng  project  and  ini6a6ves   –  Developers  and  researchers  (ISGC  2012,  EGI/EMI   CF  2012,  EGI  TF  2012,  SowarePrac6ce  2012,   OGF)   –  Decision-­‐makers  in  interna6onal  organiza6ons,   research  centers  and  funding  bodies  (EIROForum,   EC,  FAO)   –  Open  source  consultancy  companies  and   incubators   EMI  INFSO-­‐RI-­‐261611   09/10/2012   SowarePrac6ce12  -­‐  Chicago   17  
  • 18. Opera6onal  Challenges   Governance   Funding   Founda6on?   Public  funding   Roles,  policies   Sponsoring   Admin,  legal,   Paid-­‐services   logis6cs,  etc.   Voluntary   EMI  INFSO-­‐RI-­‐261611   contribu6ons   09/10/2012   SowarePrac6ce12  -­‐  Chicago   18  
  • 19. Next  steps   • Finish  the  prototype  according  to  plan   • Discuss  with  other  projects  about  common   ac6vi6es  and  extending/reusing   func6onality   • Disseminate  the  results   • 2nd  workshop  tenta6vely  Feb  2013   –  Governance,  funding,  future  plans   • Based  on  feedback  and  par6cipa6on,  stop   EMI  INFSO-­‐RI-­‐261611   or  con6nue  with  opera6onal  phase     09/10/2012   SowarePrac6ce12  -­‐  Chicago   19  
  • 20. h?p://scienceso.org   SoftwarePractice12 - Chicago09/10/2012   20  

×