- Issue was unassigned.
- Status changed to Needs review
about 2 years ago 6:42am 4 May 2023 - 🇮🇳India urvashi_vora Madhya Pradesh, India
Hi,
I would like to suggest a few designs. Please have a look.Thanks
- Status changed to RTBC
about 2 years ago 12:28am 20 May 2023 - 🇺🇸United States leslieg
Entity-Reference-Revision-Logo-5.png is a ng, 512x512 and less than 10k
- 🇨ðŸ‡Switzerland berdir Switzerland
This is a hard one to have a logo for and I think it's not that relevant because people will install this just because other modules depend on it, like Paragraphs or Commerce.
I like the style of version 5 best as well. That said, the logo doesn't really make sense to me. the magnifying glass implies search related features while the arrow in both direction implies bidirection. While it actually kind of does that, it's not really the central part of its functionallity. What about removing the magnifying glass, making the arrow directional and then visual revisions/versions a bit so we can point to a specific version? I'm imagining roughly something like the following for versions, but with the element used in the current logo:
Thoughts?
Also, shouldn't we keep a source/editable version of this file in the repository as well, like an SVG? So that we can update it in the future? Also not sure how issue credits work, as @leslieg uploaded this in the project, shouldn't we ensure the person who created it gets credits there as well?
And last comment, it would be very helpful for maintainers if you could already open merge request with the file, then you can easily ensure that it will have the correct filename and so on. You can actually do that through the, for ERR, I first requested a issue fork to be opened, then clicking there brings me to https://git.drupalcode.org/issue/entity_reference_revisions-3362560/-/tr..., where a file can be uploaded and committed with the "+" button and then UPload image.
- 🇮🇪Ireland lostcarpark
I agree it's a tricky concept to encompass in a logo.
Here's a possible idea...
Hopefully it conveys the idea of a of an entity referencing another, and previous versions stacked behind.
I've attached as a PNG file, shrunk to be under 10kb. I've also included the SVG file so it can be added to the repo. I had to add .txt to the file extension so it could upload.
- Status changed to Needs review
12 months ago 11:49pm 11 July 2024 - 🇮🇪Ireland lostcarpark
I wonder does this issue need further review. There seem to have been several options proposed, but no actual discussion on them. Not sure was there any reasoning in selecting the logo in the Proposed Resolution.
Setting back to Needs Review. Please move back to RTBC if this is settled.
- 🇮🇪Ireland lostcarpark
I do actually like @urvashi_vora's logo in the Proposed Resolution, but there is a lot of whitespace around the edges. I feel it needs the logo part blown up to fill the space.
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
@lostcarpark Would you rather we update the one in the summary or switch to your proposal? I like the summary one but agree it needs less whitespace.
- 🇺🇸United States leslieg
I am moving this back to RTBC since the Proposed resolution was already provided to the maintainer. They have a link to this ticket of they want to review other options
- Status changed to Fixed
11 months ago 9:15pm 30 July 2024 - Status changed to Needs work
11 months ago 7:56am 31 July 2024 - 🇨ðŸ‡Switzerland berdir Switzerland
I already gave feedback in #9, IMHO the current logo does not represent the purpose of this project.