pymc-devs / pymc-devs/pymc-examples
Discuss: whether to add notebook update on when notebooks were transferred from pymc
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 325
- Avg merge
- 9d 15m
- Merged PRs (30d)
- 1
Description
Notebook title: generally, most
Notebook url: generally, most
Issue description
In updating the notebooks and the "Author" section, I have been adding this information:
## Authors
* Moved from pymc to pymc-examples repo in December 2020 ([pymc-examples#8](https://github.com/pymc-devs/pymc-examples/pull/8))
Some notebooks have been merged with this updates, and other(s) are under discussion.
See: https://github.com/pymc-devs/pymc-examples/pull/426/files#r984794260
@OriolAbril
I would not include this here
@reshamas:
Are you sure we should remove this? I've added it in for other notebooks. I think it helps folks know that to look for prior commits on the notebook, they can find some history in the other repo.
Note
Can we discuss and agree on a consistent rule?
Contributor guide
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 reviewing the notebook Author-section examples described in this issue, the transfer history in pymc-examples#8, and the discussion on pull request #426. Clarify whether transfer history belongs in notebooks and document the agreed consistent rule; done means the project has a decided policy and affected notebooks follow it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100