Lab 1 code

CODE 1: Koha

License:GNU

This site accepts patches from contributors through git hub at the link http://git.koha-community.org/gitweb/

the process to submit patches is to create the patch write a commit message. Then send it to the QA manager who will check the code and then send it to the release manager who then decides when and where to release the patch.

This site is very hands off you basically decided what code you want to add in a patch make it and submit it the only people who review your code are QA and Release managers. the time it takes is how long it takes them to get to it. as shown in the patches surrounding release tools used in koha found at http://git.koha-community.org/gitweb/?p=release-tools.git;a=summary
References

• https://en.wikipedia.org/wiki/Koha_(software) 
• https://wiki.koha-community.org/wiki/Version_Control_Using_Git
• http://git.koha-community.org/gitweb/?p=release-tools.git;a=summary
• http://git.koha-community.org/gitweb/?p=release-tools.git;a=summary

CODE 2: Krita

License :GPL
To make patches on krita you must have a KDE Identity. You then create your code and send it in with a merge request and a detailed explanation of what your code does. The code will then be reviewed by the offical krita developers. who will then decided if and when to apply your patch. Review times are dependent on the amount of patches and time the reviewers have.

References

•  https://en.wikipedia.org/wiki/Krita
• https://docs.krita.org/en/untranslatable_pages/intro_hacking_krita.html 
• https://invent.kde.org/kde/krita/tree/master/3rdparty/ext_libraw