Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Search results

Jump to navigation Jump to search

Page title matches

  • '''Help and support:''' quality@egi.eu ...ject should be exported in (one of xls/csv/ods) format and provided to the quality manager for deposit and providing following information:<br>- WP number<br>
    13 KB (2,007 words) - 10:02, 16 September 2016

Page text matches

  • #REDIRECT [[EGI-Engage:Quality Plan]]
    37 bytes (4 words) - 17:36, 25 May 2015
  • ...to EGI must meet, Quality Control ensures that the software will meet the quality described earlier. Hence, Quality Control in EGI is involved in two phases of Quality Control in the relationships between EGI and its Technology Providers:
    3 KB (447 words) - 17:45, 29 November 2012
  • | Gender Action Plan | Sustainability Plan
    2 KB (308 words) - 20:43, 24 December 2014
  • ...e successful execution of the project and that all its outputs are of high quality by: * Quality assurance efforts to monitor the progress of the project against its define
    7 KB (991 words) - 15:13, 24 December 2014
  • |service quality= [[FAQ_GGUS-QoS-Levels]] |documentation= System Guide, Test Plan. No specific support documentation is available.
    647 bytes (89 words) - 14:03, 28 July 2015
  • | Strategic Plan&nbsp; Annual Report on Quality Status
    2 KB (281 words) - 20:58, 24 December 2014
  • *[[Plan 2014 Milestones]] *[[Plan 2013 Milestones]]
    7 KB (1,002 words) - 23:36, 24 December 2014
  • ...Administrative and Finance Coordinator (AFC) and will oversee the overall quality management and risk management, define monitoring and reporting process and | Quality and Risk Management
    6 KB (785 words) - 16:52, 13 January 2016
  • == UMD Quality Criteria == ...Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould
    2 KB (380 words) - 23:11, 24 December 2014
  • ...management will support the implementation of the project’s technical work plan and the achievement of its scientific objectives, as well as the completion #The evaluation of the overall performance of the project and the quality assurance and timely submission of deliverables.<br>
    9 KB (1,362 words) - 11:11, 17 September 2015
  • '''Help and support:''' quality@egi.eu ...ken in order to avoid the risks or to minimize their impact (risk response plan) for each risk
    14 KB (1,877 words) - 12:00, 12 October 2016
  • [https://documents.egi.eu/document/436 D1.5 Quality Plan and Project Metrics]
    1 KB (144 words) - 13:10, 6 January 2015
  • (D1.1) Quality plan for Period 1 === Task NA1.3 Quality and Risk Management ===
    4 KB (504 words) - 11:36, 2 April 2015
  • | '''Quality of Support level''' ...ested monthly performance for one month MUST provide a service improvement plan.
    2 KB (240 words) - 11:05, 29 September 2014
  • Action Plan</span></strike> | EGI Sustainability and Business Plan
    7 KB (823 words) - 20:42, 24 December 2014
  • | Quality Manager<br> ...eviewer’s comment must be tracked in the review document. The moderator is Quality Manager.
    8 KB (1,120 words) - 11:51, 24 August 2016
  • === Task NA1.3 Quality and Risk Management === *[[EGI-Engage:Quality Assurance#Review_process_for_deliverables_and_milestones|Review process for
    5 KB (627 words) - 09:20, 28 April 2015
  • === Task NA1.3 Quality and Risk Management === *working on Quality plan for Period 1 - deliverable<br>
    5 KB (651 words) - 10:42, 29 April 2015
  • | Quality Manager<br> The goal of this procedure is to identify risks and plan proper response to prevent risk occurrence.&nbsp; <br>
    2 KB (315 words) - 22:54, 30 October 2016
  • === Task TNA1.4: Quality Assurance === ** SAM refactor TF - plan reuse of the Probe NagiosWG tools (twiki, meiling-list)
    3 KB (449 words) - 22:59, 24 December 2014
  • ...ups for developing and approving policies relating to operations, software quality, security, user communities and general governance. The development of thes D2.2 Dissemination Plan [PM3]<br>
    8 KB (1,266 words) - 15:14, 24 December 2014
  • [[FAQ GGUS-QoS-Levels|Quality of Support (QoS) levels are definition. ]] ...ested monthly performance for one month MUST provide a service improvement plan.
    4 KB (512 words) - 14:16, 20 March 2015
  • We plan to do the following for the scenarios: ...o need no migration to other formats in the foreseeable future), give high quality images, and be available as target formats in some migration tool(s).
    4 KB (545 words) - 09:29, 14 August 2013
  • ...so, service reliability appears to have noticeably improved. The failover plan has recently been re-established and constitutes current work. The planned
    3 KB (418 words) - 16:07, 6 January 2015
  • * '''audio quality''' ...d not surprising, but very important observation is that the Skype call-in quality largely depends on end user conferencing setup
    22 KB (2,771 words) - 20:58, 24 December 2014
  • === Ensuring UMD release quality === To ensure that UMD releases consistently deliver the same level of quality, a '''delivery slip''' for UMD Releases is maintained.
    10 KB (1,188 words) - 17:42, 16 January 2017
  • ...ons, preparation of response to recommendations and adjustment of activity plan for Amendment N2 === Task NA1.3 Quality and Risk Management ===
    7 KB (963 words) - 12:48, 13 July 2016
  • * A production-quality scientific publications repository based on the OpenAIRE infrastructure and * Communication plan and campaign to inform the EGI community about the new services
    3 KB (385 words) - 16:36, 10 April 2014
  • | Quality Manager<br> | Proposes action plan to Technical Coordinator (TC)<br>
    3 KB (524 words) - 15:48, 9 June 2016
  • [[FAQ GGUS-QoS-Levels|Quality of Support (QoS) levels are definition. ]] ...ested monthly performance for one month MUST provide a service improvement plan.
    21 KB (2,434 words) - 16:13, 29 August 2014
  • | Deployment plan for the distribution of operational tools to the NGIs/EIROs. [https://rt.eg | A plan for the deployment of regionalised variations of the operational tools to t
    9 KB (1,247 words) - 20:45, 24 December 2014
  • === Task NA1.3 Quality and Risk Management === * D2.7 (M12 - ENG): Updated/quality checked as per review feedback
    6 KB (740 words) - 13:11, 1 July 2016
  • ...se of the UMD repositories''', which contain software verified through the quality assurance process of UMD. ...ith Liberty and Mitaka, '''in case OpenStack is Kilo (or older) an upgrade plan of OpenStack has been asked'''
    7 KB (1,044 words) - 15:27, 25 October 2017
  • Collection of Yearly project plan, organization of activities around the EGI&nbsp;Marketplace, drafting of th === Task NA1.3 Quality and Risk Management ===
    10 KB (1,444 words) - 17:22, 11 June 2015
  • ...he EGI-InSPIRE project on a three-month basis are reported in the "Quality Plan and Project Metrics" document, produced by NA2 on annually: * [https://documents.egi.eu/document/55 "Quality Plan and Project Metrics" for project year '''one''' (May 2010 - April 2011)]
    18 KB (2,263 words) - 19:29, 24 December 2014
  • '''Help and support:''' quality@egi.eu ...ject should be exported in (one of xls/csv/ods) format and provided to the quality manager for deposit and providing following information:<br>- WP number<br>
    13 KB (2,007 words) - 10:02, 16 September 2016
  • * completed D1.3 (Quality Plan for PY2) with final revision and reorganization of KPIs and metrics, final * revision of LTOS services plan and timing (Contact: Giuseppe)
    11 KB (1,481 words) - 16:07, 10 August 2016
  • === Task NA1.3 Quality and Risk Management === ** Prepared presentation on Plan for Exploitation and Dissemination in H2020 for the collaboration board (CB
    8 KB (1,151 words) - 12:27, 26 October 2016
  • === Task NA1.3 Quality and Risk Management === ...ion (R) M28 - Merge with D2.13 EGI Sustainability and Business Development Plan M30
    8 KB (1,104 words) - 10:09, 2 December 2015
  • ...nt that defines the minimum set of operational services and the respective quality parameters that a Resource Centre is required to provide in EGI, and accept ...constantly check their functioning and periodically produce reports on the quality of service offered; at the same time the measurement of resources usage hav
    6 KB (990 words) - 17:03, 23 November 2017
  • '''Help and support:''' quality@egi.eu <br> Milestone and Deliverable follow up: [https://rt.egi.eu/rt/Sear *'''DEM:''' Demonstrators, pilots, prototypes, plan design <br>
    46 KB (6,694 words) - 17:27, 20 September 2017
  • ...se of the UMD repositories''', which contain software verified through the quality assurance process of UMD. ...ith Liberty and Mitaka, '''in case OpenStack is Kilo (or older) an upgrade plan of OpenStack has been asked'''
    8 KB (1,160 words) - 15:37, 5 December 2016
  • * preparation of the market place definition plan and preparation of surveys with multi activity review * AAI short term and medium term plan to support ELIXIR
    12 KB (1,636 words) - 13:16, 26 June 2015
  • ...ating a GGUS Support Unit to receive and handle incidents (define level of quality of support - default: Medium) === Plan Release ===
    12 KB (1,799 words) - 15:20, 18 September 2019
  • ...se of the UMD repositories''', which contain software verified through the quality assurance process of UMD. * early draft plan
    9 KB (1,263 words) - 15:27, 25 October 2017
  • * operational plan for rolling out AAI services within JRA1 was requested === Task NA1.3 Quality and Risk Management ===
    8 KB (1,115 words) - 15:53, 1 September 2015
  • *To develop a plan aimed at assembling a VRC out of the existing Chemistry, Molecular & Materi ...on-technical investigations are integrated into the first draft of the VRC plan. The draft is restricted to the project leader.
    8 KB (1,152 words) - 11:10, 22 June 2015
  • === Task NA1.3 Quality and Risk Management === * Preparations for Amsterdam 2016: initial plan
    8 KB (1,089 words) - 15:11, 3 December 2015
  • ...se of the UMD repositories''', which contain software verified through the quality assurance process of UMD. ...ith Liberty and Mitaka, '''in case OpenStack is Kilo (or older) an upgrade plan of OpenStack has been asked'''
    8 KB (1,215 words) - 14:25, 10 October 2016
  • ...service provider - workaround being investigated with the tool provider - Plan B investigated for another tool. === Task NA1.3 Quality and Risk Management ===
    8 KB (1,171 words) - 11:24, 29 July 2015

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)