1 / 6

Software licensing I

Software licensing I. Create an inventory the packages under license at each lab Recommendations? Examples: SLAC

triveni-ishaan
Download Presentation

Software licensing I

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. Software licensing I • Create an inventory the packages under license at each lab • Recommendations? • Examples: • SLAC • US DOE labs, via the SLCCC (Committee of Lab CIOs) has looked across the DOE lab system for some opportunities to act together. (successes include Mathematica and Red Hat Enterprise) • TRIUMF • Aflliated with University of British Columbia (Maple, Mathematica, FEMLAB, OPERA, PSPICE, MAFIA, ABSOFT) • ORACLE (via CERN) IHEPCCC - June 1 2006

  2. Software licensing II • Non-open HEP source software development • Should we make a general recommendation (with referring to any particular project) that HEP software should be open source • Examples: • SLAC • The DOE and Stanford University prefer that the software we develop be either: open source or aggressively commercialized. • Scidac2 Program (FW) IHEPCCC - June 1 2006

  3. Visitor support I • Document that status of the availability of wireless networks, printing, access to teleconferencing and videoconferencing facilities, use of VOIP, … (and review annually) • Examples: • TRIUMF • Visitor wireless network - contact network admin. Coverage is not site-wide. • Printing is available for visitors • Teleconferencing not provided by TRIUMF (use a local carrier $$) • Videoconferencing facilities are good • No restrictions on VOIP IHEPCCC - June 1 2006

  4. Visitor support II • SLAC • Good open wireless network (will soon require self-service registration via an initial web page) • Printing from visitor network: easy from Linux/Unix, arcane from Windows. • Teleconferencing offered free by ESNet for SLAC staff/users. • Videoconferencing: H.323, ISDN, limited VRVS (4 rooms equipped) • CERN • Wireless network requires registration (full coverage?) • Good printing for visitors • Teleconferencing service (manual and automated systems) • Videoconferencing facilities in most large meeting rooms • VOIP restrictions (Skype?) IHEPCCC - June 1 2006

  5. Meeting frequency • Aim for 4 meetings per year • Use teleconferencing but try to co-locate with other meetings • Feb 2006 CHEP in Mumbai • June 2006 teleconference • Sept 2006 EGEE in CERN (Sep 24-29)Fri Sep 22 or Sat? • Nov 2006 teleconference • Keep teleconference meetings to 1.5 hours • Agenda for this meeting is full • May have 1-2 longer meetings per year as need arises and we are co-located with another meeting IHEPCCC - June 1 2006

  6. Summary • Prepare report to ICFA (Moscow July 2006) • Proposed mandate and membership status • Report on activities • HEPiX, non-HEP use of the Grid, software issues,visitor support, … • Items for next meeting (Sept 2006) • Reports on non-HEP grid use by other organizations • Present inventory of commercial software • Report from SCIC • Role of IHEPCCC in Grid IHEPCCC - June 1 2006

More Related