stanfordjournalism / stanfordjournalism/padj-code
Housekeeping
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This repo was created largely from the old Programming in Journalism course repo.
A bunch of pages need to be deleted, added (to complete the transition), or updated to generalize the content and take into account:
- the migration of basic Python instruction Data Journalism Notebooks (running on JupyterLite).
- The use of GitHub Classroom and Codespaces for various assignments
Tasks
- Update assignments to point to JupyterLite (and or mention that we're using GH Classrooms and Codespaces to manage the basics
- Add Senate Compromisers assignment from stanford-progj-23 and solution from zstumgoren/stanford-prog-22-solutions to padj-code and padj-code-solutions, respectively (note, don't seem to have committed solution to 2023 repo so use 2022)
- Generally review and transfer progj 23 assignments and solutions to padj-code and padj-code-solutions (for solutions, we should check 2022 and possibly earlier repos on my personal account)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the assignments/ directory with the linked stanford-progj-2023 assignments and checking the corresponding 2022 and earlier solution repositories. Review which assignments and solutions still need transfer or generalization for JupyterLite, GitHub Classroom, and Codespaces; done means the remaining relevant materials are present in padj-code and padj-code-solutions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, jupyter-notebook, python
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100