On 19 June 2018 at 00:47, OpenSmalltalk-Bot <notifications@github.com><br>
wrote:<br>
<br>
><br>
><br>
> > On 18-06-2018, at 8:14 AM, HonshuBloc <notifications@github.com> wrote:<br>
> ><br>
> > Hello<br>
> > I´m a graphic designer looking for cool open source projects to make a<br>
> graphic contribution, for free of course :P<br>
><br>
<br>
Thanks for the offer.<br>
<br>
<br>
<br>
<br>
> > Î´m wondering if you are interested in a new logo for your project.<br>
><br>
> We've been happily using the current one for 22 years now, so probably<br>
> not. Of course, I'm biased since I designed it.<br>
><br>
<br>
Tim, I guess you referring to the Squeak logo (<br>
http://www.rowledge.org/tim/squeak/files/page17_1.jpg) which is well<br>
established.<br>
But I don't think we've long had the OpenSmalltalk "Cog" logo (<br>
http://opensmalltalk.org/static/img/cog.png/).<br>
While its workable, its but a bit "complicated" for a logo.<br>
<br>
Now that we have Spur and Sista as technology components that extend Cog,<br>
it might be good to base a logo on more generic concepts that distinguish<br>
us:<br>
1. message passing between objects<br>
2. object-oriented execution engine<br>
<br>
Are those reasonable?  What other distinctions are important compared to<br>
other systems, and how should they be prioritized for a logo?<br>
<br>
cheers -ben<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/269#issuecomment-398224445">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AhLyW-mtjOHaP9n_DyaYMHZH60FWRme6ks5t-DSsgaJpZM4Ur8j5">mute the thread</a>.<img src="https://github.com/notifications/beacon/AhLyW7RpbacnYJb1NwrmGTTnxo4uRcJDks5t-DSsgaJpZM4Ur8j5.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/269#issuecomment-398224445","url":"https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/269#issuecomment-398224445","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}</script>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/OpenSmalltalk/opensmalltalk-vm","title":"OpenSmalltalk/opensmalltalk-vm","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/OpenSmalltalk/opensmalltalk-vm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bencoman in #269: On 19 June 2018 at 00:47, OpenSmalltalk-Bot \u003cnotifications@github.com\u003e\nwrote:\n\n\u003e\n\u003e\n\u003e \u003e On 18-06-2018, at 8:14 AM, HonshuBloc \u003cnotifications@github.com\u003e wrote:\n\u003e \u003e\n\u003e \u003e Hello\n\u003e \u003e I´m a graphic designer looking for cool open source projects to make a\n\u003e graphic contribution, for free of course :P\n\u003e\n\nThanks for the offer.\n\n\n\n\n\u003e \u003e Î´m wondering if you are interested in a new logo for your project.\n\u003e\n\u003e We've been happily using the current one for 22 years now, so probably\n\u003e not. Of course, I'm biased since I designed it.\n\u003e\n\nTim, I guess you referring to the Squeak logo (\nhttp://www.rowledge.org/tim/squeak/files/page17_1.jpg) which is well\nestablished.\nBut I don't think we've long had the OpenSmalltalk \"Cog\" logo (\nhttp://opensmalltalk.org/static/img/cog.png/).\nWhile its workable, its but a bit \"complicated\" for a logo.\n\nNow that we have Spur and Sista as technology components that extend Cog,\nit might be good to base a logo on more generic concepts that distinguish\nus:\n1. message passing between objects\n2. object-oriented execution engine\n\nAre those reasonable?  What other distinctions are important compared to\nother systems, and how should they be prioritized for a logo?\n\ncheers -ben\n"}],"action":{"name":"View Issue","url":"https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/269#issuecomment-398224445"}}}</script>
<script type="application/ld+json">{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [OpenSmalltalk/opensmalltalk-vm] Design contribution (#269)",
"sections": [
{
"text": "",
"activityTitle": "**Ben Coman**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@bencoman",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"OpenSmalltalk/opensmalltalk-vm\",\n\"issueId\": 269,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"OpenSmalltalk/opensmalltalk-vm\",\n\"issueId\": 269\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/269#issuecomment-398224445"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 347064569\n}"
}
],
"themeColor": "26292E"
}</script>