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

RFC: move nim-plotly to more general org #19

Open
brentp opened this issue Jul 16, 2018 · 4 comments
Open

RFC: move nim-plotly to more general org #19

brentp opened this issue Jul 16, 2018 · 4 comments

Comments

@brentp
Copy link
Collaborator

brentp commented Jul 16, 2018

I use nim-plotly very often but I don't have the time/expertise to review great new features like those from @Vindaar or to keep up with changes in Nim that would allow new things in the library.

is there any interest in moving this repo to a more general org so I can more readily cede some control over it and hopefully get more contributors and users?

@Vindaar
Copy link
Member

Vindaar commented Jul 17, 2018

Thank you for the very kind words! :) Thank you again or getting this library started. For me it's one of the most useful Nim libraries out there.

I guess there's 3 things one can do:

  1. you can give other people access to this repo (maybe as an interim solution?)
  2. we can create a completely separate org and move it there
  3. we could contact the official https://github.com/plotly org and ask them kindly if they want to host this repo there? Although I'm not sure if they demand any specific licensing or something for their official bindings or if they think this is missing too much functionality etc. (Note: just checked and the Python bindings are under MIT license).

Maybe it would be a good idea to post this RFC in the Nim forum, Nim subreddit and / or Nim IRC channel to get the opinions of other people, who are more experienced with a situation like this.

@brentp
Copy link
Collaborator Author

brentp commented Jul 18, 2018

I have added you as a collaborator to the repo for now. We can maybe move elsewhere as it gains more traction. Or you can ask around if you prefer to move it along.

@Vindaar
Copy link
Member

Vindaar commented Jul 19, 2018

Thanks a lot! :)
Yes, I agree. We can wait and see how things develop first.

@ringabout
Copy link
Contributor

this could be closed

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

No branches or pull requests

3 participants