While v1 is still a WIP, it is important to communicate that until it is released, UAVCAN itself is in the state of WIP, too; one should not expect stability from v0.
As I commented on during the dev-call this week: I disagree with this requirement. There arenāt enough pixels/ink dedicated to logos to convey meaningful technical information. We should choose a āpretty pictureā and imbue this icon with meaning through association.
Besides, with your āUā logo I just see a āUā with a pusher propeller
As discussed on the dev-call: Iād like to keep v0 front-and-center until:
The v1 specification has been released and weāve had some time to get feedback.
We have at least 1 full reference implementation available.
Once these two milestones have been reached we can discuss flipping the website messaging to be āv1ā first with āv0ā as a link.
When we do this flip we need to provide careful guidance for v0 support and a porting plan. I really want to let people know that v0 is still supported and weāll accept patches to the reference implementations but that that specification is fixed and will not change.
Well, Iām not a graphic designer so other proposals are welcome but of the ones I submitted what do people like best? (I got rid of the square one because it didnāt meet requirement 4 becoming just a blue box at 16x16)
I do not have strong feelings towards any particular font face.
The option 2 could be okay if we spelled the word āUAVCANā in its entirety (otherwise weāre kind of promoting the old acronym). And possibly added a second line on top, representing the roof of a bike shed.