~jan0sch/smederee

Showing details for patch 287ebf4b46073414bf3237267b1a0e1a39a927cc.
2024-02-02 (Fri), 4:55 PM - Jens Grassel - 287ebf4b46073414bf3237267b1a0e1a39a927cc

contributing: change wording regarding fork and branch in 3.4.7

Summary of changes
1 files modified with 1 lines added and 1 lines removed
  • CONTRIBUTING.md with 1 added and 1 removed lines
diff -rN -u old-smederee/CONTRIBUTING.md new-smederee/CONTRIBUTING.md
--- old-smederee/CONTRIBUTING.md	2025-01-13 01:32:25.698643072 +0000
+++ new-smederee/CONTRIBUTING.md	2025-01-13 01:32:25.698643072 +0000
@@ -58,7 +58,7 @@
 4. The user or Contributor SHOULD seek consensus on the accuracy of their observation, and the value of solving the problem.
 5. Users SHALL NOT log feature requests, ideas, suggestions, or any solutions to problems that are not explicitly documented and provable.
 6. Thus, the release history of the project SHALL be a list of meaningful issues logged and solved.
-7. To work on an issue, a Contributor SHALL fork the project repository and then work on their forked repository.
+7. To work on an issue, a Contributor SHALL branch from the project repository (a darcs branch can be considered a fork in git nomenclature) and then work on their own repository.
 8. To submit a patch, a Contributor SHALL send the patch to the project mailing list.
 9. A Contributor SHALL NOT commit changes directly to the project.
 10. A Contributor MAY directly send a patch without logging a separate issue.