Clarify contribution terms for an external FXMacroData integration page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
Start with the catalogue contribution instructions and the separate Haystack core CLA referenced in the issue. Confirm which licence and contributor agreement apply to integrations/fxmacrodata.md; the issue is resolved when maintainers document those terms so the proposed page can be contributed.
Written by the indexing model from the issue text.
Description
I maintain FXMacroData and have prepared an Apache-2.0 Haystack integration. It provides native pipeline components, Documents and agent tools, with public USD examples that need no API key.
Before contributing an original integrations/fxmacrodata.md page, could you clarify which licence governs contributions to this catalogue and whether its contributors must complete a CLA? I found the catalogue contribution instructions and the separate Haystack core CLA, but no licence or contributor agreement for this repository.
The proposed catalogue page would link to the externally maintained package and document installation and a runnable Pipeline example.
- Dominant language
- Shell
- Stars
- 115
- Forks
- 232
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from deepset-ai/haystack-integrations
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
deepset-ai/haystack-integrations#638 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
deepset-ai/haystack-integrations#541 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
deepset-ai/haystack-integrations#429 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
deepset-ai/haystack-integrations#401 ·
Maintainers usually reply within 1 day
-
Align and merge integration typesMay be free again @bilgeyucel claimed this 230 days ago, and no pull request is open. Open
deepset-ai/haystack-integrations#399 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in deepset-ai/haystack-integrations
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/appmod-blueprints#972 ·
Maintainers usually reply within 1 day
-
[Bug]: remote-ls --updates reports up-to-date OCI refs because it ignores deployed Alt-idPossibly taken @Joao-kouznetz claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days