Librarian and Integrators meeting (24 September 2013)
 
Attendees:
==========
Ben Couturier, Andrea Valassi, Bertrand Bellenot, Emil Obreshkov, Marco Clemencic,
Gloria Corti, Frank Winklmeier, I Ueda, Benedikt Hegner, Anton Karneyeu
 
Announcements:
==============
Victor Diez Gonzalez left the SPI project.
 
 
New action items:
  Organize common meeting with JIRA support in IT -> action Benedikt
 
 
 
JIRA migration discussion
=========================
 
ATLAS experience
----------------
Tutorial would be desirable
Default notifications are incomplete; notification schemes by category?
Need possibility for adding new masks and fields 
On creating new issues users are faced w/ a lot of unnecessary information
Can projects be grouped and depending on login be filtered?
Need replacement for 'squad' functionality of Savannah using egroups
Can the RESTful API be used? How does the SSO integration work there?
 
Is it possible to do a global search? (Gloria: feature there and better than in Savannah; searches can be saved)
Reply via email to issues (Benedikt: functionality used in SFT instance already)
Would like to see watch list of tickets (others: can be seen in the SFT instance; so probably a matter of permissions)
Would like to have a summary of project roles for a given user (Benedikt: needs one extra click from expected place)
Feature request: due date to become red when approaching deadlines
Trigger migration suffers from free text fields in "affected release" (Benedikt: can tackle cleanup in Savannah DB directly)
 
LHCb experience
---------------
Similar concerns as ATLAS, in particular complexity of screens and cluttered submission fields
Had a meeting with JIRA team in June. Got contradicting information by IT on whether dedicated instance makes sense or not
Notification schemes not known before enabling them; took a long time to converge
Would need better project templates according to a set of types
Documentation largely missing
Jira is perceived slow by many LHCb users
Workflow customisation can't be done
Mobile interface SSO broken -> unusable; get rid or fix
 
Discussion outcome
------------------
To tackle the problem of notification and permission schemes, we should define a standard set of ~3 per experiment. Similar for screens
Have a follow up with IT to discuss above concerns and to start hands-on work for missings schemes;
Getting a development instance and initial training would be necessary to prepare the canonical profiles
Eventually they have to be migrated to the production instance
 
The importance of the URL redirection facility after Savannah shutdown has been stressed again.
 
LCG 66 status
=============
Created new release to support gcc48. Waiting for validation from PF project before announcement. 
 
Round table
===========
 
SPI
---
Would like to move to new infrastructure in dev slot asap. Will do the changes once LCG 66 has been announced. 
 
PF
--
Validating LCG 66. No progress on CMake yet. Asked for hostname fixes to build machines
 
ATLAS
-----
reported problems with dev slot (Benedikt: will investigate)
 
LHCb
----
Requesting the addition of Boost 1.54 and wxpython to the next release
 
GENSER
------
nothing to report
 
ROOT
----
nothing to report
 
GEANT4
------
not present