http://www.fi-ware.euhttp://www.fi-ppp.eu

FI-WARE Collaborative Tools

Miguel Carrillo (Telefónica I+D)

Index

1. Overview of the forge

2. Usage of tools

3. Conclusions

1 Overview of the forge Fusion Forge is the collaborative space where we work in FI-

WARE. • http://forge.fi-ware.eu/

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 userForge Users

Project A

Project B

Project n

…

Per project access rights

For instance, a given user may:

1. have admin access in project A2. 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

1 Overview of the forge

You apply for a user once by using a self service facility • Tutorial: http://wiki.fi-ware.eu/How_to_create_a_FusionForge_account

• The e-mail 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: http://wiki.fi-ware.eu/How_to_join_a_FI-WARE_project_in_FusionForge

• 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: http://wiki.fi-ware.eu

• Note that “Users” in this context means “Use Case Projects”

1 Overview of the forge

Project Purpose Access rightsFI-WARE Main 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-WAREPPP 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:

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

2 Usage of tools

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

Tracker: tool to handle tickets. A ticket represents something that will need some work and has a workflow (bugs, issues, requests, backlog items, etc.)

2 Usage of tools

Mailing lists: standard mailman lists integrated with the forge

2 Usage of tools

States

• Active: public

• Deleted: in the “rubbish bin”. Hidden

• Pending: hidden, pending approval by admin person

• Private: only visible to users logged on the forge

Docs: to store & share documents

2 Usage of tools

This tool can be used or not (no obligation to release source code)

The SW can be released under “FI-WARE” Project (optional per GE)

SCM: Source Code Management (SVN instances)

2 Usage of tools

Files: tool to store bigger files. We deliver binaries using this tool.

2 Usage of tools

Mediawiki: tool to edit wiki pages.

Mediawiki is a standard tool and it is fully integrated in the forge

2 Usage of tools

The delivarable dilemma • FI-WARE wanted to create a consistent wiki with the public deliverables

• But the EC needed “traditional” deliverables

Solution: FI-WARE made an effort to create an automated wiki deliverable generation tool

Delivery cockpit wiki page

Deliverable Generation Tool

wiki pages

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 userpermissions

Per userpermissions

Focus on collaborativework

Focus on collaborativework