vogt4nick / datascience-wiki Goto Github PK

See something missing? Visit our GitHub Repo and make a pull request.

All these should point to issues instead of the repo.

When? Probably Mondays. Maybe another day? Mods can decide.

The "Curated Answers and Threads" takes up a lot of space on the table of contents. Format it bold instead of formatting it as a subheading.

#### Curated Answers and Threads

becomes

__Curated Answers and Threads__

The current beginner.md is intimidating. Let's make it more welcoming.

• Format content
• Prioritize content
  • Breaking into sections would be a big help.
• Annotate content if useful

It's just easier to verify that OP is getting the message.

Consider adding a removal reason too if that's possible.

It's intimidating as it is. Organize by topic and possible reading level.

The weekly thread currently refreshes every Sunday at 4:00 PM UTC.

When users comment on the sticky between Saturday 4:00 PM - Sunday 4:00 PM, tell them that the weekly thread will renew soon, and to consider resubmitting their comment to the new thread for higher visibility.

On this thread.

• Everybody Lies
• Uncharted
• Dataclysm
• Freakonomics
• Super Freakonomics
• Weapons of Math Destruction
• Signal and the Noise
• How Not to Be Wrong
• Data Science for Business

More popsci titles at elitedatascience

What are the biggest questions to answer? How will it be distinct from the FAQ and Resources pages?

Here was a good thread

• towardsdatascience.com
• medium.com

Coach authors on how to improve their posts in the comment.

I'm not even sure how to do this yet, but the feeling is we should make it available. /r/csshelp put together a wiki page for this exact thing.

Figure out how to do it, and what it will look like, then we can flag it for enhancement.

The wiki on /r/AutoModerator has a good list of boilerplate. Things like troll control, self posts without text, etc. Figure out which ones we want to use and run them by the other mods to keep things open.

https://www.reddit.com/r/datascience/comments/au9cn9/weekly_entering_transitioning_thread_24_feb_2019/eh9orrt/

Threads without context are intimidating. Let's put them in context in the other pages.

It's best to keep them coordinated. A lot of text goes into it.

There are some sources that are interesting, but haven't yet been approved (curated) for the wiki. We need a way to talk about these.

Some options come to mind:

• Make an uncontrolled branch called future so folks can make and approve PRs for their own suggestions?

  • Pro: I don't have to monitor anything
  • Con: A bad guy might delete other resources. But that's what version control is for, so any malicious actions can be rolled back.

• Allow issues where people raise possible contributions and tag them future

  • Pro: We can discuss additions in a forum conducive to discussions.
  • Con: The issues will get cluttered if people don't use the future label. I don't anticipate many contributors, so this is probably a minor nuisance.

• Separate community contributions from the repo entirely and keep them on /r/datascience

  • Pro: Moves all responsibility and problems away from the repo.
  • Con: Community curated content needs to be a guided discussion.

PRs should be pulled into dev, not master.

Flairs can help to foster a sense of belonging in the community. Should we expand our flair selection? Flairs like

• Casually Interested
• Learning Data Science
• Searching for First DS Job

Notes:

• Flairs like PhD | Data Scientist | Gov should be mod approved because they carry some weight in a data science subreddit.
• The final flairs should be more concise than what I listed.

The purpose of this page is to promote freedom of information and minimizing financial barriers to becoming a data scientist. Content will center around two goals:

1. to direct aspiring data scientists to the curated resources, and
2. to set proper expectations on the path to becoming a data scientist.

This page would rub elbows with the FAQ and Resources. It will certainly change the scope of the FAQ, but the Resources page should not change much.

Labeling future until we can figure out what this will look like in action. Some requirements:

• Action applies to authors with less than 50 karma
• Automod comments on the target post
  • to direct the author to the weekly thread with a valid url
  • to share that their post requires approval from the moderators
  • to tell them to contact the mods if they believe their post is not related to getting started, transitioning, etc.

Is there a way to require approval for posts under 50 karma without removing or deleting the post?

example

This probably means catching "best", "podcast"; or catching "beginner" and redirecting those to the wiki or weekly thread.

Add Mastering the DS Interview Loop to the Searching section of the FAQ

https://www.reddit.com/r/datascience/comments/au2u0h/crowdsourcing_the_top_skillset_to_become_a_decent/