Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found
Select Git revision
  • master
  • 0.1.0
  • 0.1.1
3 results

Target

Select target project
  • oss/utilities/requirements-manager
1 result
Select Git revision
  • master
  • 0.1.0
  • 0.1.1
3 results
Show changes
Showing
with 1913 additions and 1282 deletions
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
---
null
...
ID: ID1-22
Title: null
# Reference to other requirements
References: null
# Display, Functional, Performance, Printing, Report, Testing or Validation
Type: null
Alias: null
Keywords:
- Requirement
Keywords: - Requirement
# First and last name of the authors as a list
Author:
- null
Author: - null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
Complexity: null
# Low, Medium, Hi
Difficulty: null
# Nice to have, Low, Medium, Hi or Blocker
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
# Valid time units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, “h”.
Time Spent: 5h
# who is the source of the demand
Source: null
Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
Items: - ID: null
Name: null # what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null # does this belong to a group
Group: null
Description: null
Delivery until: null # when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy: - ID: null # Purpose of the data processing, # for example, shipping an order and handing it over to a shipping service provider.
Purposes: null # More detailed description of the reason and process of data processing.
Description: null # Who is responsible for data protection
Contact: null # But working with these categories might end up being a bad idea since doing so might # mean packing different things into one. This leads to either oversimplifications or # a lot of specifications within a category. It might be advisable to split some of them # up or to add additional ones to make them fit your business reality. # Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null #
Category: # Example: 5 years from the payment of the salary
Data Retention Period: null # On what legal basis is the data collected # Special legal regulation outside the GDPR # Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field # Collective agreement (e.g. company agreement, collective agreement) # Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG) # Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.) # Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null # “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or # her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies # his or her agreement to personal data relating to him or her being processed.
Consent: null # Where applicable, transfers of personal data to a third country or an international organisation, including # the identification of that third country or international organisation and, in the case of transfers referred # to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers: # Where possible, a general description of the technical and organisational # security measures referred to in Article 32(1).
TOM: null
### {{ .Title }} - {{ .ID }}
......@@ -105,39 +103,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
......@@ -7,18 +7,18 @@ References: null
Type: null
Alias: null
Keywords:
- Requirement
- Requirement
# First and last name of the authors as a list
Author:
- null
- null
# Proposed (The requirement has been requested by an authorized source.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# In Progress (A business analyst is actively working on crafting the requirement.),
# Drafted (The initial version of the requirement has been written.),
# Approved (The requirement has been analyzed, its impact on the project has been estimated, and it has been allocated to the baseline for a specific release. ),
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Implemented (The code that implements the requirement has been designed, written, and unit tested. The requirement has been traced to the pertinent design and code elements. It’s now ready for review or other verification.),
# Verified (The requirement has satisfied its acceptance criteria, meaning that the correct functioning of the implemented requirement has been confirmed.),
# Deferred (An approved requirement is now planned for implementation in a later release.),
# Deleted (An approved requirement has been removed from the baseline.) or
# Rejected (The requirement was proposed but was never approved and is not planned for implementation in any upcoming release.)
Status: "Proposed"
# Low, Medium, Hi
......@@ -29,7 +29,7 @@ Difficulty: null
Priority: null
Version: 0.0.1
Milestone: null
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 0 (means that a task has already been completed), 1 (is a very small task), 2, 3, 5 (are rather smaller tasks),
# 8, 13, 20, 40, 100
Estimation: 40
# The time required for this requirement
......@@ -41,62 +41,58 @@ Created: 2022-05-03
Last Update: null
# the individual items as a list
Items:
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
- ID: null
Name: null
# what is it, a image, font, legal information, access data, texts, decisions, etc.
Type: null
# does this belong to a group
Group: null
Description: null
Delivery until: null
# when was the project items delivered and by whom?
Provided on: null
Provided by: null
# https://gdpr-info.eu/art-30-gdpr/
Privacy:
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
- ID: null
# Purpose of the data processing,
# for example, shipping an order and handing it over to a shipping service provider.
Purposes: null
# More detailed description of the reason and process of data processing.
Description: null
# Who is responsible for data protection
Contact: null
# But working with these categories might end up being a bad idea since doing so might
# mean packing different things into one. This leads to either oversimplifications or
# a lot of specifications within a category. It might be advisable to split some of them
# up or to add additional ones to make them fit your business reality.
# Examples: Employees, Suppliers, Customers, Job applicants, Consultants, Visitors, Prospects, Contractors, Trainees
Affected Groups: null
#
Category:
# Example: 5 years from the payment of the salary
Data Retention Period: null
# On what legal basis is the data collected
# Special legal regulation outside the GDPR
# Consent of the data subject (Art. 6 para. 1 a) DSG-VO) use Consent field
# Collective agreement (e.g. company agreement, collective agreement)
# Establishment, performance or termination of an employment relationship (nationally regulated in the BDSG)
# Contract or initiation of a contract with the data subject (Art. 6 para. 1 b) DSG-VO.)
# Balancing of interests (Art. 6 para. 1 f) DSG-VO): Please name the overriding interests
Legal Basis: null
# “Consent” of the data subject refers to any freely given specific, informed and unambiguous indication of his or
# her wishes in the form of a statement or other unambiguous affirmative act by which the data subject signifies
# his or her agreement to personal data relating to him or her being processed.
Consent: null
# Where applicable, transfers of personal data to a third country or an international organisation, including
# the identification of that third country or international organisation and, in the case of transfers referred
# to in the second subparagraph of Article 49(1), the documentation of suitable safeguards;
Transfers:
# Where possible, a general description of the technical and organisational
# security measures referred to in Article 32(1).
TOM: null
...
### {{ .Title }} - {{ .ID }}
#### Subheading
......@@ -104,39 +100,35 @@ Privacy:
- [ ] task 1
- [ ] task 2
{{ if .Items }}
#### Items
| ID | Name | Delivery until | Provided on |
|--------------------|--------------|----------------------:|-----------------------------------------:|
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
| ID | Name | Delivery until | Provided on |
| --- | ---- | -------------: | ----------: |
{{ range .Items
}}| {{ .ID }} | {{ .Name }} | {{ .DeliveryUntil.Format "02.Jan" }} | {{ .ProvidedOn.Format "02.Jan" }} |
{{ end }}
{{ end }}
{{ if .Privacy }}
#### Privacy
{{ range .Privacy }}
**{{ .Purposes }} ({{ .ID }})**
**{{ .Purposes }} ({{ .ID }})**
{{ .Description }}
| | |
|--|--|
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
| | |
| --------------------- | -------------------------- |
| Category | {{ .Category }} |
| Data Retention Period | {{ .DataRetentionPeriod }} |
| Legal Basis | {{ .LegalBasis }} |
| Transfers | {{ .Transfers }} |
{{ end }}
{{ end }}
{
"nodes": {
"devenv": {
"locked": {
"dir": "src/modules",
"lastModified": 1710819219,
"narHash": "sha256-SXTz20R4ZDXwr3iPxXJXQTftHmZwOPzSpIK7bIIculA=",
"owner": "cachix",
"repo": "devenv",
"rev": "169d2cbce65977289f2e0e863a4e8f42f9ce98af",
"type": "github"
},
"original": {
"dir": "src/modules",
"owner": "cachix",
"repo": "devenv",
"type": "github"
}
},
"flake-compat": {
"flake": false,
"locked": {
"lastModified": 1696426674,
"narHash": "sha256-kvjfFW7WAETZlt09AgDn1MrtKzP7t90Vf7vypd3OL1U=",
"owner": "edolstra",
"repo": "flake-compat",
"rev": "0f9255e01c2351cc7d116c072cb317785dd33b33",
"type": "github"
},
"original": {
"owner": "edolstra",
"repo": "flake-compat",
"type": "github"
}
},
"flake-utils": {
"inputs": {
"systems": "systems"
},
"locked": {
"lastModified": 1710146030,
"narHash": "sha256-SZ5L6eA7HJ/nmkzGG7/ISclqe6oZdOZTNoesiInkXPQ=",
"owner": "numtide",
"repo": "flake-utils",
"rev": "b1d9ab70662946ef0850d488da1c9019f3a9752a",
"type": "github"
},
"original": {
"owner": "numtide",
"repo": "flake-utils",
"type": "github"
}
},
"gitignore": {
"inputs": {
"nixpkgs": [
"pre-commit-hooks",
"nixpkgs"
]
},
"locked": {
"lastModified": 1709087332,
"narHash": "sha256-HG2cCnktfHsKV0s4XW83gU3F57gaTljL9KNSuG6bnQs=",
"owner": "hercules-ci",
"repo": "gitignore.nix",
"rev": "637db329424fd7e46cf4185293b9cc8c88c95394",
"type": "github"
},
"original": {
"owner": "hercules-ci",
"repo": "gitignore.nix",
"type": "github"
}
},
"nixpkgs": {
"locked": {
"lastModified": 1710695816,
"narHash": "sha256-3Eh7fhEID17pv9ZxrPwCLfqXnYP006RKzSs0JptsN84=",
"owner": "nixos",
"repo": "nixpkgs",
"rev": "614b4613980a522ba49f0d194531beddbb7220d3",
"type": "github"
},
"original": {
"owner": "nixos",
"ref": "nixos-23.11",
"repo": "nixpkgs",
"type": "github"
}
},
"nixpkgs-stable": {
"locked": {
"lastModified": 1710695816,
"narHash": "sha256-3Eh7fhEID17pv9ZxrPwCLfqXnYP006RKzSs0JptsN84=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "614b4613980a522ba49f0d194531beddbb7220d3",
"type": "github"
},
"original": {
"owner": "NixOS",
"ref": "nixos-23.11",
"repo": "nixpkgs",
"type": "github"
}
},
"nixpkgs_2": {
"locked": {
"lastModified": 1710695816,
"narHash": "sha256-3Eh7fhEID17pv9ZxrPwCLfqXnYP006RKzSs0JptsN84=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "614b4613980a522ba49f0d194531beddbb7220d3",
"type": "github"
},
"original": {
"id": "nixpkgs",
"ref": "nixos-23.11",
"type": "indirect"
}
},
"pre-commit-hooks": {
"inputs": {
"flake-compat": "flake-compat",
"flake-utils": "flake-utils",
"gitignore": "gitignore",
"nixpkgs": [
"nixpkgs"
],
"nixpkgs-stable": "nixpkgs-stable"
},
"locked": {
"lastModified": 1710843117,
"narHash": "sha256-b6iKQeHegzpc697rxTPA3bpwGN3m50eLCgdQOmceFuE=",
"owner": "cachix",
"repo": "pre-commit-hooks.nix",
"rev": "e8dc1b4fe80c6fcededde7700e6a23bcdf7f3347",
"type": "github"
},
"original": {
"owner": "cachix",
"repo": "pre-commit-hooks.nix",
"type": "github"
}
},
"root": {
"inputs": {
"devenv": "devenv",
"nixpkgs": "nixpkgs",
"pre-commit-hooks": "pre-commit-hooks",
"version": "version"
}
},
"systems": {
"locked": {
"lastModified": 1681028828,
"narHash": "sha256-Vy1rq5AaRuLzOxct8nz4T6wlgyUR7zLU309k9mBC768=",
"owner": "nix-systems",
"repo": "default",
"rev": "da67096a3b9bf56a91d16901293e51ba5b49a27e",
"type": "github"
},
"original": {
"owner": "nix-systems",
"repo": "default",
"type": "github"
}
},
"version": {
"inputs": {
"nixpkgs": "nixpkgs_2"
},
"locked": {
"lastModified": 1704542622,
"narHash": "sha256-HnFuaOXHoxv8tpBvMsEjfhcl/hFNxEY7GbBqoyJ1U8U=",
"ref": "refs/heads/master",
"rev": "6b4f85fe6d934429cf3055bbcd8cf15014730118",
"revCount": 114,
"type": "git",
"url": "https://gitlab.schukai.com/oss/utilities/version.git"
},
"original": {
"type": "git",
"url": "https://gitlab.schukai.com/oss/utilities/version.git"
}
}
},
"root": "root",
"version": 7
}
# See full reference at https://devenv.sh/reference/options/
{
pkgs,
inputs,
phps,
lib,
config,
modulesPath,
...
}: let
taskfileYaml = let
ciJobToken = builtins.getEnv "CI_JOB_TOKEN";
gitCommit =
if ciJobToken == ""
then (builtins.getFlake "git+https://gitlab.schukai.com/schukai/entwicklung/nix-flakes").packages.${builtins.currentSystem}.git-commit
else "";
goPkgReleaseData = import ./project.nix;
goPkgName = goPkgReleaseData.name or "goPkg";
goPkgMnemonic = goPkgReleaseData.mnemonic or "go-pkg";
in
pkgs.writeTextFile {
name = "Taskfile.yaml";
text = ''
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
version: '3'
tasks:
build:
desc: Build the app
aliases:
- b
cmds:
- build-app
sources:
- source/*.go
- source/**/*.go
- source/go.mod
- dist/**
git-commit:
desc: Commit changes to git
cmds:
- ${gitCommit}/bin/git-commit
silent: true
default:
desc: Print this help message
aliases: [d, help]
cmds:
- task --list
silent: true
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
'';
};
treefmtConfig = pkgs.writeTextFile {
name = "treefmt.toml";
text = ''
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
[formatter.nix]
command = "${pkgs.alejandra}/bin/alejandra"
options = []
includes = [ "*.nix" ]
#excludes = [ "devenv.nix" ]
[formatter.go]
command = "${pkgs.go}/bin/gofmt"
options = ["-w"]
includes = [ "*.go" ]
excludes = []
#[formatter.php]
#command = "${pkgs.php83Packages.php-cs-fixer}/bin/php-cs-fixer"
#options = ["fix"]
#includes = [ "*.php" ]
#excludes = []
[formatter.shell]
command = "${pkgs.shfmt}/bin/shfmt"
options = ["-w"]
includes = [ "*.sh", "*.bash" ]
excludes = []
[formatter.prettier]
command = "${pkgs.nodePackages.prettier}/bin/prettier"
options = ["--write","--plugin=${pkgs.nodePackages.prettier-plugin-toml}/lib/node_modules/prettier-plugin-toml/lib/api.js"]
includes = [
"*.css",
"*.html",
"*.js",
"*.mjs",
"*.json",
"*.xml",
"*.toml",
"*.jsx",
"*.md",
"*.mdx",
"*.scss",
"*.ts",
"*.yml",
"*.yaml"]
excludes = ["treefmt.toml", "Taskfile.yml", "node_modules"]
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
'';
};
gitlabCiYaml = pkgs.writeTextFile {
name = ".gitlab-ci.yml";
text = ''
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
image: docker-registry.schukai.com:443/nixos-ci-devenv:latest
#services:
# - docker:dind
variables:
NIXOS_VERSION: "23.11"
NIXPKGS_ALLOW_UNFREE: "1"
NIXPKGS_ALLOW_INSECURE: "1"
#DOCKER_DRIVER: overlay2
stages:
- tag
- release
# if you want to debug the ci pipeline, uncomment the following lines
#debug:
# tags:
# - nixos
# stage: tag
# script:
# - export
tag-it:
tags:
- nixos
stage: tag
script:
- devenv shell tag-version
rules:
- if: '$CI_COMMIT_TAG'
when: never
- if: '$CI_COMMIT_TAG_MESSAGE =~ /DO_RELEASE/'
when: never
- if: '$CI_COMMIT_MESSAGE =~ /Bump version/'
when: never
- when: on_success
release:
tags:
- nixos
stage: release
rules:
- if: '$CI_COMMIT_TAG_MESSAGE =~ /DO_RELEASE/'
when: on_success
- when: never
variables:
# Disable shallow cloning so that goreleaser can diff between tags to
GIT_DEPTH: 0
script:
- devenv shell deploy-app
#- cd source; goreleaser release --clean
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
'';
};
goReleaserYaml = let
goPkgReleaseData = import ./project.nix;
goPkgName = goPkgReleaseData.name or "goPkg";
goPkgMnemonic = goPkgReleaseData.mnemonic or "go-pkg";
in
pkgs.writeTextFile {
name = ".goreleaser.yml";
text = ''
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
gitlab_urls:
api: https://gitlab.schukai.com/api/v4
download: https://gitlab.schukai.com
# set to true if you use a self-signed certificate
skip_tls_verify: false
use_package_registry: true
# Set this if you set GITLAB_TOKEN to the value of CI_JOB_TOKEN.
# Since: v1.11
use_job_token: false
project_name: ${goPkgMnemonic}
builds:
- id: ${goPkgMnemonic}
goos:
- linux
- darwin
- windows
dir: ${config.devenv.root}/source
ldflags:
- -s -w
- -X main.version={{.Version}}
- -X 'main.commit={{.Commit}}'
- -X 'main.build={{.Date}}'
- -X 'main.mnemonic=${goPkgMnemonic}'
- -X 'main.name=${goPkgName}'
## DO NOT EDIT THIS FILE MANUALLY, IT IS GENERATED BY NIX
'';
};
in {
env.APP_NAME = let
goPkgReleaseData = import ./project.nix;
goPkgMnemonic = goPkgReleaseData.mnemonic or "go-pkg";
in
goPkgMnemonic;
# https://devenv.sh/packages/
packages = with pkgs; [
inputs.version.defaultPackage."${builtins.currentSystem}"
appimage-run
goreleaser
go-tools
awscli2
blackbox
blackbox-terminal
coreutils-full
d2
dbeaver
delve
dialog
dive
docker-client
docker-compose
drill
eza
fd
gawk
gcc12
gdlv
git
glab
gnugrep
gnum4
gnumake
gnupg
gnused
go-task
graphviz
treefmt
gum
httpie
hurl
jq
libffi
libffi
logrotate
mdbook
mdbook-admonish
mdbook-cmdrun
mdbook-d2
mdbook-emojicodes
mdbook-graphviz
mdbook-linkcheck
mdbook-mermaid
mdbook-pdf
meld
memcached
netcat
netcat
oha
openai
oxker
pandoc-katex
plantuml
pprof
procps
ranger
termbook
unixtools.arp
unixtools.xxd
unzip
util-linux
wget
zlib
];
scripts.tag-version.exec = ''
#!${pkgs.bash}/bin/bash
if [[ -z "''${CI_JOB_TOKEN}" ]]; then
echo " ✖ Not in gitlab ci."
exit 0
fi
set -x
${pkgs.git}/bin/git config user.email "''${GITLAB_USER_EMAIL}"
${pkgs.git}/bin/git config user.name "''${GITLAB_USER_NAME:-"Gitlab CI"}"
${pkgs.git}/bin/git config credential.helper '!f() { echo "username=gitlab-ci-token"; echo "password=''${CI_JOB_TOKEN}"; }; f'
${pkgs.git}/bin/git config pull.rebase true
${pkgs.git}/bin/git config http.sslVerify "false"
${pkgs.git}/bin/git remote set-url origin https://pad:''${GITLAB_TOKEN}@''${CI_REPOSITORY_URL#*@}
${pkgs.git}/bin/git fetch --all --tags --unshallow
${pkgs.git}/bin/git reset --hard origin/master
${pkgs.git}/bin/git checkout $CI_COMMIT_REF_NAME
${pkgs.git}/bin/git pull origin $CI_COMMIT_REF_NAME
NEWVERSION=$(${inputs.version.defaultPackage."${builtins.currentSystem}"}/bin/version predict --git exit-code-if-no-bump)
if [[ $? -ne 0 ]]; then
echo " ✖ No bump wanted."
exit 0
fi
if [[ -z "''${NEWVERSION}" ]]; then
echo " ✖ No version found."
exit 0
fi
sed -i "s/version\s*=\s*\".*\"/version = \"''${NEWVERSION}\"/" ${config.devenv.root}/project.nix
${pkgs.git}/bin/git add ${config.devenv.root}/project.nix
${pkgs.git}/bin/git commit -m "chore: Bump version to ''${NEWVERSION}"
${pkgs.git}/bin/git log --decorate=short --pretty=oneline
${pkgs.git}/bin/git tag -a "''${NEWVERSION}" -m "chore: Release ''${NEWVERSION} - DO_RELEASE"
${pkgs.git}/bin/git push origin $CI_COMMIT_REF_NAME --tags
'';
scripts.common-functions.exec = ''
if [ -t 1 ]; then
RED='\033[0;31m'
GREEN='\033[0;32m'
BLUE='\033[0;34m'
RESET='\033[0m'
BOLD='\033[1m'
else
RED=""
GREEN=""
RESET=""
fi
is_true() {
val="$1"
if [ "$val" = 'true' ] || [ "$val" = '1' ]; then
return 0
else
return 1
fi
}
get_commit_hash() {
hash=""
if [[ -n "$CI_COMMIT_SHORT_SHA" ]]; then
hash="$CI_COMMIT_SHORT_SHA"
else
hash="$(git rev-parse --short HEAD)"
if [[ -n "$(git status --porcelain)" ]]; then
hash="''${hash}-dirty"
fi
fi
echo "$hash"
}
echo_green() {
echo -e "$GREEN ✔ $1$RESET"
}
echo_red() {
echo -e "$RED ✖ $1$RESET"
}
echo_todo() {
echo_bold "$BLUE • $1"
}
update_project_version() {
if version auto --git --exit-code-if-no-bump --verbose
then
buildVer=$(version print --git)
local project_nix="${config.devenv.root}/project.nix"
sed -i "s/^\s*version\s*=.*/ version = \"$buildVer\";/" "$project_nix"
echo_green "Project version updated to $buildVer"
${pkgs.git}/bin/git add "$project_nix"
${pkgs.git}/bin/git commit -m "chore: Update project version to $buildVer" "$project_nix"
${pkgs.git}/bin/git tag -f -a "$buildVer" -m "Release $buildVer"
if is_true "$CI_MODE"; then
${pkgs.git}/bin/git push -o ci.skip origin ''${CI_COMMIT_REF_NAME} --tags
fi
else
echo_green "Project version is up to date"
fi
}
get_project_version() {
echo "$(version print --git)"
}
if [ -z "$DEBUG_MODE" ]; then
DEBUG_MODE='false'
fi
if [ -n "$CI_JOB_TOKEN" ]; then
CI_MODE='true'
fi
if is_true "$DEBUG_MODE" || is_true "$CI_MODE"; then
set -x
fi
'';
scripts.update-files.exec = ''
#!${pkgs.bash}/bin/bash
source common-functions
create_symlink() {
if ln -s "$1" "$2" 2>/dev/null; then
echo_green "$2 created"
else
echo_red "$2 already exists"
fi
}
update_symlink() {
echo -e " → $1"
local source_path="$1"
local target_path="$2"
local file_name="$(basename "$target_path")"
local source_dir="$(dirname "$source_path")"
mkdir -p "$source_dir" || true
if [[ ! -d "$source_dir" ]]; then
echo_red "$RED ✖ $source_dir is not a directory. Please remove it manually and run the script again."
exit 1
fi
if [[ -L "$source_path" ]]; then
if [[ "$(readlink "$source_path")" != "$target_path" ]]; then
rm "$source_path"
create_symlink "$target_path" "$source_path"
echo_green "$GREEN ✔ $source_path updated$RESET"
else
echo_green "$GREEN ✔ $source_path is up to date$RESET"
fi
elif [[ -e "$source_path" ]]; then
echo_red "$RED ✖ $source_path already exists and is not a symlink. Please remove it manually and run the script again."
exit 1
else
create_symlink "$target_path" "$source_path"
fi
}
# Usage for Taskfile.yaml
update_symlink "${config.devenv.root}/Taskfile.yaml" "${taskfileYaml}"
update_symlink "${config.devenv.root}/.goreleaser.yml" "${goReleaserYaml}"
update_symlink "${config.devenv.root}/treefmt.toml" "${treefmtConfig}"
cat ${gitlabCiYaml} > "${config.devenv.root}/.gitlab-ci.yml"
'';
languages = {
go = {enable = true;};
};
difftastic.enable = true;
scripts.get-commit-hash.exec = ''
#!${pkgs.bash}/bin/bash
hash=""
if [[ -n "$CI_COMMIT_SHORT_SHA" ]]; then
hash="$CI_COMMIT_SHORT_SHA"
else
hash="$(git rev-parse --short HEAD)"
if [[ -n "$(git status --porcelain)" ]]; then
hash="''${hash}-dirty"
fi
fi
echo "$hash"
'';
## this script should be run after debugging the ci pipeline
scripts.delete-pipeline.exec = ''
#!${pkgs.bash}/bin/bash
pipeline_list=$(glab ci list)
commit_hashes=$(echo "$pipeline_list" | awk '/#/{print $3}')
for hash in $commit_hashes; do
hh=$(echo "$hash" | cut -d"#" -f2)
echo "found hash: $hh"
glab ci delete "$hh"
done
echo "done"
'';
scripts.build-app.exec = ''
#!${pkgs.bash}/bin/bash
${pkgs.treefmt}/bin/treefmt
update-hashes
${pkgs.nix}/bin/nix build .#reqman
'';
scripts.deploy-app.exec = ''
#!${pkgs.bash}/bin/bash
${pkgs.goreleaser}/bin/goreleaser release --clean --config ${config.devenv.root}/.goreleaser.yml
'';
scripts.update-hashes.exec = ''
#!${pkgs.bash}/bin/bash
sed -i 's/vendorHash\s*=\s*".*"/vendorHash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="/' ${config.devenv.root}/project.nix
HASH=$(${pkgs.nix}/bin/nix build 2>&1 | grep 'got:' | awk '{print $2}')
sed -i "s/vendorHash\s*=\s*\".*\"/vendorHash = \"''${HASH}\"/" ${config.devenv.root}/project.nix
'';
enterShell = ''
update-files
'';
}
inputs:
nixpkgs:
url: github:nixos/nixpkgs/nixos-23.11
version:
url: git+https://gitlab.schukai.com/oss/utilities/version.git
flake: true
{
"nodes": {
"nixpkgs": {
"locked": {
"lastModified": 1710695816,
"narHash": "sha256-3Eh7fhEID17pv9ZxrPwCLfqXnYP006RKzSs0JptsN84=",
"owner": "NixOS",
"repo": "nixpkgs",
"rev": "614b4613980a522ba49f0d194531beddbb7220d3",
"type": "github"
},
"original": {
"id": "nixpkgs",
"ref": "nixos-23.11",
"type": "indirect"
}
},
"root": {
"inputs": {
"nixpkgs": "nixpkgs"
}
}
},
"root": "root",
"version": 7
}