3
1 Overview of the forge  Fusion Forge is the collaborative space where we work in FI-WARE.  We can create as many projects as we want inside the forge  A person has a single forge-wide user  The users get access to the projects where they work.  There are user profiles: different sets of permissions per user Forge Users Project A Project B Project n … Per project access rights For instance, a given user may: 1.have admin access in project A 2.be a plain user of Project B (no admin rights ) 3.be plain user of C but different permissions than in B) 4.and have no access to the other projects at all Project C

4
1 Overview of the forge  You apply for a user once by using a self service facility Tutorial: The you provide has to be corporate (gmail, etc. will be rejected) IMPORTANT: follow the naming convention  Then you apply to join the projects where you need access Tutorial: This is subject to the approval of an administrator  Each project has a set of tools (wiki, doc management…)  Check out the online tutorials before asking questions!!! Scroll down here: Note that “Users” in this context means “Use Case Projects”

5
1 Overview of the forge ProjectPurposeAccess rights FI-WAREMain project. All FI-WARE members should have access to it. Fi-WARE members and PPP member projects can access all the info. Users on the internet can see part of the info FI-WARE PPP Restricted Space to share info with the PPP Fi-WARE members and PPP member projects can access all the info. Not meant for Users on the internet  Still not open to Use Case Trials. We will specify the contact points and support channels for each project once we set up JIRA Check the online tutorials before asking!  Projects of interest for the UCs:

6
2 Usage of tools The ones we use in FI-WARE are these:  Tracker: to handle tickets. A ticket represents something that will need some work and a workflow (request, backlog item, issue, bug, etc.) FI-WARE will use a separate one (JIRA) to interact with the UC Trials  Mailing lists: mailman lists integrated with the forge  Docs: to store & share documents  SCM: Source Code Management. SVN instances for GE source code  Files: tool to store bigger files. We deliver GE binaries using this tool.  Mediawiki: wiki instance using the mediawiki platform Tools on the forge Forge wide single sign on Forge wide single sign on

7
2 Usage of tools  JIRA (+ Greenhopper) Issue creation, browsing and searching › Issue creation from s, 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 Tracker: tool to handle tickets. A ticket represents something that will need some work and has a workflow (bugs, issues, requests, backlog items, etc.)

14
3 Conclusions Forge wide single sign on Forge wide single sign on Instant access to multiple resources Instant access to multiple resources Using a forge has strengths that catalyse a large scale project Per user permissions Per user permissions Focus on collaborative work Focus on collaborative work