cran-task-views / cran-task-views/WebTechnologies
systematic checks
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 178
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Hi @wibeasley !
I had a hard week and I'm checking the task view now, please feel free to check this in forthcoming days.
So far, my method to keep the list of pkgs in good shape is:
- Use ctv to inspect the file
- Check for any package removed from CRAN
- If the package is on GH, link to it, but 1st email the author and ask about the pkg continuity
- If the GH repo is maintained, push changes pointing to a GH link
- If the GH repo is abandoned (+1 yr without changes or follow ups on issues), then I remove the pkg from the list
- 1-5 go to a log where I manually annotate the changes and the reason why I made the change
Do you have any other ideas in mind? This is a process that I don't want to automate, the communication with authors is key.
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 with the ctv inspection step and the current package list described in the issue. The proposed process is still a discussion: no file, test, concrete change, or definition of done is specified, so clarify the intended maintenance workflow before beginning work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100