-
Notifications
You must be signed in to change notification settings - Fork 14
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
Generalizing data 8 references #32
Comments
I think something like this would be a good idea - I think the link to Data 8 is helpful just for people who are coming explicitly with that in mind, but I agree that the stack as a whole is much more than data 8. Do you think it'd require refactoring the name of the book itself? |
Cool! I don't think it'd require changing the name but it might be confusing otherwise. "Data 8" is known outside of Berkeley and I think for a certain audience, "Zero to Data 8" has an obvious meaning. For others it might not be as meaningful, especially if the Data 8 specific mentions are abstracted out. But that decision could probably be left until the end should anything come out of this issue. |
Would it be helpful if I started by itemizing all of the Data 8 specific mentions (usually URLs) of the book? |
Another thought is if we pulled out the pieces of this book that are data-8-agnostic, and had a different guide that we called out to (like "zero to jupyterhub for education"). Your suggestion seems like a reasonable place to start just to see what kind of changes we're talking about here |
Okay, tagging my opinion of generalizable items as z2jh4e.
|
So maybe deploy+tech-teaching forms z2jh4e with a new intro? If so I can try that in a fork which rebrands/generalizes Data 8 as "JupyterHub For Education" to see how it reads. |
I'm curious what other folks at the DSEP would think about this. Do you think that they'd be hesitant to rebrand anything? And if so, maybe Z2JH4E would be more like a separate resource that would live in parallel, and over time we could start replacing information here with links to there? |
Hmm, not sure about the others in dsep. For now I think I'll make a berkeley-dsep-infra/zero-to-jh4edu fork with just the generalized deploy and tech bits. This will help me help the non-data8 instructors and gsis. I may ask you questions about the book deployment process. :) |
That all sounds good to me, I don't see any problem with keeping two parallel versions. Does that work for you in the short term? |
Yep, should be fine. |
Lemme know when you have another site up, and I can link to it from Z2D8! |
The datahub repo is home to many deployments now, each for different courses. The processes outline in this textbook are still highly relevant for those other courses. For example if I want to point the Data 100 instructors and GSIs at the docs for how to do things like update the single user image, I'd send them a link to this textbook with a note about replacing all data 8 related links (hub, docker image manifest, syllabus, course website, etc.) with their data100 equivalents.
That's simple enough, but I wonder if this textbook should be refactored so that it is less data8-specific -- basically following the "keep it generalized" mantra of z2jh. I just wanted to get your thoughts on this. If there's some interest maybe we can spitball here?
The text was updated successfully, but these errors were encountered: