sajolida:
> Hi VeraCrypt,
Hi again VeraCrypt!
Did our initial email reached you well?
In the meantime we drafted two possible versions of our logo for
VeraCrypt Mounter:
- If your logo is free software and there's no trademark issue with us
using it, we'll probably use this icon:
https://labs.riseup.net/code/attachments/2079/package-vc.png
- Otherwise, we'll probably use this icon:
https://labs.riseup.net/code/attachments/2078/package-key.png
I'm keeping the full content of our first email here below...
> I'm writing you on behalf of Tails: https://tails.boum.org/.
>
> I'm putting in copy our public development mailing list.
>
> Over the last months, we've been working on integrating VeraCrypt in
> Tails and GNOME in general. The native VeraCrypt application not being
> included in Debian, we've opted for extending the native GNOME
> technologies to support opening VeraCrypt volumes. (We are not working
> on allowing the creation of new volumes in GNOME.)
>
> See our pull requests on:
>
> GNOME Disks:
> https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/84#note_222551
>
> GNOME Shell:
> https://gitlab.gnome.org/GNOME/gvfs/merge_requests/4
>
> While doing user testing on our design for this feature we discovered
> that Tails users, especially when trying to unlock file containers, were
> almost always looking for something called VeraCrypt in the Applications
> menu to unlock their containers.
>
> To help them on their way, we designed a very simple GNOME applications
> that offers a file chooser to select a file container and then try to
> mount it using the underlying GNOME technologies. We called this app
> "VeraCrypt Mounter".
>
> The code is very minimal and it performed well during usability testing.
>
> The code:
> https://gitlab.com/segfault3/veracrypt-mounter.git
>
> Sketch of the interface:
> https://labs.riseup.net/code/attachments/download/1842/veracrypt-mounter.png
>
> We're now designing an icon for this application and we wanted to check
> with you to which extent we could reuse the VeraCrypt logo to make a
> visual reference to your native implementation.
>
> For example, we created the two icons in attachment. One reusing the
> full "VC" icon and one reusing only the "V" part of the logo.
>
> Would these be fine to use?
>
> What are the license and terms of use of the VeraCrypt logo?
>
> Note that VeraCrypt Mounter is only meant to be distributed as part of
> Tails and the icon would only appear in the Applications menu of GNOME
> in Tails. See screenshot in attachment.
>
> NB: You might also be interested in reading the results of the
> quantitative survey that we did as user research before designing our
> solution. It gives interesting insights on the popularity of the main
> features of VeraCrypt:
>
> https://tails.boum.org/blueprint/veracrypt/
>
> Cheers,
--
sajolida
%0A>%20>%20%0A>%20>%20See%20our%20pull%20requests%20on:%0A>%20>%20%0A>%20>%20GNOME%20Disks:%0A>%20>%20https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/84#note_222551%0A>%20>%20%0A>%20>%20GNOME%20Shell:%0A>%20>%20https://gitlab.gnome.org/GNOME/gvfs/merge_requests/4%0A>%20>%20%0A>%20>%20While%20doing%20user%20testing%20on%20our%20design%20for%20this%20feature%20we%20discovered%0A>%20>%20that%20Tails%20users,%20especially%20when%20trying%20to%20unlock%20file%20containers,%20were%0A>%20>%20almost%20always%20looking%20for%20something%20called%20VeraCrypt%20in%20the%20Applications%0A>%20>%20menu%20to%20unlock%20their%20containers.%0A>%20>%20%0A>%20>%20To%20help%20them%20on%20their%20way,%20we%20designed%20a%20very%20simple%20GNOME%20applications%0A>%20>%20that%20offers%20a%20file%20chooser%20to%20select%20a%20file%20container%20and%20then%20try%20to%0A>%20>%20mount%20it%20using%20the%20underlying%20GNOME%20technologies.%20We%20called%20this%20app%0A>%20>%20%22VeraCrypt%20Mounter%22.%0A>%20>%20%0A>%20>%20The%20code%20is%20very%20minimal%20and%20it%20performed%20well%20during%20usability%20testing.%0A>%20>%20%0A>%20>%20The%20code:%0A>%20>%20https://gitlab.com/segfault3/veracrypt-mounter.git%0A>%20>%20%0A>%20>%20Sketch%20of%20the%20interface:%0A>%20>%20https://labs.riseup.net/code/attachments/download/1842/veracrypt-mounter.png%0A>%20>%20%0A>%20>%20We're%20now%20designing%20an%20icon%20for%20this%20application%20and%20we%20wanted%20to%20check%0A>%20>%20with%20you%20to%20which%20extent%20we%20could%20reuse%20the%20VeraCrypt%20logo%20to%20make%20a%0A>%20>%20visual%20reference%20to%20your%20native%20implementation.%0A>%20>%20%0A>%20>%20For%20example,%20we%20created%20the%20two%20icons%20in%20attachment.%20One%20reusing%20the%0A>%20>%20full%20%22VC%22%20icon%20and%20one%20reusing%20only%20the%20%22V%22%20part%20of%20the%20logo.%0A>%20>%20%0A>%20>%20Would%20these%20be%20fine%20to%20use?%0A>%20>%20%0A>%20>%20What%20are%20the%20license%20and%20terms%20of%20use%20of%20the%20VeraCrypt%20logo?%0A>%20>%20%0A>%20>%20Note%20that%20VeraCrypt%20Mounter%20is%20only%20meant%20to%20be%20distributed%20as%20part%20of%0A>%20>%20Tails%20and%20the%20icon%20would%20only%20appear%20in%20the%20Applications%20menu%20of%20GNOME%0A>%20>%20in%20Tails.%20See%20screenshot%20in%20attachment.%0A>%20>%20%0A>%20>%20NB:%20You%20might%20also%20be%20interested%20in%20reading%20the%20results%20of%20the%0A>%20>%20quantitative%20survey%20that%20we%20did%20as%20user%20research%20before%20designing%20our%0A>%20>%20solution.%20It%20gives%20interesting%20insights%20on%20the%20popularity%20of%20the%20main%0A>%20>%20features%20of%20VeraCrypt:%0A>%20>%20%0A>%20>%20https://tails.boum.org/blueprint/veracrypt/%0A>%20>%20%0A>%20>%20Cheers,%0A>%20%0A>%20--%20%0A>%20sajolida%0A>%20%0A>%20 "Vastaa")
