You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/00_BB_creation_template.yml
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ body:
104
104
id: usage_example
105
105
attributes:
106
106
label: BB Usage
107
-
description: Example on how to use BB or link to documentation
107
+
description: Example on how to use BB or link to documentation. Should include code snippets, information about usage, trainings, skills, examples and how-to's.
108
108
placeholder:
109
109
validations:
110
110
required: false
@@ -232,7 +232,7 @@ body:
232
232
- type: textarea
233
233
id: rel_projects
234
234
attributes:
235
-
label: Related Project(s)
235
+
label: Contribution supported by RDI projects
236
236
description: If Yes – e.g. The BB should be used/added in the Eclipse Blueprint A – for demo purposes, show added value, If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework
237
237
placeholder:
238
238
validations:
@@ -412,15 +412,6 @@ body:
412
412
validations:
413
413
required: false
414
414
415
-
- type: textarea
416
-
id: sys_context
417
-
attributes:
418
-
label: System Context
419
-
description: OS and runtime/framework requirements eg. AGL, QNX, ROS-based, container runtime, web assembly, web service
420
-
placeholder:
421
-
validations:
422
-
required: false
423
-
424
415
- type: dropdown
425
416
id: state
426
417
attributes:
@@ -437,6 +428,15 @@ body:
437
428
validations:
438
429
required: true
439
430
431
+
- type: textarea
432
+
id: sys_context
433
+
attributes:
434
+
label: System Context
435
+
description: OS and runtime/framework requirements eg. AGL, QNX, ROS-based, container runtime, web assembly, web service
Copy file name to clipboardExpand all lines: BB-CEST/Development-Testing-and-Simulation-Environments/Simulation-and-Emulation-Tools/BB_Eclipse_Cloe.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,4 @@
1
1
# Eclipse Cloe
2
-
3
2
## BB Tags(s)
4
3
<!-- Tag(s) define in which area(s) (cloud, in-vehicle) the BB is executed, and what type of BB it is (tool, process, microservice) -->
5
4
BB-CEST, BB-CSC-TC
@@ -12,7 +11,9 @@ BB-CEST, BB-CSC-TC
12
11
AppLayer
13
12
14
13
## BB Usage
15
-
<!-- example on how to use BB or link to documentation -->
14
+
<!-- Example on how to use BB or link to documentation. Should include code snippets, information about usage,
15
+
trainings, skills, examples and how-to's. -->
16
+
16
17
17
18
## Known Implementation
18
19
https://cloe.readthedocs.io/en/latest/
@@ -49,6 +50,7 @@ TBD
49
50
E.g. BB-SC StateManagement
50
51
BB is a composition of other BBs -->
51
52
53
+
52
54
## What is needed to Design and Implement
53
55
<!-- e.g. we expect to have a certain HW capability and or SW environment or Tool support, or a documentation, or an extra audit, or Test, or Compiler, or Prog. Language, … -->
54
56
@@ -69,15 +71,16 @@ TBD
69
71
If “No” – nothing more to do
70
72
If “Yes, proposal for additional Signals/Information – what should be made available, and where e.g. via (COVESA) VSS/VISS -->
71
73
74
+
72
75
## Author/Company
73
76
Eclipse Foundation
74
77
75
78
## Priority
76
79
<!-- High, Medium, Low -->
77
80
78
-
## Related Project(s)
81
+
## Contribution supported by RDI projects
79
82
<!-- If Yes – e.g. The BB should be used/added in the Eclipse Blueprint A – for demo purposes, show added value,
80
-
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework -->
83
+
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework)-->
81
84
TBD
82
85
83
86
## Availability of Source Code
@@ -124,7 +127,6 @@ Example:
124
127
TBD
125
128
126
129
## State (+ date of last change)
127
-
128
130
<!--
129
131
- Incubating (no code yet)
130
132
- Implementation started
@@ -136,7 +138,6 @@ TBD
136
138
First public release available
137
139
138
140
## System Context
139
-
140
141
<!--
141
142
OS and runtime/framework requirements
142
143
@@ -153,4 +154,4 @@ TBD
153
154
154
155
## Bazel compliance status
155
156
<!-- The S-CORE project requires all BB contributions to be ready for BAZEL compliant (https://github.com/bazelbuild/bazel)-->
Copy file name to clipboardExpand all lines: BB-CEST/Development-Testing-and-Simulation-Environments/Simulation-and-Emulation-Tools/BB_Eclipse_Mosaic.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,4 @@
1
1
# Eclipse Mosaic
2
-
3
2
## BB Tags(s)
4
3
<!-- Tag(s) define in which area(s) (cloud, in-vehicle) the BB is executed, and what type of BB it is (tool, process, microservice) -->
5
4
BB-CEST, BB-CSC-TC
@@ -12,7 +11,9 @@ BB-CEST, BB-CSC-TC
12
11
AppLayer
13
12
14
13
## BB Usage
15
-
<!-- example on how to use BB or link to documentation -->
14
+
<!-- Example on how to use BB or link to documentation. Should include code snippets, information about usage,
15
+
trainings, skills, examples and how-to's. -->
16
+
16
17
17
18
## Known Implementation
18
19
https://github.com/eclipse-mosaic/mosaic
@@ -38,6 +39,7 @@ TBD
38
39
E.g. BB-SC StateManagement
39
40
BB is a composition of other BBs -->
40
41
42
+
41
43
## What is needed to Design and Implement
42
44
<!-- e.g. we expect to have a certain HW capability and or SW environment or Tool support, or a documentation, or an extra audit, or Test, or Compiler, or Prog. Language, … -->
43
45
@@ -58,15 +60,16 @@ TBD
58
60
If “No” – nothing more to do
59
61
If “Yes, proposal for additional Signals/Information – what should be made available, and where e.g. via (COVESA) VSS/VISS -->
60
62
63
+
61
64
## Author/Company
62
65
Eclipse Foundation
63
66
64
67
## Priority
65
68
<!-- High, Medium, Low -->
66
69
67
-
## Related Project(s)
70
+
## Contribution supported by RDI projects
68
71
<!-- If Yes – e.g. The BB should be used/added in the Eclipse Blueprint A – for demo purposes, show added value,
69
-
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework -->
72
+
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework)-->
70
73
TBD
71
74
72
75
## Availability of Source Code
@@ -113,7 +116,6 @@ Example:
113
116
TBD
114
117
115
118
## State (+ date of last change)
116
-
117
119
<!--
118
120
- Incubating (no code yet)
119
121
- Implementation started
@@ -125,7 +127,6 @@ TBD
125
127
First public release available
126
128
127
129
## System Context
128
-
129
130
<!--
130
131
OS and runtime/framework requirements
131
132
@@ -142,4 +143,4 @@ TBD
142
143
143
144
## Bazel compliance status
144
145
<!-- The S-CORE project requires all BB contributions to be ready for BAZEL compliant (https://github.com/bazelbuild/bazel)-->
Copy file name to clipboardExpand all lines: BB-CEST/Development-Testing-and-Simulation-Environments/Simulation-and-Emulation-Tools/BB_Eclipse_SCM.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,4 @@
1
1
# Eclipse SCM
2
-
3
2
## BB Tags(s)
4
3
<!-- Tag(s) define in which area(s) (cloud, in-vehicle) the BB is executed, and what type of BB it is (tool, process, microservice) -->
5
4
BB-CEST, BB-CSC-TC
@@ -12,7 +11,9 @@ BB-CEST, BB-CSC-TC
12
11
AppLayer
13
12
14
13
## BB Usage
15
-
<!-- example on how to use BB or link to documentation -->
14
+
<!-- Example on how to use BB or link to documentation. Should include code snippets, information about usage,
15
+
trainings, skills, examples and how-to's. -->
16
+
16
17
17
18
## Known Implementation
18
19
https://gitlab.eclipse.org/eclipse/scm/scm
@@ -39,6 +40,7 @@ TBD
39
40
E.g. BB-SC StateManagement
40
41
BB is a composition of other BBs -->
41
42
43
+
42
44
## What is needed to Design and Implement
43
45
<!-- e.g. we expect to have a certain HW capability and or SW environment or Tool support, or a documentation, or an extra audit, or Test, or Compiler, or Prog. Language, … -->
44
46
@@ -59,15 +61,16 @@ TBD
59
61
If “No” – nothing more to do
60
62
If “Yes, proposal for additional Signals/Information – what should be made available, and where e.g. via (COVESA) VSS/VISS -->
61
63
64
+
62
65
## Author/Company
63
66
Eclipse Foundation
64
67
65
68
## Priority
66
69
<!-- High, Medium, Low -->
67
70
68
-
## Related Project(s)
71
+
## Contribution supported by RDI projects
69
72
<!-- If Yes – e.g. The BB should be used/added in the Eclipse Blueprint A – for demo purposes, show added value,
70
-
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework -->
73
+
If No – Project Proposal (e.g. WP4 in FEDERATE, or in the SDV EcoSystem Community Framework)-->
71
74
TBD
72
75
73
76
## Availability of Source Code
@@ -114,7 +117,6 @@ Example:
114
117
TBD
115
118
116
119
## State (+ date of last change)
117
-
118
120
<!--
119
121
- Incubating (no code yet)
120
122
- Implementation started
@@ -126,7 +128,6 @@ TBD
126
128
First public release available
127
129
128
130
## System Context
129
-
130
131
<!--
131
132
OS and runtime/framework requirements
132
133
@@ -143,4 +144,4 @@ TBD
143
144
144
145
## Bazel compliance status
145
146
<!-- The S-CORE project requires all BB contributions to be ready for BAZEL compliant (https://github.com/bazelbuild/bazel)-->
0 commit comments