Hi! I recently found Piwigo and after comparing it against Koken (defunct?) and Lychee (lacking features), decided to stick with it. I'm a (primarily backend) software engineer by profession and would like to volunteer to help make improvements to Piwigo's core.
If there's a roadmap with prioritized items I'd be happy to help with those. Otherwise, some things I saw that might benefit from some work are:
1. Overhauling the database interface functions to use bound parameters instead of string concatenation for specifying values. I'm aware this would be no small lift. Piwigo has some nice mass and single operation database utility functions, but using string concatenation to supply values to SQL statements is the beginning of SQL-injection vulnerabilities. That concern disappears with bound parameters.
2. I'd like to be able to use any UTF-8 character in a photo filename. Bound parameter is likely a good first step towards that.
Any advice along the lines of what would be most useful for the project would be helpful. Also, does the project have a roadmap, style guide or unit tests?
Thanks!
-Pat
Offline
Cool. I see 413 open issues. Are they prioritized any way? Oldest first? Newest first?
Does the project have a style guide? Does it have unit tests?
Offline
Ah, labels. Cool!
Offline
Tell me if you need more "help wanted" or "for beginners" labels on current issues :-)
Offline