You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -754,19 +754,22 @@ As for performance and scalability, pools can become bottlenecks, if all the poo
754
754
755
755
# How to contribute
756
756
757
-
**To add a new pattern** you need to do the following steps:
757
+
**To work on a new pattern** you need to do the following steps:
758
758
759
-
1. Fork the repository.
760
-
2. Implement the code changes in your fork. Remember to add sufficient comments documenting the implementation.
761
-
3. Create a simple class diagram from your example code.
762
-
4. Add description of the pattern in README.md and link to the class diagram.
763
-
5. Create a pull request.
759
+
1. If there is no issue for the new pattern yet, raise new issue. Comment on the issue that you are working on it so that others don't start work on the same thing.
760
+
2. Fork the repository.
761
+
3. Implement the code changes in your fork. Remember to add sufficient comments documenting the implementation. Reference the issue id e.g. #52 in your commit messages.
762
+
4. Create a simple class diagram from your example code.
763
+
5. Add description of the pattern in README.md and link to the class diagram.
764
+
6. Create a pull request.
764
765
765
-
**To work on one of the raised issues** you need to do the following steps:
766
+
**To work on one of the non-pattern issues** you need to do the following steps:
766
767
767
-
1. Fork the repository.
768
-
2. Implement the code changes in your fork. Remember to add sufficient comments documenting the implementation. Reference the issue id e.g. #52 in your commit messages.
769
-
3. Create a pull request.
768
+
1. Check that the issue has "help wanted" badge
769
+
2. Comment on the issue that you are working on it
770
+
3. Fork the repository.
771
+
4. Implement the code changes in your fork. Remember to add sufficient comments documenting the implementation. Reference the issue id e.g. #52 in your commit messages.
772
+
5. Create a pull request.
770
773
771
774
**For creating/editing UML diagrams** you need [ObjectAid UML Explorer for Eclipse](http://www.objectaid.com/home).
0 commit comments