search

USRSE / blog

syndicated blog for research software engineer stories and experiences
https://usrse.github.io/blog/
1 stars 5 forks source link

Update logo to official svg logo #30

Open lparsons opened 5 years ago

lparsons commented 5 years ago

Update the logo to the official (fixed) US-RSE svg logo.

vsoch commented 5 years ago

I don't approve - this logo is a simplified version that is much more elegant to begin with, see the site https://us-rse.org/blog/.

vsoch commented 5 years ago

This is a downgrade https://233-186452639-gh.circle-artifacts.com/0/blog/index.html

lparsons commented 5 years ago

Sorry, but the Steering Committee is not comfortable with an unofficial logo being used (esp on us-rse.org).

lparsons commented 5 years ago

Let's try to get a version of the logo without the text but with all the design elements. I agree that it would be nice to have an official version without the added text... @cmaimone Is that doable?

vsoch commented 5 years ago

Sorry, but the Steering Committee is not comfortable with an unofficial logo being used (esp on us-rse.org).

This is... not how you grow a community.

lparsons commented 5 years ago

Pushed an update with a cleaner version of the logo with no words and no background.

cmaimone commented 5 years ago

@vsoch It could have been put better, but I think @lparsons was mostly sharing that the SC isn't comfortable with versions of the logo being used to represent the org that are significantly different -- there are versions with no text, and one that's just the center square that are variations we've used though.

I get that the comment effectively shut down discussion, but it is doesn't need to.

Other than the aesthetic argument about the logo generally (which is a separate discussion), is there something here we're missing?

lparsons commented 5 years ago

I see how my comment wasn't well worded, but I honestly did not intend to shut down discussion. It was simply done in a hurry and too curt. For that I apologize.

vsoch commented 5 years ago

Almost! The white lines should probably be white and not transparent?

9A61FC44-DBBD-45A6-9181-4231BE623F56

For reference, the current:

29DA7961-80FE-4CAE-B7A2-4D6B05EDD286

I’m sorry I’m really upset by these interactions, it doesn’t feel like community decisions, more like something else.

lparsons commented 5 years ago

Almost! The white lines should probably be white and not transparent?

Agreed, I think the lines probably should be white. Might be more consistent with the other versions that way.