Repository navigation
Supported external contribution workflow under the current source-available licence #1291
Replies: 1 comment
|
Good afternoon. Most commercial users make contact directly and privately and supply code that is often incorporated later. |
Uh oh!
There was an error while loading. Please reload this page.
I am studying fixed-income curve construction and would like to understand
the supported route for external correctness contributions before preparing
a patch.
The current README and
LICENCEexplicitly describe rateslib assource-available, not open source. The default personal/educational licence
does not grant modification or redistribution rights. I do not want to assume
that a public GitHub repository grants those permissions.
Could you clarify:
licence, and if so, what permission or contributor agreement should be
obtained before modifying or publishing a fork?
step a minimal public bug report/reproducer, or contacting you privately?
ownership/licensing of accepted patches that prospective contributors
should follow?
This is a contribution-process question, not a request to change your
commercial licensing or grant commercial deployment rights. No source patch
or redistributed derivative is attached. A short contribution-policy link
would help avoid accidental licence misunderstandings for future contributors.
All reactions