It’s my turn again to do the dev diary.
For those that don’t remember, I’m the Technical Lead for the Community Platform development team.
First of all, I would like to give a warm welcome to the newest member of the team - Blake. Blake needs no introduction, he has been with us as a giffgaff member for over 9 years (and he has the emails to prove it).
Blake’s focus this week has been to get his development environment up and running and acquaint himself with the code base. He has improved the postcode flagging and started work improving the profanity filters. Nice one, @ajapayne! 👍️
@ianmorland has been focusing his efforts on making sure that the payback reports are generated and sent to the appropriate teams in time for processing this months payback. After a bit of tweaking, he has managed to bring the data processing down from 6+ hours to about 30-40 minutes. Moving forward, most of the community payback data extraction is now automated, leaving only a very minimal amount of manual processing to do each month, from now onwards.
We’ve been getting a lot of feedback about the usability of the community forums which has been transformed into action points for the development team to focus on.
I’m pleased that @ianmorland , @andrewdyer and @harrycollins97 have started making progress on these - we have already improved the design and flow of various elements on the platform including Private Discussions.
@andrewdyer has been continuing his work from last week in improving some of the tools educators have in making sure our members have a safe and fun platform to communicate on.
Finally, I’ve been continuing the challenge of optimising the load times of various parts of the site. Part of it could be solved with our work on Elastic Search, unfortunately the extendable nature of Flarum means we cannot completely optimise the algorithm as some of the performance hits are coming from our plugins. Investigation work continues around this area.
That’s it for today.
Wishing you all a pleasant weekend!