On Fri, Jul 2, 2021 at 5:28 PM Daniel Sahlberg <daniel.l.sahlb...@gmail.com> wrote: >> Yes; also I did a little bit of graphics work with the various logo >> and icon files; mostly to rasterize the original vector artwork (in >> SVG format IIRC?) to various resolutions and formats expected by >> various browsers and smartphones, though I seem to recall that I had >> to do a little massaging of the vector formats for some reason. The >> one where I got "creative" was tile-wide.png; we didn't have a >> wide-format file so I made that as a placeholder. I wasn't very happy >> with it at the time but I just looked at it again and now I think it >> actually looks cool. Let me know what you think... > > > Not a graphics designer ;-) but I try to keep graphics elements separate (ie, > the square separate without any other elements intruding its space). We have > already, slightly, change the original logo by moving the text SUBVERSION > from within the square to outside of the square and adding some blue bars > above/below so I don't know how strict we should be with this "rule". > > As far as I can find this wide logo is used only in browserconfig.xml, which > in turn is only used for Internet Explorer and possibly Edge Legacy. As these > are both EOL, maybe the discussion is moot and we can remove > browserconfig.xml, tile.png and tile-wide.png?
Sure, if it's not needed anymore then feel free to remove it. As to whether we have to strictly stay with the exact original logo without modifying it (i.e., keeping just the stylized S without the text under it), I don't really know, but we've had an altered version of the Subversion logo as the site logo for years, possibly decades actually. I lost the part of your reply where you mentioned merging to staging. I was hoping to test with a web server and browser, but it probably won't happen for at least a couple of days, so if you'd like, feel free to merge to staging, give everyone a few days to look at it, and worst case if there's a problem it can always be unmerged from staging (but I don't think that will need to happen). Thanks for driving this forward! Cheers, Nathan
