practical-tutorials / practical-tutorials/project-based-learning

Proposal for better gatekeeping: stick to masterpiece materials

Open
#143 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement question
Dominant language
Python
Stars
284k
Forks
36.3k
PR merge metrics
No merged PRs in 30d

Description

Description

Can we please refrain from adding things if content isn’t unique?

Why

I’ve been following the changes happening lately and I’m concerned making changes to this repo is turning into a popularity contest. Below are a few reasons why.

Possible Implementations

I propose contributors ask themselves these questions before opening a PR:

  • Does the writing follow a unique pedagogy?
  • Does the writing put you outside your comfort zone by taking an unfamiliar and scary topic and making you happy, instead of overwhelmed?
  • Is the writing from a portal, aggregator or a commercial site (constains ads, etc)? That should be a yellow flag as these places favor breath over depth.

A few other random points:

  • I would prefer that topics endure test of time and that they stay away from frameworks. Thoughts here?
  • If we link to an aggregator site, we defeat the point of being curators here.
Is this something you're interested in working on?
  • YES
  • NO

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named, so start by reading the issue and its comment thread to determine whether maintainers want a concrete curation policy. Done would require an agreed scope, decision criteria for tutorial additions, and a documented place for contributors to apply them.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.