Owf12 open forges summit interoperability of floss forges
0 likes404 views
The document discusses software forge interoperability and integration. It covers different forge architectures, the need to break silos by making data portable, and some solutions for integrating tools like using semantic web standards and Linked Open Data. It provides examples of integrating FusionForge with other tools using OSLC and connecting it to Jenkins for continuous integration. The conclusion restates the issues addressed.
Owf12 open forges summit interoperability of floss forges
- 1. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Interoperability of FLOSS forges; lessons from the COCLICO project, implemented in FusionForge and other platforms Olivier Berger <olivier.berger@telecom-sudparis.eu>, Télécom SudParis Christian Bayle <christian.bayle@orange.com> Orange Labs Thursday 11/10/2012 Open World Forum - Paris Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 2. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Quick Introduction Short bio Olivier BERGER <olivier.berger@telecom-sudparis.eu> Research Engineer at TELECOM SudParis, expert on software development forges, and interoperability in Libre Software development projects. Contributor to FusionForge, Debian, etc. Participated to COCLICO project (ended 10/2011). Christian BAYLE <christian.bayle@orange.com> Research engineer at Orange Labs, in Grenoble (France), in charge of deploying FLOSS software for developers, like Software Forges, Continuous integration as a service. Contributes to FusionForge and Tuleap forges, Debian maintainer, and participated in COCLICO project (FUI7) in the previous years. Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 3. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion FusionForge FusionForge https://fusionforge.org/ Formerly known as GForge (Libre version) inherited its codebase from the initial SourceForge (year 2000) Host your own forge (Linux, Postgres, PHP, etc.) FLOSS + Open Community (loose consensus) Used in many academic institutes (INRIA, SourceSup RENATER, IFREMER, . . . ), FLOSS projects (Debian’s Alioth, ...) Boosted by project COCLICO in 2010-2011 Christian and Olivier co-maintainers of the Debian packages FusionForge 5.2 released on 2012/09/28 Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 4. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Previously, at OWF Recap 2011 Last year at OWF 2011 (OSDCFr) : Jailbreaking the Forges : project export/import efforts Since then : COCLICO project finished Codendi -> Tuleap Some contributions to FusionForge in 5.2 Some interest in OSLC ADMS.SW 1.0 specification released not much effort in ForgePlucker Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 5. 1/4 Forge architecture Integration strategies
- 6. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Different current architectures Architectures & development models From scratch / comprehensive Can you compete with GitHub or other proprietary tools ? Integration of other FLOSS projects SSO, APIs, via Unix / Apache / PHP glue/hacks Services Components / Web Services Web 2+ mashups REST, Ajax Unhosted (.org) ? Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 7. Git SCM code
- 8. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Different current architectures Common plugins Common Sourceforge™ inheritance Common Theme functions Codendi™ /Tuleap™ plugin system derivated from Gforge OSE/FusionForge They made it because they didn’t know it was impossible Common plugin were realized for Mailman/Forumml/Hudson/Mediawiki Possible continuation with ADMS.SW, industrialisation of Mediawiki But hard to industrialize and keep synced Leading to duplicated effort Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 9. 2/4 Hosted, cloud. . . Silos Who owns your data/code Can you escape ?
- 10. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Breaking forge silos with Linked Open Data approach Data portability software is libre (well most of it ;-) (software development) data jailed in services (silos) even worse at the Cloud scale ? “Freedom in the Cloud” by Eben Moglen “Franklin Street Statement on Freedom and Network Services” Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 11. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion How we could solve this (Semantic) Web Standards REST (not yet so much of a standard. . . but LDP WG @ W3C) RDF (not necessarily XML) Linked (Open) Data Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 12. 3/4 Some solutions
- 13. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Tools integration and interoperability Software development tools integration issues Lots of different (legacy) systems in respective silos Integrated suites Open Source tools or Proprietary Software alike Software development forges Agile methodologies vs. monolithic suites Traceability Scalability Very poor interoperability Syntactic Semantic Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 14. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Tools integration and interoperability Integration with silos Tools are “natively” integrated in isolated suites Ad-hoc interfaces : no standardization Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 15. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Tools integration and interoperability Linked lifecycle data OSLC (Open Services for Lifecycle Collaboration) : http ://oslc.co/ Source : IBM/Rational Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 16. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Tools integration and interoperability Example : OSLC Compact preview of FusionForge users Resources linking and preview through standardized mechanism for URIs + AJAX preview http://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/OslcCompactPreviewTooltips Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 17. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Tools integration and interoperability Continuous integration : FusionForge + JenkinsCI Demo : http://vimeo.com/23480321 Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 18. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW Vision EC / ISA Vision for an enhanced federation of software forges Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 19. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW Goal : Federations of forges / directories Source : SEMIC.EU D5.1.1 – “Vision document : The vision for an enhanced software description metadata schema and federated software catalogue” Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 20. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW ADMS.SW Asset Description Metadata Schema for Software (ADMS.SW) Pilot : EC / Interoperability Solutions for European Public Administrations (ISA) - cf. Joinup site Exchanging project / packages / releases descriptions across development platforms and directories Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 21. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW Specifications + RDF Schema Reuse : ADMS / RADion (generic meta-data for semantic assets indexing) DOAP (Description of a project) SPDX™ ( Software Package Data Exchange ®) W3C Government Linked Data (GLD) Working Group version 1.0 issued 2012/06/29 Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 22. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW ADMS.SW main concepts Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 23. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW Implementation FusionForge plugin for project meta-data (reuse of the DOAPRDF plugin developped in COCLICO) Debian PTS (Package Tracking System) : 1.5 M triples PREFIX doap : <h t t p : / / u s e f u l i n c . com/ n s / doap> SELECT ∗ WHERE { GRAPH <h t t p : / / p a c k a g e s . qa . d e b i a n . o r g /> { ? dp doap : homepage ? h } GRAPH <h t t p : / / p r o j e c t s . a p a c h e . o r g /> { ? ap doap : homepage ? h } } Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 24. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion ADMS.SW Matching packages Example (Matching upstream project homepages with Debian source packages’) dp h ap ivy ant.a.o/ivy/ ant.a.o/ivy/ apr apr.a.o/ apr.a.o/ apr-util apr.a.o/ apr.a.o/ libcommons-cli-java commons.a.o/cli/ commons.a.o/cli/ libcommons-codec-java commons.a.o/codec/ commons.a.o/codec/ libcommons-collections3-java commons.a.o/collections/ commons.a.o/collections/ libcommons-collections-java commons.a.o/collections/ commons.a.o/collections/ commons-daemon commons.a.o/daemon/ commons.a.o/daemon/ libcommons-discovery-java commons.a.o/discovery/ commons.a.o/discovery/ libcommons-el-java commons.a.o/el/ commons.a.o/el/ libcommons-fileupload-java commons.a.o/fileupload/ commons.a.o/fileupload/ commons-io commons.a.o/io/ commons.a.o/io/ commons-jci commons.a.o/jci/ commons.a.o/jci/ libcommons-launcher-java commons.a.o/launcher/ commons.a.o/launcher/ ... ... ... Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 25. 4/4 Perspectives Conclusion
- 26. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Perspectives FLOSS distributions ecosystem Source : http ://git.upsilon.cc/r/talks/20110224-evry.git Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 27. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Perspectives Large scale bug-tracking Lots of duplicate or related bug reports Not a single place where to monitor bugs OK, launchpad, maybe. . . too much a silo anyway No interoperability of tools Manual work of maintainer / QA (bug triaging, etc.) Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 28. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Perspectives Bugtracker interoperability prerequisite No existing standard for bugtracker APIs . . . until OSLC-CM (2009-) Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 29. Intoduction Forges architecture Breaking silos Integration of forges with other tools Conclusion Perspectives More interoperability in FLOSS tools Push standardization in tools development Eclipse Mylyn support of OSLC (in the FLOSS parts), based on Eclipse Lyo roots ? . . . When ? New opportunities Open Linked Data for direct “mining” of FLOSS projects development process metrics Large scale bug tracking and QA process in the FLOSS ecosystem Qui vivra verra. . . Olivier Berger <olivier.berger@telecom-sudparis.eu>,Télécom SudParisChristian Bayle <christian.bayle@orange.com>Ora Interoperability of FLOSS forges;lessons from the COCLICO project, implemented in FusionForge and other platforms
- 30. Fin Merci. Questions ? Copyright Copyright 2012 Institut Mines Telecom + Olivier Berger + Orange Labs + Christian Bayle License of this presentation : Creative Commons Share Alike (except illustrations which are under copyright of their respective owners)