Removed files and typos
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 17
- Forks
- 18
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 1
Description
Hi @Girgias. Accidentally I found out that in the last months different files were removed from this repository. The commits I'm referring to are the following:
- https://github.com/php/doc-it/commit/0cda083487db80a9e1a64df29746307f1d1aed48;
- https://github.com/php/doc-it/commit/baabd2e9121da34063eda8c35929a28ef022f718;
- https://github.com/php/doc-it/commit/e93021df1d9437ba4633870563b03060db541ebc;
- https://github.com/php/doc-it/commit/2fee73231dfbe58e1a6897f2e1a58ac39a2ca7b8;
- https://github.com/php/doc-it/commit/411cc01052e712c7e0760540d3ad2e0e532f86b3;
- https://github.com/php/doc-it/commit/3535ca0a4dd5124242f157df857a043dd9e69521;
- https://github.com/php/doc-it/commit/10c2b6de0018d3ab4f3c26340f23de3d7d583445;
- https://github.com/php/doc-it/commit/aa707f51a10fad7d6c5cd2dbf5807845d1e17099.
Only the last listed commit contains removal of files that were not in the EN tree, all of the others are referring to files that are still available in the main doc-en repository.
I saw that some of these commits also include the following description: "No EN tag, and barely documented".
Now I'm curious to understand why most of the files that are removed from this repository are not touched in any other language repository (e.g. doc-fr). I think that here we are removing files that should be anyway translated and also wasting the effort (that could be counted in days/weeks) that was spent by previous contributors into translating big files (even in an old state) that could be still useful when somebody will want to update, re-using partial translations of them.
Unfortunately I also found out that some files were synced with typos or grammar errors (e.g. here and here) without passing through the PR approval.
Currently I'm the maintainer of this repository and for this reason I should be informed about such big changes and I suppose we have to agree together on these actions.
\cc @cmb69
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
Review the eight linked commits against the main doc-en repository and the corresponding doc-fr history, then inspect the two cited typo or grammar changes. Determine which removals and wording changes require maintainer agreement; done means documenting the findings and reaching an agreed action with the repository maintainer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100