-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path for supporting presently-third-party apis #4
Comments
Comment by MSevey Hi @xloem
As for your response/suggestion https:/NebulousLabs/skynet-webportal/pull/120#issuecomment-650109032 We do need to define a path/strategy for third party SDKs, we owe that to the community. Our default has always been to support the third party developers and help publish their work to the community but leave the repo in their control. I will leave this issue open for now and hopefully we can provide some communication to community soon. |
Issue by xloem
Monday Jul 06, 2020 at 13:07 GMT
Originally opened as NebulousLabs/skynet-docs#12
As someone who's put work into supporting skynet in another language, I was wondering if there was any available avenue to bring such work into the main supported repository. I could for example work to meet the guidelines of the other apis and look for a co-maintainer, but I'd like to know the avenue is available first.
I started a c++ api at https:/xloem/siaskynetpp but it will need cleanup and redesign to match the interface norms.
The text was updated successfully, but these errors were encountered: