Skip to content
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

🗄🔧 Nim #60

Closed
1 of 5 tasks
battila7 opened this issue Apr 26, 2017 · 9 comments
Closed
1 of 5 tasks

🗄🔧 Nim #60

battila7 opened this issue Apr 26, 2017 · 9 comments
Labels

Comments

@battila7
Copy link

battila7 commented Apr 26, 2017

Current Status

Todo:

  • 🏁 Fork the starter repo & post the link in this issue
  • 🔨 Implement all of Conduit's functionality per the spec & API
  • 🎨 Create logo for repo & update issue status (@EricSimons)
  • 👀 Move repo to main org & Peer review final codebase by admins/community (RFC)
  • 🎉 Tag v1 release and officially list it on the README!

If I have the time on the weekend, I'll start the implementation in Nim and then update this issue accordingly.
Not decided yet, whether to use Jester or Rosencrantz.

@EricSimons EricSimons changed the title Nim 🗄🔧 Nim Apr 26, 2017
@EricSimons
Copy link
Member

@battila7 awesome!! I'm looking forward to seeing this come together :) Fork the starter repo and post the link in here whenever you have a chance & I'll update the issue status 👍

@EricSimons
Copy link
Member

Created a logo that you can use for the readme in your repo:

nim

@battila7
Copy link
Author

@EricSimons Just forked the repo: Nim RealWorld

@battila7
Copy link
Author

battila7 commented May 1, 2017

Concluding the experiences of the past two days:

Real World Nim Adventures

@EricSimons
Copy link
Member

@battila7 I loved the medium post! Sad to hear you won't have enough time to finish it off :( Should we invite devs to come in & help?

PS - would love to interview you on Thinkster sometime about your experience building the Nim implementation :)

@battila7
Copy link
Author

battila7 commented May 1, 2017

@EricSimons I will definitely continue the development, but not be able to dedicate a whole weekend to this project. It'll slow down a little bit but will be finished :)

Sounds like a great opportunity and honor, thanks! We should talk about the details after finishing the implementation, what do you think?

@EricSimons
Copy link
Member

@battila7 sounds good to me! 👍

@dom96
Copy link

dom96 commented Aug 10, 2017

If you need any assistance feel free to ping me :D

@geromegrignon
Copy link
Contributor

Hello we are currently moving all work in progress to Github Discussions.
I'll close this issue by now, you can find instruction to open a discussion there : #633

Thanks for your contribution !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants