Skip to content

Commit 93a67a1

Browse files
mariojmdavidmariojmdavid
committed
small type corrections, markdown line format
1 parent 3580d4f commit 93a67a1

File tree

8 files changed

+229
-232
lines changed

8 files changed

+229
-232
lines changed

‎content/01.abstract.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Abstract {.page_break_before}
22

3-
The purpose of this document is to define a set of quality standards,
4-
procedures and best practices to conform a Software Quality Assurance plan to
5-
serve as a reference within the European research ecosystem related projects
6-
for the adequate development and timely delivery of software products.
3+
The purpose of this document is to define a set of quality standards, procedures and best practices
4+
to conform a Software Quality Assurance plan to serve as a reference within the European research
5+
ecosystem related projects for the adequate development and timely delivery of software products.

‎content/02.0.copyright-ack.md‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,13 @@
11
# Copyright Notice
22

3-
Copyright © Members of the INDIGO-DataCloud, DEEP Hybrid-DataCloud eXtreme
4-
DataCloud and EOSC-Synergy collaborations, 2015-2021.
3+
Copyright © Members of the INDIGO-DataCloud, DEEP Hybrid-DataCloud eXtreme DataCloud and
4+
EOSC-Synergy collaborations, 2015-2021.
55

66
# Acknowledgements
77

8-
The INDIGO-DataCloud, DEEP-Hybrid-DataCloud, eXtreme-DataCloud and
9-
EOSC-Synergy projects have received funding from the European Union’s
10-
Horizon 2020 research and innovation programme under grant agreement
11-
number 653549, 777435, 777367 and 857647 respectively.
8+
The INDIGO-DataCloud, DEEP-Hybrid-DataCloud, eXtreme-DataCloud and EOSC-Synergy projects have
9+
received funding from the European Union’s Horizon 2020 research and innovation programme under
10+
grant agreement number 653549, 777435, 777367 and 857647 respectively.
1211

1312
<p align="center">
1413
<img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcT1WF4g5KH3PnQE_Ve10QFRS-gZ0NpCQ7Qr-_km1RqnOCEF1fQt">

‎content/02.document-log.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,4 @@
88
| v3.1 | 05/03/2020 | Add tags/names for each criteria |
99
| v3.2 | 23/04/2020 | Add EOSC-Synergy to copyright |
1010
| v3.3 | 15/10/2020 | Fix issues: #32, #46, #47, #48, #49, #51 |
11-
| v4.0 | 2021 | Add annex, spell check, Fix issues: #7, #57, #59, #60, #61, #63, #64 |
11+
| v4.0 | 12/2021 | Add annex, spell check, Fix issues: #7, #35, #50, #57, #59, #60, #61, #63, #64, #65, #66 |

‎content/03.intro.md‎

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,16 @@
11
# 1. Introduction and Purpose {.page_break_before}
22

3-
This document has been tailored upon the recommendations and requirements found
4-
in the Initial Plan for Software Management and Pilot Services deliverable
5-
[@url:https://owncloud.indigo-datacloud.eu/index.php/s/yDklCrWjKnjutVA],
6-
produced by the INDIGO-DataCloud project. These guidelines evolved throughout
7-
the project’s lifetime and are being extended in the
8-
EOSC-Synergy [@doi:10.20350/digitalCSIC/12607],
9-
as well as as the past DEEP-Hybrid-DataCloud and eXtreme DataCloud subsequent projects.
10-
The result is a consolidated Software Quality Assurance (SQA) baseline criteria emanated
11-
from the European Open Science Cloud (EOSC), which aims to outline the SQA
12-
principles to be considered in the upcoming software development efforts within
13-
the European research community, and continuously evolve in order to be aligned
14-
with future software engineering practices and security recommendations.
3+
This document has been tailored upon the recommendations and requirements found in the Initial Plan
4+
for Software Management and Pilot Services deliverable
5+
[@url:https://owncloud.indigo-datacloud.eu/index.php/s/yDklCrWjKnjutVA], produced by the
6+
INDIGO-DataCloud project.
7+
8+
These guidelines evolved throughout the project’s lifetime and are being extended in the
9+
EOSC-Synergy [@doi:10.20350/digitalCSIC/12607], as well as the past DEEP-Hybrid-DataCloud and
10+
eXtreme DataCloud subsequent projects.
11+
12+
The result is a consolidated Software Quality Assurance (SQA) baseline criteria emanated from the
13+
European Open Science Cloud (EOSC), which aims to outline the SQA principles to be considered in the
14+
upcoming software development efforts within the European research community, and continuously
15+
evolve in order to be aligned with future software engineering practices and security
16+
recommendations.

‎content/04.goals.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@
99
3. Promote code style standards to deliver good quality source code emphasizing its readability and
1010
reusability.
1111

12-
4. Improve the quality and reliability of software by covering different
13-
testing methods at development and pre-production stages.
12+
4. Improve the quality and reliability of software by covering different testing methods at
13+
development and pre-production stages.
1414

1515
5. Propose a change-based driven scenario where all new updates in the source code are continuously
1616
validated by the automated execution of the relevant tests.

‎content/05.notational_conventions.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# 3. Notational Conventions
22

3-
The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
4-
“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be
5-
interpreted as described in RFC 2119 [@https://www.rfc-editor.org/info/rfc2119].
3+
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
4+
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119
5+
[@https://www.rfc-editor.org/info/rfc2119].

0 commit comments

Comments
 (0)