1 / 14

FI-WARE Collaborative Tools Miguel Carrillo ( Telefónica I+D)

FI-WARE Collaborative Tools Miguel Carrillo ( Telefónica I+D). http://www.fi-ware.eu http://www.fi-ppp.eu. Index. Overview of the forge Usage of tools Conclusions. 1 Overview of the forge. Fusion Forge is the collaborative space where we work in FI-WARE. http://forge.fi-ware.eu/

lawson
Download Presentation

FI-WARE Collaborative Tools Miguel Carrillo ( Telefónica I+D)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FI-WARE Collaborative ToolsMiguel Carrillo (Telefónica I+D) http://www.fi-ware.eu http://www.fi-ppp.eu

  2. Index • Overview of the forge • Usage of tools • Conclusions

  3. 1 Overview of the forge • FusionForgeisthecollaborativespacewherewework in FI-WARE. • http://forge.fi-ware.eu/ • We can create as manyprojects as wewantinsidetheforge • A person has a single forge-wideuser • Theusersgetaccesstotheprojectswheretheywork. • There are userprofiles: different sets of permissions per user Forge Users Forinstance, a givenusermay: haveadminaccess in project A be a plainuser of Project B (no adminrights ) be plainuser of C butdifferentpermissionsthan in B) and have no accesstotheotherprojects at all Project A Per projectaccessrights Project B … Project C Project n

  4. 1 Overview of the forge • Youapplyfor a user once byusing a selfservicefacility • Tutorial: http://wiki.fi-ware.eu/How_to_create_a_FusionForge_account • The e-mail youprovide has to be corporate (gmail, etc. will be rejected) • IMPORTANT: followthenamingconvention • Thenyouapplytojointheprojectswhereyouneedaccess • Tutorial: http://wiki.fi-ware.eu/How_to_join_a_FI-WARE_project_in_FusionForge • Thisissubjecttotheapproval of anadministrator • Eachproject has a set of tools (wiki, docmanagement…) • Checkouttheonline tutorialsbeforeaskingquestions!!! • Scrolldownhere: http://wiki.fi-ware.eu • Note that “Users” in thiscontextmeans “Use Case Projects”

  5. 1 Overview of the forge • Stillnot open to Use Case Trials. Wewillspecifythecontactpointsand supportchannelsforeachproject once we set up JIRA • Checkthe online tutorialsbeforeasking! • Projects of interestfortheUCs:

  6. 2Usage of tools Theoneswe use in FI-WARE are these: • Tracker: tohandle tickets. A ticket representssomethingthatwillneedsomework and a workflow(request, backlogitem, issue, bug, etc.) • FI-WARE will use a separateone (JIRA) tointeractwiththe UC Trials • Mailinglists: mailmanlistsintegratedwiththeforge • Docs: to store & share documents • SCM: SourceCode Management. SVN instancesfor GE sourcecode • Files: toolto store bigger files. Wedeliver GE binariesusingthistool. • Mediawiki: wiki instanceusingthemediawikiplatform Tools ontheforge Forgewide single signon

  7. 2 Usage of tools Tracker: tool to handle tickets. A ticket represents something that will need some work and has a workflow (bugs, issues, requests, backlog items, etc.) • JIRA (+ Greenhopper) • Issue creation, browsing and searching • Issue creation from emails, browsers or other channels • Activity monitoring and reporting • Links to tasks • Dashboard – rich set of graphs • Well defined and customizable workflow • Good conceptual model, with issues already adapted to agile methodology • Importation of issues from CSV files • Issue creation open to groups of non JIRA users • Extensive number of add-ons

  8. 2 Usage of tools Mailing lists: standard mailman lists integrated with the forge

  9. 2 Usage of tools Docs: to store & share documents • States • Active: public • Deleted: in the “rubbishbin”. Hidden • Pending: hidden, pendingapprovalbyadminperson • Private: only visible tousersloggedontheforge

  10. 2 Usage of tools SCM: Source Code Management (SVN instances) • Thistool can be usedornot (no obligationtoreleasesourcecode) • The SW can be releasedunder “FI-WARE” Project (optional per GE)

  11. 2 Usage of tools Files: tool to store bigger files. We deliver binaries using this tool.

  12. 2 Usage of tools Mediawiki: tool to edit wiki pages. • Mediawikiis a standard tool and itisfullyintegrated in theforge

  13. 2 Usage of tools • Thedelivarabledilemma • FI-WARE wantedtocreate a consistent wiki withthepublicdeliverables • Butthe EC needed “traditional” deliverables • Solution: FI-WARE madeanefforttocreateanautomated wiki deliverablegenerationtool Deliverycockpit wiki page wiki pages DeliverableGenerationTool

  14. 3 Conclusions Using a forge has strengths that catalyse a large scale project Forgewide single signon Instantaccessto multipleresources Per user permissions Focusoncollaborative work

More Related