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/---enhancement-request.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,24 +4,27 @@ about: Propose an addition or change to the FDC3 standard!
4
4
title: ''
5
5
labels: enhancement
6
6
assignees: ''
7
-
8
7
---
9
8
10
9
## Enhancement Request
11
10
12
-
### Use Case:
13
-
...please specify at least one use case that this enhancement would support
11
+
### Use Case
12
+
13
+
<!--- Please specify at least one use case that this enhancement would support
14
14
15
-
... a use case should not be a solution, but a description of a problem from an end user point of view.
15
+
A use case should not be a solution, but a description of a problem from an end user point of view.
16
16
17
17
For example:
18
-
> Often, end users want to link from one app to another to dynamically create a workflow without prior knowledge of the app they want to connect to. For example, using the 'share' feature allows an end user to dynamically discover what apps they have that support social sharing and no advanced knowledge is required by the end user.
18
+
> Often, end users want to link from one app to another to dynamically create a workflow without prior knowledge of the app they want to connect to. For example, using the 'share' feature allows an end user to dynamically discover what apps they have that support social sharing and no advanced knowledge is required by the end user. --->
19
19
20
20
### Workflow Description
21
-
...clearly and concisely describe the target workflow for the prosed enhancement.
21
+
22
+
<!--- clearly and concisely describe the target workflow for the proposed enhancement --->
22
23
23
24
### Workflow Examples
24
-
... provide one or more concrete examples of the proposed workflow.
25
+
26
+
<!--- provide one or more concrete examples of the proposed workflow --->
25
27
26
28
### Additional Information
27
-
... please add any other information that can provide additional detail for this enhancement request
29
+
30
+
<!--- please add any other information that can provide additional detail for this enhancement request --->
Please use minor issues for discrepancies or errors found in the spec or supporting documentation, examples, and other materials. If you wish to propose a new feature or a revision to an existing feature, please use the *Enhancement Request* template.
10
+
11
+
<!-- Please use minor issues for discrepancies or errors found in the spec or supporting documentation, examples, and other materials. If you wish to propose a new feature or a revision to an existing feature, please use the *Enhancement Request* template. -->
12
12
13
13
### Area of Issue
14
-
-[ ] App Directory
15
-
-[ ] API
16
-
-[ ] Context Data
17
-
-[ ] Intents
18
-
-[ ] Desktop Agent Bridging
19
-
-[ ] Use Cases
20
-
-[ ] Other
21
-
22
-
### Issue Description:
23
-
...please provide a detailed description of the issue
24
-
25
-
### Additional Context:
26
-
...add any other context about the problem here. If applicable, add screenshots to help explain...
14
+
15
+
-[ ] App Directory
16
+
-[ ] API
17
+
-[ ] Context Data
18
+
-[ ] Intents
19
+
-[ ] Desktop Agent Bridging
20
+
-[ ] Use Cases
21
+
-[ ] Other
22
+
23
+
### Issue Description
24
+
25
+
<!--- please provide a detailed description of the issue --->
26
+
27
+
### Additional Context
28
+
29
+
<!--- Add any other context about the problem here. If applicable, add screenshots to help explain... --->
| Find your local number |<https://zoom.us/u/ad2WVnBzb8>||
35
33
36
34
## Meeting notices
35
+
37
36
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet).
38
37
39
38
-**All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://community.finos.org/docs/governance/code-of-conduct) and all other [FINOS policies](https://community.finos.org/docs/governance/#policies).
40
39
41
-
- FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
40
+
- FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact <[email protected]> with any questions.
42
41
43
42
- FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
44
43
45
44
- A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.
46
45
47
-
48
46
## Participation Requirements
49
47
50
48
**Note:** Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.
51
49
52
50
Please click the following links at the start of the meeting if you have not done so previously.
53
51
54
-
-[View the CSL](https://github.com/finos/FDC3/blob/main/LICENSE.md)
55
-
-[View the GOVERNANCE of the Project](https://github.com/finos/FDC3/blob/main/GOVERNANCE.md)
56
-
-[Click here to start a PR](https://github.com/finos/FDC3/edit/main/NOTICES.md).
57
-
- Edit the page to add your details.
58
-
- Hit the save button.
59
-
- Click "Create Pull Request".
60
-
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
61
-
-[Click here to send email to become a voting participant on the FDC3 Project](mailto:[email protected]?subject=Please%20enroll%20me%20as%20an%20FDC3%20Standards%20Participant&body=HI%2C%20my%20name%20is%20%3CFirstName%20LastName%3E%20and%20I'd%20like%20to%20formally%20participate%20to%20the%20FDC3%20standard%20process.%20I%20plan%20to%20contribute%20as%20%3Cindividual%7Con%20behalf%20of%20organizationName%3E%20and%20I%20have%20reviewed%20the%20policies%20described%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FGOVERNANCE.md%20and%20read%20the%20license%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FLICENSE%20.%20Thank%20you!")
52
+
-[View the CSL](https://github.com/finos/FDC3/blob/main/LICENSE.md)
53
+
-[View the GOVERNANCE of the Project](https://github.com/finos/FDC3/blob/main/GOVERNANCE.md)
54
+
-[Click here to start a PR](https://github.com/finos/FDC3/edit/main/NOTICES.md).
55
+
- Edit the page to add your details.
56
+
- Hit the save button.
57
+
- Click "Create Pull Request".
58
+
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
59
+
-[Click here to send email to become a voting participant on the FDC3 Project](mailto:[email protected]?subject=Please%20enroll%20me%20as%20an%20FDC3%20Standards%20Participant&body=HI%2C%20my%20name%20is%20%3CFirstName%20LastName%3E%20and%20I'd%20like%20to%20formally%20participate%20to%20the%20FDC3%20standard%20process.%20I%20plan%20to%20contribute%20as%20%3Cindividual%7Con%20behalf%20of%20organizationName%3E%20and%20I%20have%20reviewed%20the%20policies%20described%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FGOVERNANCE.md%20and%20read%20the%20license%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FLICENSE%20.%20Thank%20you!")
62
60
63
61
## Tracking Attendance
64
62
65
63
**Note:** Meeting participants are expected to _add a comment to this GitHub issue_ in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.
66
-
64
+
67
65
## Agenda
66
+
68
67
-[ ] Convene & roll call, review meeting notices (5mins)
69
68
-[ ] Review action items from previous meeting (5mins)
70
69
-[ ] Agenda item 1
@@ -73,14 +72,15 @@ Please click the following links at the start of the meeting if you have not don
| Find your local number |<https://zoom.us/u/ad2WVnBzb8>||
29
25
30
26
## Meeting notices
27
+
31
28
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet).
32
29
33
30
-**All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://community.finos.org/docs/governance/code-of-conduct) and all other [FINOS policies](https://community.finos.org/docs/governance/#policies).
34
31
35
-
- FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
32
+
- FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact <[email protected]> with any questions.
36
33
37
34
- FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
38
35
@@ -56,6 +53,7 @@ Please click the following links at the start of the meeting if you have not don
56
53
**Note:** Meeting participants are expected to _add a comment to this GitHub issue_ in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.
57
54
58
55
## Agenda
56
+
59
57
-[ ] Convene & roll call, review meeting notices (5mins)
60
58
-[ ] Review action items from previous meeting (5mins)
61
59
-[ ] Agenda item 1
@@ -64,9 +62,11 @@ Please click the following links at the start of the meeting if you have not don
| Find your local number |<https://zoom.us/u/ad2WVnBzb8>||
29
25
30
26
## Meeting notices
27
+
31
28
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://community.finos.org/docs/governance/meeting-procedures/). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet).
32
29
33
30
-**All participants** in FINOS project meetings are subject to the [LF Antitrust Policy](https://www.linuxfoundation.org/antitrust-policy/), the [FINOS Community Code of Conduct](https://community.finos.org/docs/governance/code-of-conduct) and all other [FINOS policies](https://community.finos.org/docs/governance/#policies).
- FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
38
35
39
-
40
-
## Participation Requirements
36
+
## Participation Requirements
41
37
42
38
**Note:** Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.
43
39
44
40
Please click the following links at the start of the meeting if you have not done so previously.
45
41
46
-
-[View the CSL](https://github.com/finos/FDC3/blob/main/LICENSE.md)
47
-
-[View the GOVERNANCE of the Project](https://github.com/finos/FDC3/blob/main/GOVERNANCE.md)
48
-
-[Click here to start a PR](https://github.com/finos/FDC3/edit/main/NOTICES.md).
49
-
- Edit the page to add your details.
50
-
- Hit the save button.
51
-
- Click "Create Pull Request".
52
-
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
53
-
-[Click here to send email to become a voting participant on the FDC3 Project](mailto:[email protected]?subject=Please%20enroll%20me%20as%20an%20FDC3%20Standards%20Participant&body=HI%2C%20my%20name%20is%20%3CFirstName%20LastName%3E%20and%20I'd%20like%20to%20formally%20participate%20to%20the%20FDC3%20standard%20process.%20I%20plan%20to%20contribute%20as%20%3Cindividual%7Con%20behalf%20of%20organizationName%3E%20and%20I%20have%20reviewed%20the%20policies%20described%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FGOVERNANCE.md%20and%20read%20the%20license%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FLICENSE%20.%20Thank%20you!")
42
+
-[View the CSL](https://github.com/finos/FDC3/blob/main/LICENSE.md)
43
+
-[View the GOVERNANCE of the Project](https://github.com/finos/FDC3/blob/main/GOVERNANCE.md)
44
+
-[Click here to start a PR](https://github.com/finos/FDC3/edit/main/NOTICES.md).
45
+
- Edit the page to add your details.
46
+
- Hit the save button.
47
+
- Click "Create Pull Request".
48
+
- Click "Accept" on the EasyCLA dialog in the PR's discussion section.
49
+
-[Click here to send email to become a voting participant on the FDC3 Project](mailto:[email protected]?subject=Please%20enroll%20me%20as%20an%20FDC3%20Standards%20Participant&body=HI%2C%20my%20name%20is%20%3CFirstName%20LastName%3E%20and%20I'd%20like%20to%20formally%20participate%20to%20the%20FDC3%20standard%20process.%20I%20plan%20to%20contribute%20as%20%3Cindividual%7Con%20behalf%20of%20organizationName%3E%20and%20I%20have%20reviewed%20the%20policies%20described%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FGOVERNANCE.md%20and%20read%20the%20license%20at%20https%3A%2F%2Fgithub.com%2Ffinos%2FFDC3%2Fblob%2Fmain%2FLICENSE%20.%20Thank%20you!")
54
50
55
-
## Tracking Attendance
51
+
## Tracking Attendance
56
52
57
53
**Note:** Meeting participants are expected to _add a comment to this GitHub issue_ in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.
58
54
59
55
## Agenda
56
+
60
57
-[ ] Convene & roll call, review meeting notices (5mins)
61
58
-[ ] Review action items from previous meeting (5mins)
0 commit comments