-
Notifications
You must be signed in to change notification settings - Fork 65
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
Jupyter Enterprise gateway #25
Conversation
|
||
### Demonstrate continued growth and development. | ||
|
||
See "Have an active developer community that offers a sustainable model for future development" and "Have an active user community" sections above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this section is more about -- how is the contributor base expanding beyond that of the initiators of the project? How has that been going? It's a different question than number of users and variance of users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the feedback @rgbkrk, I have pushed a new commit expanding on that section, please let me know if you think we should add any more details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's looking great, thanks for coming back to it.
@lresende Thanks for prepping this proposal. I added the steering council members as reviewers as a way of notifying them that this proposal exists. (FYI: I tried to add everyone but TIL that GitHub has a 15 reviewer limit and so it kicked @Ruv7 off when I added the last few folks. Take no offense, @Ruv7, your comments are of course welcome!) |
@parente, next time you could use https://blog.github.com/2017-06-28-requesting-reviews-from-repository-teams/, it should notify all the members AFAIK. |
Thanks for the current feedback so far. If there are any further questions/comments please let us know. Having said that, JupyterCon is a week away and, if possible, we would love to be able to hint/announce the outcome of this proposal at the conference. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the proposal, @lresende!
Just a thought while I'm here reviewing, it seems some refactoring is in order between |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's unique value in EKG. I agree with @blink1073
that figuring out how to consolidate / refactor with KG and jupyter-server is definitely worth doing as development continues.
One question (that really doesn't change my approval): do you wish to move nb2kg out of incubator at the same time?
@parente if we don't delay EG, it would be very helpful to get nb2kg moved as well. |
It was a pleasure to meet several of you guys in person at last week JupyterCon. I know you are all busy, and trying to catch up, but I would appreciate your review of this proposal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks all!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave my +1 during JupyterCon in person but re-add it here. I also gave Luciano ability to create a post on blog.jupyter.org to do an announce if necessary/wanted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congratulations on 1.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congrats on this work, excited to see move forward. We are already looking at using it ourselves in some deployments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just catching up with backlog after JupyterCon, sorry I couldn't get to it during the conference!
This is an excellent contribution and I'm very happy to see it graduate, thanks for the excellent work.
It looks like we have 8 "yes" and the rest abstaining so far. I don't think the governance docs state a number of votes required to incorporate a new project. Therefore, I'd like to propose a "last call" for votes and comments, and then equate silence with agreement as we have in the past, come Wednesday, September 12th. |
Good plan @parente |
Caught up in hurricane prep here and missed my self-imposed last-Wednesday deadline. I see no further comments. I'm going to merge this PR and then move jupyter-incubator/enterprise-gateway and jupyter-incubator/nb2kg into the jupyter org. Congrats to @lresende and team. |
Thanks everyone!
…On Sun, Sep 16, 2018 at 4:41 PM Peter Parente ***@***.***> wrote:
Merged #25 <#25>
into master.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABr0PZmG9Gc3S9X4lphTGztoamnczN7ks5ubuGfgaJpZM4V2BTx>
.
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger@calpoly.edu and ellisonbg@gmail.com
|
This PR proposes graduating Jupyter Enterprise Gateway project from jupyter-incubator. I would like to open this up for comments.
Adding our
mentors/sponsors
@rgbkrk and @parente which have been directly involved in the creation of this proposal.