Agenda: https://indico.cern.ch/conferenceDisplay.py?confId=272822

Participants: 
Joel Closier (LHCb), Alina Grigoras (ALICE), Maria Dimou (chairperson & notes),
Helmut Dres (GGUS), Maarten Litmaath (WLCG), Stefan Roiser (LHCb), 
Pable Saiz (WLCG-GGUS), I.Ueda (ATLAS).

Apologies:
!!! NEW !!! Alberto Aimar (WLCG), Guenter Grein (GGUS), Benedikt Hegner (Savannah), Nils Hoimyr (JIRA), Christoph Wissing (CMS).

Discussion & Decisions:

A. Agenda items 1.1-1.4 - About savannah projects belonging to experiments:
The Librarians & Integrators' meeting https://indico.cern.ch/categoryDisplay.py?categId=1449 is the right forum, so the WLCG Tracking Tools TF 
should not discuss progress on experiment savannah projects, in the future. 
Expressed experiment requests, e.g. for one JIRA instance per experiment 
should  be discussed in that forum. 
All participants expressed worries about the JIRA notifications and access permissions,
i.e. tickets are only accessible by the JIRA project Admins+users, we can't 
enter a JIRA ticket URI in a document readable by the wide world. 
!!! NEW !!! After circulating the 1st version of these minutes, Nils explained that 
!!! NEW !!! https://cern.service-now.com/service-portal/article.do?n=KB0002226 clarifies that by choosing an Open Source JIRA instance (like Open or EMI), 
!!! NEW !!! projects are available publicly on the internet by default.

B. Agenda item 1.5 - About the 83 savannah projects belonging to IT+Grid:
Maarten will list clearly:
	- the ones to migrate to JIRA and continue living.
	- the ones to close and migrate to JIRA because they are history and should remain accessible.
 	- the ones to close and throw away because they are not important.
***ACTION: Maarten***

C. Agenda item 1.6 - About the savannah.cern.ch future:
Current policy verified with Benedikt Hegner on 2013/10/09 is:
------------
One can browse savannah tickets on the web as long as there are savannah projects 
being migrated to JIRA. Savannah project owners who don't wish to migrate 
or said nothing must understand that their project shall simply disappear 
when the server is shutdown. Legacy projects can either:
	- be migrated to JIRA
	- have their contents given to their owners as an xml dump
	- have their contents copied to tape, i.e. no more web-accessible!
------------

D. Agenda item 1.7 - About most recent JIRA FAQ:
Follow link from the agenda, QAs on access permissions are included.
***ACTION: All***

E. Agenda item 2 - About multiple tickets' generation from a single GGUS ticket submission form.
Participants agree the functionality is very much needed. Additional GGUS development
requests that came out of the discussion:
	a. Put the "Ticket category:[Incident | ChangeRequest]" menu already on the ticket submission form for ALL tickets.
	b. Put the relevant ROC/NGI next to the site name in the drop-down menu of the "Affected Site" field.
	c. Display a Warning "You are about to generate X tickets with this submission. Are you sure the information is complete and correct?"
	d. Document that the "Concerned VO" value should be selected for these tickets to show in the WLCG weekly reports.
	e. Group the sites under their ROC/NGI for checking before submission.
These points should be recorded in the GGUS dev. items' list https://savannah.cern.ch/support/?138299 and more.
***ACTION: Maria***
To decide on the "Type of Problem" value for this new submission form, Maarten 
said the WLCG MoU changed in 2013 and he will submit it to the Tracking Tools TF 
for possible extension of the values' list.
***ACTION: Maarten***

F. Agenda item 3 - Re-visit the TF Mandate:  
Maria announced Pablo will succeed her in the GGUS dev. team and the chairing of the TF.
The Mandate discussion was postponed, due to lack of time. To be done at the next meeting.
***ACTION: Pablo***