-
Notifications
You must be signed in to change notification settings - Fork 323
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Community meetup? #1550
Comments
I think this is actually a great general idea! And the proposal outlined above seems reasonable (and interesting!) to me. |
It would be great if we can also invite/involve people who are porting nbgrader to jlab. |
There's a few people working on nbgrader to jlab.... and we're one of them Note that nbgrader works just fine as a command-line tool - it's only the UI stuff that changes [the client-side has moved from javascript to typescript, and there's a whole suite of methods for interacting with the Interface] |
It would be great if those teams have cross-talks about the work being done so there is no duplication of work 😉. |
Maybe the Notebook weekly calls could be a good place to start these community meetings? They happen on Wednesdays at 08:00 Pacific Time: https://github.com/jupyter/notebook-team-compass#weekly-team-meetings cc @brichet @SylvainCorlay @fcollonval who might be interested |
Agree this would be a great thing to do! I probably couldn't join in the near future (I am currently on parental leave 😄) but it would be great to see something like this happen, and if there's a meetup later in the year perhaps I could join then! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi all.
Would anyone be interested in some sort of community event, to get a picture of all the different ways nbgrader is used and developed now? I have a feeling that a lot has been done in the last few years, but it has been local, without as much sharing as there could be.
I don't think it should be anything big, but this is my initial proposal:
I hope the outcomes would include seeing what each other are up to, co-work on making some of our developments reusable, and a plan for future community meetups and development.
I happened to chat with @gollington, and we could get some sort of Jupyter support for this.
The text was updated successfully, but these errors were encountered: