Archive?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Confirm with maintainers whether the repository should be archived, since the issue is phrased as a question. If approved, update the README to direct new content to https://blog.scientific-python.org/ and archive the repository; done means both the note and repository status reflect that decision.
Written by the indexing model from the issue text.
Description
Since the content was moved to https://blog.scientific-python.org/, should this repo be archived, w/ a note on the readme to submit new content there?
- Dominant language
- Jupyter Notebook
- Stars
- 39
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
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.
More from matplotlib/matplotblog
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
matplotlib/matplotblog#67 · 1 comment ·
All issues in matplotlib/matplotblog
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
A11y ♿️
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
documentation improve or update documentation priority/low triage
Difficulty 2/5 Half a day Newbie friendliness 86/100
warpdotdev/docs#782 · 1 comment ·