Skip to content

Commit

Permalink
Merge pull request #1 from finos/master
Browse files Browse the repository at this point in the history
upstream sync
  • Loading branch information
agitana authored Jan 20, 2021
2 parents 9c2c7b5 + 7390f10 commit 3317d54
Show file tree
Hide file tree
Showing 220 changed files with 21,299 additions and 3,646 deletions.
30 changes: 30 additions & 0 deletions .editorconfig
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# http://editorconfig.org

# A special property that should be specified at the top of the file outside of
# any sections. Set to true to stop .editor config file search on current file
root = true

[*]
# Indentation style
# Possible values - tab, space
indent_style = space

# Indentation size in single-spaced characters
# Possible values - an integer, tab
indent_size = 2

# Line ending file format
# Possible values - lf, crlf, cr
end_of_line = lf

# File character encoding
# Possible values - latin1, utf-8, utf-16be, utf-16le
charset = utf-8

# Denotes whether to trim whitespace at the end of lines
# Possible values - true, false
trim_trailing_whitespace = true

# Denotes whether file should end with a newline
# Possible values - true, false
insert_final_newline = true
12 changes: 8 additions & 4 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,18 +11,22 @@ must be made with a
in place, and there are [additional legal requirements](https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/75530375/Legal+Requirements)
that must also be met.**

Commits and pull requests to FINOS repositories such as FDC3 will only be accepted from those contributors with an active, executed Individual Contributor License Agreement (ICLA) with FINOS OR who are covered under an existing and active Corporate Contribution License Agreement (CCLA) executed with FINOS. Commits from individuals not covered under an ICLA or CCLA will be flagged and blocked by the FINOS ["CLA Bot" tool](https://github.com/finos/cla-bot). Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.

As a result, PRs submitted to the FDC3 project cannot be accepted until you have a CLA in place with the Foundation.

Need an ICLA? Unsure if you are covered under an existing CCLA? Email [help@finos.org](mailto:help@finos.org?subject=CLA)

# Contributing Issues

## Prerequisites

* [ ] Have you [searched for duplicates](https://github.com/FDC3/FDC3/issues?utf8=%E2%9C%93&q=)? A simple search for exception error messages or a summary of the unexpected behaviour should suffice.
* [ ] Have you [searched for duplicates](https://github.com/finos/FDC3/issues?utf8=%E2%9C%93&q=)? A simple search for exception error messages or a summary of the unexpected behaviour should suffice.
* [ ] Are you running the latest version?
* [ ] Are you sure this is a bug or missing capability?

## Raising an Issue
* Create your issue [here](https://github.com/FDC3/FDC3/issues/new).
* Create your issue [here](https://github.com/finos/FDC3/issues/new).
* New issues contain two templates in the description: bug report and enhancement request. Please pick the most appropriate for your issue, **then delete the other**.
* Please also tag the new issue with either "Bug" or "Enhancement".
* Please use [Markdown formatting](https://help.github.com/categories/writing-on-github/)
Expand All @@ -34,12 +38,12 @@ To make review of PRs easier, please:

* Please make sure your PRs will merge cleanly - PRs that don't are unlikely to be accepted.
* For code contributions, follow the existing code layout.
* For documentation contributions, follow the general structure, language, and tone of the [existing docs](https://github.com/FDC3/FDC3/wiki).
* For documentation contributions, follow the general structure, language, and tone of the [existing docs](https://github.com/finos/FDC3/wiki).
* Keep commits small and cohesive - if you have multiple contributions, please submit them as independent commits (and ideally as independent PRs too).
* Reference issue #s if your PR has anything to do with an issue (even if it doesn't address it).
* Minimise non-functional changes (e.g. whitespace shenanigans).
* Ensure all new files include a header comment block containing the [Apache License v2.0 and your copyright information](http://www.apache.org/licenses/LICENSE-2.0#apply).
* If necessary (e.g. due to 3rd party dependency licensing requirements), update the [NOTICE file](https://github.com/FDC3/FDC3/blob/master/NOTICE) with any new attribution or other notices
* If necessary (e.g. due to 3rd party dependency licensing requirements), update the [NOTICE file](https://github.com/finos/FDC3/blob/master/NOTICE) with any new attribution or other notices


## Commit and PR Messages
Expand Down
27 changes: 27 additions & 0 deletions .github/ISSUE_TEMPLATE/---enhancement-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
name: "\U0001F680 Enhancement Request"
about: Propose an addition or change to the FDC3 standard!
title: ''
labels: enhancement
assignees: ''

---

## Enhancement Request

### Use Case:
...please specify at least one use case that this enhancement would support

... a use case should not be a solution, but a description of a problem from an end user point of view.

For example:
> 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.
### Workflow Description
...clearly and concisely describe the target workflow for the prosed enhancement.

### Workflow Examples
... provide one or more concrete examples of the proposed workflow.

### Additional Information
... please add any other information that can provide additional detail for this enhancement request
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/---minor-issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: "\U0001F41B Minor Issue"
about: "If something isn't as expected \U0001F914."
title: ''
labels: bug
assignees: ''

---

## Minor Issue
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.

### Area of Issue
[ ] App Directory
[ ] API
[ ] Context Data
[ ] Intents
[ ] Use Cases
[ ] Other

### Issue Description:
...please provide a detailed description of the issue

### Additional Context:
...add any other context about the problem here. If applicable, add screenshots to help explain...
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/---question.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: "\U0001F917 Question"
about: "If you have a questions about FDC3. \U0001F4AC"
title: ''
labels: ''
assignees: ''

---

## Question

### Question Area
[ ] App Directory
[ ] API
[ ] Context Data
[ ] Intents
[ ] Use Cases
[ ] Other

### Question
24 changes: 0 additions & 24 deletions .github/ISSUE_TEMPLATE/Bug_report.md

This file was deleted.

17 changes: 0 additions & 17 deletions .github/ISSUE_TEMPLATE/Feature_request.md

This file was deleted.

7 changes: 5 additions & 2 deletions .github/ISSUE_TEMPLATE/Support_question.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
---
name: 🤗 Support Question
about: If you have a question about configuration, usage, etc. 💬
name: "\U0001F917 Support Question"
about: "If you have a question about configuration, usage, etc. \U0001F4AC"
title: ''
labels: ''
assignees: ''

---

Expand Down
56 changes: 56 additions & 0 deletions .github/ISSUE_TEMPLATE/general-meeting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
name: General Meeting
about: minutes for an FDC3 General Meeting
title: ''
labels: General meeting
assignees: ''

---

---
name: 🤝FDC3 General Meeting Minutes
about: Track FDC3 General meeting agenda and attendance
---

## Date
DD MMM yyyy - 10am EST

## Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...

## Meeting notices
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md#run-the-meeting). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/).

- **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://github.com/finos/community/blob/master/governance/Code-of-Conduct.md) and all other [FINOS policies](https://github.com/finos/community/tree/master/governance#policies).

- 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 legal@finos.org with any questions.

- 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.

## Agenda
- [ ] Convene & roll call (5mins)
- [ ] Display [FINOS Antitrust Policy summary slide](https://github.com/finos/community/blob/master/governance/Compliance-Slides/Antitrust-Compliance-Slide.pdf)
- [ ] Review Meeting Notices (see above)
- [ ] Approve past meeting minutes
- [ ] Review action items from previous meetings (5mins)
- [ ] Agenda item 1
- [ ] Agenda item 2
- [ ] AOB & Adjourn (10mins)

## Decisions Made
- [ ] ...

## Action Items
- [ ] ...

### WebEx info
- [Meeting Link](https://finos.webex.com/finos/j.php?MTID=m3015a7e4a511656ceafebda5eadcbe6d)
- Meeting number: 403 028 328

*More ways to join*
- Join by video system: dial 173.243.2.68 and enter your meeting number
- Join by phone
- +1-415-655-0003 US Toll
- +44-20319-88141 UK Toll
- Access code: 403 028 328
57 changes: 57 additions & 0 deletions .github/ISSUE_TEMPLATE/pmc-meeting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
name: PMC Meeting
about: minutes for an FDC3 Product Management Committee meeting
title: PMC Meeting
labels: PMC Meeting, meeting
assignees: ''

---

---
name: 🤝FDC3 PMC Meeting Minutes
about: Track PMC meeting agenda and attendance
---

## Date
Friday DD MMM yyyy - 9am EST

## Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...

## Meeting notices
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md#run-the-meeting). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/).

- **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://github.com/finos/community/blob/master/governance/Code-of-Conduct.md) and all other [FINOS policies](https://github.com/finos/community/tree/master/governance#policies).

- 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 legal@finos.org with any questions.

- 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.

## Agenda
- [ ] Convene & roll call (5mins)
- [ ] Display [FINOS Antitrust Policy summary slide](https://github.com/finos/community/blob/master/governance/Compliance-Slides/Antitrust-Compliance-Slide.pdf)
- [ ] Review Meeting Notices (see above)
- [ ] Approve past meeting minutes
- [ ] Review action items from previous meetings (5mins)
- [ ] Agenda item 1
- [ ] Agenda item 2
- [ ] ...
- [ ] AOB & Adjourn (10mins)

## Decisions Made
- [ ] ...


## Action Items
- [ ] ...


### WebEx info
- [Meeting Link](https://finos.webex.com/finos/j.php?MTID=mb24e0868b724abcfa92221ca14207e14)
Description:FDC3 PMC Meeting
Meeting number: 663 444 364
Dial in:
+1.415.655.0003 USA Toll
+44-20319-88141 UK Toll
Access code: 663 444 364
60 changes: 60 additions & 0 deletions .github/ISSUE_TEMPLATE/standard-wg-meeting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
---
name: Standard WG Meeting
about: minutes for an FDC3 Standard Working Group Meeting
title: ''
labels: Standard WG Meeting, meeting
assignees: ''

---

---
name: 🤝FDC3 Standard WG Meeting Minutes
about: Track Standard Working Group meeting agenda and attendance
---

## Date
Thursday DD MMM yyyy - 10am EST

## Untracked attendees
- Fullname, Affiliation, (optional) GitHub username
- ...
## Meeting notices
- FINOS **Project leads** are responsible for observing the FINOS guidelines for [running project meetings](https://github.com/finos/community/blob/master/governance/Meeting-Procedures.md#run-the-meeting). Project maintainers can find additional resources in the [FINOS Maintainers Cheatsheet](https://odp.finos.org/docs/finos-maintainers-cheatsheet/).

- **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://github.com/finos/community/blob/master/governance/Code-of-Conduct.md) and all other [FINOS policies](https://github.com/finos/community/tree/master/governance#policies).

- 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 legal@finos.org with any questions.

- 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.

## Agenda
- [ ] Convene & roll call (5mins)
- [ ] Display [FINOS Antitrust Policy summary slide](https://github.com/finos/community/blob/master/governance/Compliance-Slides/Antitrust-Compliance-Slide.pdf)
- [ ] Review Meeting Notices (see above)
- [ ] Approve past meeting minutes
- [ ] Review action items from previous meetings (5mins)
- [ ] Agenda item 1
- [ ] Agenda item 2
- [ ] ...
- [ ] AOB & Adjourn (10mins)

## Decisions Made
- [ ] ...


## Action Items
- [ ] ...


### WebEx info
- [Meeting Link](https://finos.webex.com/finos/j.php?MTID=ma4b1de1b9f691d89e4b2ff380ec9687c)
Meeting number: 665 568 411

*More ways to join*
- Join by video system:
- Dial 665568411@finos.webex.com
- You can also dial 173.243.2.68 and enter your meeting number
- Join by phone
- +1-415-655-0003 US Toll
- +44-20319-88141 UK Toll
- Access code: 665 568 411
Loading

0 comments on commit 3317d54

Please sign in to comment.