[guardian-dev] otrfileconverter/keysync branding session

[Hans-Christoph Steiner]

hey all,

Since Mark, Nathan, and I will be in the same room tomorrow, we're going to
kick this off for an hour session tomorrow, Friday, at noon Eastern time.  We
can set up a hangout for any remote people that want to join.

.hc

On 07/16/2013 12:04 AM, Hans-Christoph Steiner wrote:
> 
> 
> On 07/15/2013 11:58 AM, Nathan of Guardian wrote:
>>
>>
>> Hans-Christoph Steiner <hans at guardianproject.info> wrote:
>>
>>>
>>> Now that we have a fully working OTR key sync system, I think its time
>>> we
>>> figured out how this app should be represented to users.  I originally
>>> chose
>>> the name otrfileconverter just to have a working title.  Nathan
>>> proposed keysync.
>>>
>>> I'm proposing we have a branding session where we figure out a name for
>>> the
>>> app, how to describe it and teach it, and how best to shape the app to
>>> fit
>>> into well established user patterns.  We could either do it at
>>> SATELLITE if
>>> Nathan and Abel overlap, otherwise we can do it on the internet.
>>
>> I think we should broaden the discussion to the larger feature concept of key/identity 
>> sharing and syncing between devices as well. For example, if we use NFC to sync public
>> keyrings between devices, that feature or activity should also have a name.
> 
> I think it makes sense to talk about that as the long term goal of this work,
> but I fear that it could turn into a big distraction, taking us away from
> discussing how best to represent what we currently have working.  Identity
> syncing is a big problem, and we only have one small part of it working.  So I
> think we should focus on best describing the features we have now and can
> deliver in the next few months.  We can talk about the long term goal of full
> crypto identity sync as long as it directly informs what we have now.
> 
> So in terms of concrete things that we can do in this session:
> 
> 1) discuss the OTR key sync bootstrapping experience and figure out how to
> represent it in the desktop app
> 
> 2) discuss naming and language to describe how to use it
> 
> 3) figure out direction for logos, graphics, branding etc.
> 
> .hc
> 
> 

-- 
PGP fingerprint: 5E61 C878 0F86 295C E17D  8677 9F0F E587 374B BE81