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 Plan2 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 define7 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 Annual Report on Quality Status2 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 Management6 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 sould2 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 risk14 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 Plan7 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 for5 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. <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 planned3 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 setup22 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 services3 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 t9 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 feedback6 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 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 (CB8 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 M308 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 hav6 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 ELIXIR12 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 plan9 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 plan8 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
- *D4.2 Certification scheme plan (M12, M24) - The plan for the creation of a professional personal certification scheme based on t **Input to the exploitation plan from task 4.312 KB (1,740 words) - 17:59, 6 November 2015
- === Task NA1.3 Quality and Risk Management === *D2.9: “EGI Sustainability and Business Development Plan”7 KB (892 words) - 16:20, 4 March 2016
- === Task NA1.3 Quality and Risk Management === *Data Plan - https://wiki.egi.eu/wiki/EGI-Engage:Data_Plan9 KB (1,191 words) - 15:52, 1 October 2015
- === Task NA1.3 Quality and Risk Management === * M6.5 - Training plan for second period11 KB (1,540 words) - 09:58, 18 May 2016
- === Task NA1.3 Quality and Risk Management === *D2.9: “EGI Sustainability and Business Development Plan”11 KB (1,550 words) - 11:01, 10 February 2016
- * Changes to activity plan to reflect management changes, central budget updates to be finalised TNA1.4 Quality assurance4 KB (611 words) - 23:04, 24 December 2014
- === Task NA1.3 Quality and Risk Management === *D2.4 "Data Management Plan" (M6 - Aug 2015)9 KB (1,299 words) - 08:27, 14 August 2015
- === Task NA1.3 Quality and Risk Management === ** Designed a plan for Publications until the end of the project8 KB (1,085 words) - 17:56, 21 April 2017
- === Task NA1.3 Quality and Risk Management === **Formal plan sent to WP manager to complete work12 KB (1,723 words) - 15:04, 28 January 2016
- === Task NA1.3 Quality and Risk Management === ...s into other activities as well e.g. P4U, CloudSME; input to dissemination plan; identify concrete use cases7 KB (994 words) - 11:49, 7 September 2016
- === Task NA1.3 Quality and Risk Management === * D3.1 Technical design of the new Accounting Portal and implementation plan (https://documents.egi.eu/document/2545) --> to EC8 KB (1,047 words) - 10:23, 8 September 2015
- === Task NA1.3 Quality and Risk Management === * Defined plan for integration the EGI application platform to the marketplace9 KB (1,251 words) - 08:48, 6 April 2017
- === Task NA1.3 Quality and Risk Management === * CANFAR: work progressing to plan. A new release of the GMS is planned for September enabling cross-continent7 KB (998 words) - 10:20, 27 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'''12 KB (1,759 words) - 15:31, 7 November 2016
- ...cal nature of the activity bid must contain an availability and continuity plan for the service. == UMD and CMD quality assurance ==13 KB (1,910 words) - 09:55, 24 June 2021
- === Task NA1.3 Quality and Risk Management === *D2.9: "EGI Sustainability and Business Development Plan" (EGI.eu)8 KB (1,031 words) - 11:28, 16 December 2015
- Central MyEGI instance will reach production quality. * UK and Ireland plan to perform NGI creation in the next quarter.5 KB (802 words) - 18:59, 6 January 2015
- | How can I be sure the price is equal to the quality of resource? | Pricing / Service Quality14 KB (2,182 words) - 17:19, 25 March 2014
- === Task NA1.3 Quality and Risk Management === *Call with Anton, Celine, Sergio to define an activity plan and effort consumption (2 May)12 KB (1,642 words) - 10:38, 12 June 2017
- * Changes to activity plan to reflect management changes, central budget updates to be finalised TNA1.4 Quality assurance7 KB (991 words) - 23:05, 24 December 2014
- ** inform Project office if actual efforts and costs deviate from the plan; === Task NA1.3 Quality and Risk Management ===12 KB (1,703 words) - 13:01, 10 August 2017
- * Plan to release version 1.16.0 on: 2013-06-30 Product teams expressed interest in moving the EGI quality assurance process earlier in the PTs release process. In order to receive f11 KB (1,594 words) - 15:10, 8 July 2013
- * Telcon with STARnet gateway alliance - discuss topics of collaboration (plan for an MoU) Definition of UMD Quality Criteria5 KB (665 words) - 22:57, 24 December 2014
- === Task NA1.3 Quality and Risk Management === ...NDIGO WP3. I have been reading the INDIGO D3.1, that has a section of code quality.12 KB (1,607 words) - 15:32, 26 October 2015
- ...re and retrieve both local and EGI level sites in the central GOCDB. (This plan is from "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-5 | Provide a production quality package for GOCDB regional module || 4.0d7 || Oct 20106 KB (885 words) - 13:29, 18 December 2012
- To define the charging rate the plan is to use a new feature of GOCDB which is known as 'A Key-Value Pair Proper *it will allow more effectively plan the use of resources21 KB (3,114 words) - 14:27, 15 July 2016
- === Task NA1.3 Quality and Risk Management === No progress - quality manager on holidays and attending EGI conference (Collaboration board meeti11 KB (1,583 words) - 11:44, 14 June 2017
- ...and e-grant architecture review; review of e-grant work plan and LTOS work plan, reassignment === Task NA1.3 Quality and Risk Management ===17 KB (2,313 words) - 10:46, 14 October 2016
- ...VOMS <span class="il">services</span>, do NOT support IPv6 and there is no plan to support it ...nt-family:Arial;font-weight:normal;color:#000000;" bgcolor="#ffccff" | UMD quality assurance22 KB (3,261 words) - 14:32, 16 March 2020
- ...components within EMI are going to be assessed and the related timing. The plan also states which software packages that have been assessed so far. SVG wil ...bal oversight over the whole EGI infrastructure. This is to provide a high-quality grid infrastructure to the user communities. A ROD Newsletter is now period23 KB (3,456 words) - 16:19, 6 January 2015
- ...rck Molecular Force Field, either with or without solvent effect, to yield quality 3D molecular structures for use as input to other programs. In addition to ...few of them will be completed in the next quarter. In addition to this, we plan to organize Grid training event for NGI_AEGIS site administrators. The aim6 KB (895 words) - 11:41, 23 January 2015
- ...xpert know-how and ensures they have unique knowledge that is valuable for quality publications. | OS_IS_SoftwareRollout_HowToImprove = Latvian NGI sites plan to migrate to ARC to get middleware support from NDGF_NGI, as well as simpl12 KB (1,907 words) - 19:10, 19 December 2012
- * Plan to release version 1.16.0 on: 2013-06-30 EGI SA2 checks the Quality Control Criteria associated to the components during the verification step.13 KB (1,820 words) - 10:15, 4 December 2013
- ...al for Providers (Site Manager, NGI Manager) as it allows more effectively plan the use of resources and closer communication with Customers. *'''Quality of Service''' - Resource Provider can offer different types of access to re15 KB (2,150 words) - 17:12, 21 January 2015
- === Task NA1.3 Quality and Risk Management === * D2.13 (PM30) EGI Sustainability and Business Development Plan15 KB (2,177 words) - 12:05, 14 June 2017
- === Task NA1.3 Quality and Risk Management === * Defined plan for integration the EGI application platform to the marketplace: https://do10 KB (1,481 words) - 12:40, 6 April 2017
- ...ll be assessed at the beginning of March to understand the areas that need quality improvement. Discussion of CF2013 workshop agenda. * Updated Software Vulnerability Issue handling procedure. The original plan was to update due to end of EMI/IGE however most of the approved doc is agn7 KB (1,057 words) - 18:18, 6 January 2015
- ...dent on the software provided by our external technology providers and the quality of information (if provided) and their ability to meet their announced rele24 KB (3,040 words) - 14:48, 7 June 2021
- '''Help and support:''' quality@egi.eu This page describe data management plan for the research data that will be generated within EGI-Engage. For each da19 KB (2,890 words) - 15:33, 14 April 2016
- ...dissemination of results according to the Communications and Dissemination plan to be developed at the onset of the project. These channels will aim to str *Collect the Champions’ feedback to increase the quality and relevance of the publications and documentation produced by task NA2.1.25 KB (3,590 words) - 11:00, 13 July 2016
- ...nted their opinions. The communication was made hard by very bad technical quality of the Skype connection. Some of the voices were barely distinguishable. It ...elism, we plan to effectively manage the data on the cluster, and later we plan to use also MPI parallelism (http://www.mpi-forum.org/docs/mpi-11-html/mpi-11 KB (1,707 words) - 15:17, 19 June 2015
- * Changes to activity plan to reflect management changes, central budget updates TNA1.4 Quality assurance12 KB (1,734 words) - 23:05, 24 December 2014
- ...he users authentication is based on INFN AAI (part of IDEM Federation). We plan to put it in production and to open it to IDEM Federation in the next week ...ation of two training event with the purpose to improve the NGI_IT support quality, focused on:7 KB (1,078 words) - 19:18, 9 January 2015
- * Plan to release version: Update EMI 2 & EMI 3 - 31 Oct.2013 * Update about the Quality Criteria document to be circulated during the week through the ML.9 KB (1,269 words) - 14:41, 4 November 2013
- === Task NA1.3 Quality and Risk Management === *D2.13 (+D2.12) “EGI Sustainability and Business Development Plan” (M30 - EGI.eu)12 KB (1,697 words) - 15:06, 27 June 2017
- * Changes to activity plan to reflect management changes, central budget updates to be finalised TNA1.4 Quality assurance12 KB (1,709 words) - 23:04, 24 December 2014
- === Task NA1.3 Quality and Risk Management === **Initial discussions with Gergely to bridge activities with AGINFRA+ - plan/strategy to be defined12 KB (1,658 words) - 15:40, 10 February 2017
- Our plan is to release the Preview updates on a monthly basis, after having gathered ...e use of the UMD repositories, which contain software verified through the quality assurance process of UMD.''27 KB (3,377 words) - 11:48, 11 August 2021
- ...eteness of the resulting morphology. Yet, building a large library of high quality 3D cell morphologies is essential to comprehensively cataloging the types o Use story 2 would enable the building a large library of high quality 3D cell morphologies which is essential to comprehensively cataloging the t33 KB (4,816 words) - 09:42, 12 July 2016
- TNA1.4 Quality assurance ** Now managed by Neasan; programme for 2014 already has 4 events in the plan and more on preparation.12 KB (1,692 words) - 23:04, 24 December 2014