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.

Sign up for GitHub

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

Jump to bottom

edits needed on wiki pages #40

Open
10 of 16 tasks
clcarson opened this issue Jan 23, 2017 · 12 comments
Open
10 of 16 tasks

edits needed on wiki pages #40

clcarson opened this issue Jan 23, 2017 · 12 comments
Labels
todo

Comments

@clcarson
Copy link

clcarson commented Jan 23, 2017 •
edited by gunjanbaid
Loading

These are mostly for @choldgraf and @ryanlovett.

Home

What exactly is "the connectortools module"? It's mentioned, but I don't think it's explained.

  • Is it just the code in https://github.com/data-8/connector-instructors? Or the particular "connectortools" folder in there?
  • Should we make a list of what's available in "the connectortools module"? Would that go under Software Resources? Or somewhere else?

FAQ

  • Refers to tables demo, looks like it should be linked, and I don't know where that is.

Hardware Resources

I'm getting confused by the terms used throughout the wiki. Could we standardize and/or explain:

  • Does the cluster = our jupyterhub = datahub?
  • Are all of these identical to datahub.berkeley.edu (as a URL)?
  • Which of these will persist if we're using different resources from Data 8 (that's datahub this semester)?
  • Is "the datahub team" Ryan? Or Ryan plus others?
  • Under "Storing data and I/O" was there some talk about Box or Drive or something?

Software Resources

  • Under "Installing libraries and packages," can we list what libraries are installed for everyone?
  • Is this where we'd provide info about the datascience package?
  • Is there a place here to describe what's in the connectortools module?
  • I would sort have thought that GitHub and Interact would show up under Technical Infrastructure.

Technical Infrastructure

  • Will this eventually show up in the right-hand menu, once there's more to it?
  • What are the boundaries between Hardware Resources, Software Resources, and Technical Infrastructure?

Workflow

  • I don't know how this works, so can we ask a more experienced instructor to review it?

Overall

  • Wherever it refers to "the main course," replace by "Data 8" or "the Foundations course." I've done this everywhere I've caught it.
@choldgraf
Copy link
Collaborator

looking through this now

re: the tables demo, @SamLau95 or @ryanlovett do you know where this link should point to?

@choldgraf
Copy link
Collaborator

re: standardizing terms, I think this is a great idea but I don't want to do it all on my own, since I think we should have some kind of consensus. Maybe we can discuss this in a next meeting. I agree the terminology is confusing

@choldgraf
Copy link
Collaborator

re: software, yeah I think that's a good idea to explain the datascience package here. I didn't put that in yet because I don't really use it (we stopped using it in our connector more-or-less). At the least, we should have links to the relevant documentation for both it and connectortools, since they are described elsewhere already.

@choldgraf
Copy link
Collaborator

re: technical infrastructure, I imagined that it would not be in the sidebar, since it's probably more technical information than most people care about. Eventually it should detail the full hardware stack for jupyterhub etc, and would be more of a place we can point people to if they want to know about the guts of the setup. Is that OK?

@choldgraf
Copy link
Collaborator

re: nomenclature on main course, should we call it data 8 or foundations course? What do you prefer?

@choldgraf
Copy link
Collaborator

Also, let me know at what point the new person is going to get involved. I can keep maintaining these docs and helping etc, but we should really get them involved in these decision points once its appropriate IMO

@clcarson
Copy link
Author

I think it will be @gunjanbaid in the lead, but we haven't totally got it lined up.

I see why it's better to put in separate small issues than one big one. :)

@gunjanbaid
Copy link
Contributor

Hi @choldgraf! I'm onboarding this week so will be more involved in the coming days.

@choldgraf
Copy link
Collaborator

I've updated @clcarson 's comments so that they're checkboxes now instead of bullet points. @gunjanbaid can you take a look and we can make sure these suggestions are addressed and checked off?

@choldgraf choldgraf added the todo label Feb 1, 2017
@gunjanbaid
Copy link
Contributor

@choldgraf I updated the Tables demo link, pretty sure that's supposed to point to materials in Prof. Culler's repo.

@clcarson Are we sticking with the term "connector associates" or "connector assistants?" I see uses of both in the wiki so just want to make sure those are uniform.

@aivanoff
Copy link

aivanoff commented Feb 2, 2017 via email

@anthonysuen
Copy link
Collaborator

anthonysuen commented Feb 2, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
todo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@choldgraf @anthonysuen @clcarson @gunjanbaid @aivanoff