.NET Standard 2.0 declarations to implement concrete FDC3 compatible .NET desktop agents and usage of intents/context.
If you are an existing individual or corporate user of the FDC3 standard, we would love to hear from you: just email fdc3@finos.org with details about how you are using the standard.
- If you'd like to be listed as on the community page, please fill out the Usage Form.
- If listing your logo publicly requires legal evaluation, you can reach out privately to the FDC3 Maintainers.
- FDC3 activity primarily happens in this FDC3 GitHub repository. Watch the repository in order to be notified of new Pull Requests and issues.
- The fastest and more interactive way to connect and ask questions to the FDC3 community is to join the #fdc3 channel on the FINOS slack.
- If you'd like to receive official updates, and/or you don't have access to Slack, please send an email to fdc3@finos.org. You can join the list by sending an email to fdc3+subscribe@finos.org.
- To contact the FDC3 maintainers, send an email to fdc3-maintainers@finos.org.
- Finally, another great way to interact with the community, is to attend the monthly FDC3 Standard Working Group Meeting and/or the quarterly FDC3 General Meeting.
- Email help@finos.org to be added to the meeting invite directly, or find the meeting in the FINOS Community Calendar.
- Email fdc3@finos.org if you need help getting started in the FDC3 Community.
- If you encounter technical difficulties accessing repositories, joining Slack, mailing lists or meetings, please email help@finos.org.
For any questions, bugs or feature requests please open an issue.
To submit a contribution:
- Fork it (https://github.com/finos/fdc3-dotnet/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Read our contribution guidelines and Community Code of Conduct
- Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a new Pull Request
NOTE: Commits and pull requests to FINOS repositories 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 Clabot tool (or EasyCLA). Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.
Need an ICLA? Unsure if you are covered under an existing CCLA? Email help@finos.org
Copyright 2023 Morgan Stanley
Distributed under the Apache License, Version 2.0.
SPDX-License-Identifier: Apache-2.0