The question is there as there are indeed big chains for which you might already know the icon exists. When I worked on this in the past I had to doublecheck for every icon whether it already exists or not to prevent making duplicates. Hence, when you already know it exists it can save me some time. Mapping icons is way simpler than creating new ones in the end.
Jeroen π³οΈβπ Someone has to keep an eye on all the icons to prevent them being switched to cute cat photo's.
That's what the Pull-Request mechanism is for. Code is only merged into the codebase when it has been reviewed and approved by trusted people (either bunq employees or people they trust). π But it would take the need for proper reviews of course. π
Jeroen π³οΈβπ And I'd guess that you'd then run in more trouble regarding rights on the logo and companies not wanting that they are somewhere on a public repository with no copyright and so on.
Fair enough, but that issue is in place now as well right? But when a company does not want to appear in the lists/wants to appear differently (like ING did for example) then they can simply send a message and bunq will honor that. π