add start of language bindings #234
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We can host external tutorials for bindings that are well-tested, etc. I will include my proposal for a plan in the pull request associated with this PR Signed-off-by: vsoch <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the start of a (likely multiple PR/ multiple repository) to refactor / create a set of language bindings tutorials/snippets. Importantly, each is a separate repository that (akin to what the page says) includes:
The high level goal is that a contributor developer could fork/clone one of these repos and jump in to developing their project that uses flux without having to untangle or otherwise figure out the logic from our main repos. These repos are separate, but importantly they are regularly tested so they don't get out of date. This (I hope) achieves a balance of allowing separation without burdening the main flux core devs with extra work.
For the main plan, since we already have some Python here, this is my proposal. Under tutorials I think we should remove the top group that we currently have for the "Python API" and move these examples into their own repository. Then, we can link (to start) each of the external repos for C/C++, Python, and Go (and TBA others) like this:
I put it first there because that's where Python currently is, it doesn't need to be.
Let me know your thoughts on this! If you like the idea, my proposal is to review/merge here, and then I can start refactoring our Python examples here to be in a separate repository, and (in the meantime) if someone else wants to make a simple repository with a src folder and Makefile for C/C++, I can add the developer environment, docs, and automation around that.