Git Product home page Git Product logo

cc20's Introduction

cc20's People

Contributors

andycho97 avatar aojiu avatar cpaynerogers avatar dncamp avatar erdong021 avatar eric0871 avatar graceliudata avatar gulingxuan98 avatar ingrammyles8 avatar ivygdy avatar jialu-stellar-xia avatar jingyouu avatar jinyanlyu avatar joseph-zhuo avatar jtr13 avatar lubin-liu avatar mcryan6 avatar mlrookie35 avatar sallytt22 avatar scaisijie avatar superpowergirl avatar tonyli97 avatar tracy3057 avatar xiaoyu-su-20 avatar xuanhaowu avatar ybliu9 avatar yifeizhangcs avatar yilan007 avatar yq2305 avatar zujunpeng avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

cc20's Issues

Please add me as a collaborator

Hello Professor Robbins,

I am one of the bookdown PR merge helpers, can I be add as a collaborator?

Thanks!

Lu Bin Liu (ll3450)

avoiding merge conflicts

Let's try to come up with a way to reduce the merge conflicts in _bookdown.yml -- I know it's a pain to fix them. One possibility is to add the new chapter filename to _bookdown.yml after the pull request is merged. Not super elegant but it's not a problem to have an .Rmd file that's not included in _bookdown.yml (the other way around is a problem.) Open to suggestions.

Consider incorporating live tutorials and translations into their respective chapters

While organizing the chapters for the book, it's easy for me to empathize with reading the book as a native English speaker, and semantically placing the live tutorials and the translations at the end. I think this organization is useful for merging all of the initial pull requests. It was done in the cc19 book, too. However, I'd like us to consider collapsing either the translations or the live tutorials sections, or both, into the preceding sections, so the book isn't biased towards tutorials written in English and provided as an Rmd file. I do know this may be at odds with my cheat sheet issue :)

'speed-up-in-r-programming.Rmd' writes files to root directory

This chapter is writing the following files to the root directory:

n100distgaussian.txt    n200distt5.txt          n400distt1.txt
n100distt1.txt          n300distgaussian.txt    n400distt5.txt
n100distt5.txt          n300distt1.txt          n500distgaussian.txt
n200distgaussian.txt    n300distt5.txt          n500distt1.txt
n200distt1.txt          n400distgaussian.txt    n500distt5.txt

If they are needed they should be written to the resources file but ideally the chapter should not have any processes that write files. Please take a look and submit a new pull request to fix. @graceliudata

Consider a separate "cheatsheet" section in the `cc20` book

I have a pull request open that updates the current chapter labels and adds an appendix for chapter organization. The book, in that pull request, consists of nine parts: introduction, data processing, data visualization, results reporting, complete analyses, other topics, live tutorials, translations, and appendices. My changes added and reorganized the chapters a bit and although they may have been opinionated, I'd like to discuss whether it makes sense for cheat sheets to have their own section in the book. It at least makes sense that any cheat sheet that links to a PDF (maybe they all do) to have its own chapter, and for that chapter to get added right before the appendices, so the "flow" of the book isn't interrupted by PDF opening.

help wanted: rendering book locally

If anyone would like to take over rendering the book locally and pushing to GitHub, let me know! Warning: you'll have to install a lot of packages but otherwise it's easier and I'm happy to explain what to do.

update branch name instructions

The branch name should be descriptive but it doesn't need to be exactly the same as the .Rmd filename. This should be fixed both in the instructions to contributions and the tutorial for pull request mergers.

.Rmd files missing from _bookdown.yml

@andycho97 some or all of the filenames were not added to the _bookdown.yml when you merged the pull requests. Can you edit the current version of the _bookdown.yml adding in those files in the proper place? You can do this directly on GitHub. Thanks!!

Collaborator Request

Hello Professor Robbins,

I am one of the PR merge helpers, could you add me as a collaborator, please.

Zhuo Zhuo(zz2688)

Thank you to all the collaborators! If you'd like to be removed from the repo lmk.

Hi All,
Thank you all for your hard work. I'm doing a bunch of things on the repo which may be causing you to get a lot of unwanted email messages. If you'd like I can remove you from the repo--just comment on this issue to that effect. (Or you may be able to turn off notifications but not sure it's possible to control notifications on a repo by repo basis.)
best,
Joyce

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.