<div dir="ltr">Very lovely report. I love seeing this and encourage you to continue. If others have areas they too are working on - it wouldn't hurt to have good communication.<div><br></div><div>thanks,</div><div>Brendan </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 8, 2016 at 7:10 PM, Jonathan Druart <span dir="ltr"><<a href="mailto:jonathan.druart@bugs.koha-community.org" target="_blank">jonathan.druart@bugs.koha-community.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi devs,<br>
<br>
First, sorry for the [NEW] flag, but it is to make sure everybody<br>
reading the ML will click :)<br>
<br>
I'd like to start a monthly "what's on" email which I will send to koha-devel.<br>
It comes after some discussions at the KohaCon16 with fellows that do<br>
not have the time to follow what's going on in the community and where<br>
they could help on important things.<br>
I used to send one to my partners every month to explain what I did<br>
and what I plan to do, but actually it sounds more a community report<br>
to send to the Koha developers.<br>
So here it is :)<br>
<br>
The goal is to resume in a (relatively) short email what has been<br>
developed in the previous month(s) and what testers/developers can<br>
focus on. It could be critical/major bugfixes, code<br>
refactoring/improvements or even big-but-amazing features waiting for<br>
signoff/QA.<br>
<br>
Over the last months I have mainly focused on refactoring stuffs, fix<br>
plack-related bugs and improvement issues, as well as my usual QA<br>
work.<br>
The refactoring part is not going very well, I have suspended it 2<br>
months ago. The main problem is that the patches are no pushed as fast<br>
as I expected implying a lot of rebases which is time consuming.<br>
By refactoring I mean "moving code from old C4 modules to the new Koha<br>
namespace". The pattern I usually use in the bug report description is<br>
"Move the stuff related code to Koha::Stuff[s]"<br>
<br>
The plack-related bugs were minor, but to provide a full plack<br>
compatibility it was great to have them push quickly. Luckily they<br>
have been signed off and QAed quite quickly, only 2 are still waiting<br>
for QA. The pattern I used in the bug description was "This module is<br>
not plack safe".<br>
<br>
A few words about the performances: You have to know that since 16.05<br>
(and maybe also 3.22) it's highly recommended to use Plack and<br>
Memcache to provide your user a good response time.<br>
We have profiled the code in several areas to find useless processing<br>
time. In some places, the code has been improved, in others it has<br>
completely been removed.<br>
Fixing plack bugs, we have found that we needed to improve our cache<br>
mechanism and we have introduced a L1 memory cache which should bring<br>
us performance gain between 3.22 and 16.05. Note that we do not have<br>
completely finished the work and some more has to been done, so stay<br>
tuned :) If you have any suggestions or leads on that, please open a<br>
bug report and assign it to me.<br>
<br>
There are 2 critical bugs waiting for signoff (bug 16554 and bug<br>
16573), they fix the support of Ubuntu 16.04. So if you plan to<br>
install Koha on the latest Ubuntu, you should have a look at these 2<br>
reports.<br>
<br>
A major enhancement is in the integration queue and it would be great<br>
to see some people (librarians would be awesome) involved in the<br>
testing process. It will allow a patron to place several holds on the<br>
same record (bug 14695). This feature has been expected for more than<br>
3 years now and this is the third attempt.<br>
<br>
During the KohaCon16, I have organised a quick brainstorming about our<br>
implementation of Koha::Object[s] and how we use DBIx::Class. The goal<br>
was not to find a solution but to present the different issues we<br>
face. I'd like to bring again this discussion on koha-devel this<br>
month, listing the pros and cons of our current implementation, and<br>
gathering ideas to improve it.<br>
<br>
Hope this will be helpful for people not heavily involved on IRC or<br>
the bug tracker.<br>
<br>
Cheers,<br>
Jonathan<br>
<br>
References:<br>
Refactoring to Signoff<br>
Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4<br>
Bug 15803 - Koha::AuthorisedValues - Remove GetAuthorisedValueCategories<br>
<br>
Refactoring to QA<br>
Bug 15451 - Move the CSV related code to Koha::CsvProfile[s]<br>
Bug 15839 - Move the reviews related code to Koha::Reviews<br>
Bug 15801 - Move the framework related code to<br>
Koha::BiblioFramework[s] - part 2<br>
Bug 15407 - Move the patron categories related code to<br>
Koha::Patron::Categories - part 2<br>
<br>
Plack bugfixes to QA<br>
Bug 16441 - C4::Letters::getletter is not plack safe<br>
Bug 16443 - C4::Members::Statistics is not plack safe<br>
<br>
Performances entry points are (look at the related bugs using the show<br>
dependency graph):<br>
Bug 15342 - Performance 3.22 - Omnibus<br>
Bug 16044 - Define a L1 cache for all objects set in cache<br>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">---------------------------------------------------------------------------------------------------------------<br>Brendan A. Gallagher<br>ByWater Solutions<br>CEO<br><br>Support and Consulting for Open Source Software<br>Installation, Data Migration, Training, Customization, Hosting<br>and Complete Support Packages<br>Headquarters: Santa Barbara, CA - Office: Redding, CT<br>Phone # (888) 900-8944<br><a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a><br><a href="mailto:info@bywatersolutions.com" target="_blank">info@bywatersolutions.com</a><br></div></div>
</div>