Open Stack

On Feb 21, 2014, at 3:24 PM, Jacki Bauer <jacki.bauer at rackspace.com> wrote:

> Thanks Liz! That definitely helps.
> 
> Couple questions:
> How do you make yourself the assignee? Do you need certain permissions on the site or is there a point of contact?

Hi Jacki,

Glad this is helping. You might need to be a member of the group to be able to edit the assignee on any of the blueprints. I’ve added Jarda to this e-mail since he’s done most of the work around setting this area up. If you click on the blueprint to view more details there is an “Edit” icon next to the assignee field that should appear. Let me know if you don’t see this and I can look into it closer to see if there are permissions that have been set here.

Jarda - Would you be able to add Jacki to the UX group? Should we open this up to be more public for future contributors?

> 
> Who can edit the Launchpad site? Can we summarize the content of these emails on the overview page so people will know how to contribute?
> 

I have privileges to edit the site and have added a little “Getting Started” section to the main page. As someone who is just getting familiar with the process, let me know what you think would be helpful to have here :)

Thanks,
Liz

> 
> On Feb 20, 2014, at 9:03 AM, Liz Blanchard <lsurette at redhat.com> wrote:
> 
>> 
>> On Feb 19, 2014, at 3:56 PM, Jacki Bauer <jacki.bauer at rackspace.com> wrote:
>> 
>>> It looks like there was a lot of activity on the UX project last fall but not much since. I'm confused by things like horizon-ia-improvement in the UX launchpad and navigation-enhancement in Horizon. What's the difference between these two? I think UX should be it's own project for sure, but what do we do about redundancies like this? How do we make it easier so new designers can pick up work and be confident the blueprint they are working on isn't outdated or duplicated in a different project? Also, how can we prioritize the blueprints to help people select the work that is most needed?
>> 
>> Hi Jacki,
>> 
>> Great questions. SoŠthere definitely has been some redundancies between Horizon and the UX projects. I think what we¹ve been trying to do is make sure the design pieces are completed in the UX launchpad project blueprints and the development is done in Horizon. The ³Navigation Enhancements² that they implemented this release in Horizon was different from the ultimate IA Improvements that we¹d like to see. I think eventually, once this design is in a good spot, we¹d create a blueprint in Horizon for the development to happen. I think if we end up with a group of designers working on Horizon or any other component in OpenStack we might want to consider a weekly sync up meeting. There is an assignee field on the blueprints too and it¹s generally known that if this is blank, anyone should feel free to pick it up and work on it. Of course, they should review it with other designers when they have a good first draft. We can definitely go through an prioritization effort if you think the current priorities don¹t make sense. 
>> 
>> As a side note: This is all very new since it¹s only been a few of us working on specific things, so it¹s very much an early process that can be updated and changed as needed :)
>> 
>> Thanks,
>> Liz
>> 
>>> 
>>> I'm asking these questions generally, but also for myself, as I'm finding it hard to figure out what's what!
>>> 
>>> -Jacki
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Feb 18, 2014, at 7:21 AM, Liz Blanchard <lsurette at redhat.com> wrote:
>>> 
>>>> 
>>>> On Feb 17, 2014, at 7:49 PM, Kruithof, Piet <pieter.c.kruithof-jr at hp.com> wrote:
>>>> 
>>>>> I¹m wondering whether we should change the name to the UX Project since the scope of the team is slowly evolving into other areas (such as usability).  For example, I¹m thinking that we may want to a Card Sort to understand how users conceptualize the Horizon info architecture.  
>>>> 
>>>> There is already a UX project in launchpad that we should take advantage of here. I think it¹s the first step to get everyone working on UX stuff together :)
>>>> 
>>>> https://blueprints.launchpad.net/openstack-ux
>>>> 
>>>> You¹ll notice there are already blueprints for the work we had planned to do early on for horizon personas, triple personas, and user community testing. Additionally there are blueprints for things that we¹ve talked about like IA improvements and navigation enhancements are already here. Please feel free to edit these blueprints or take ownership of anything that you might be working on that doesn¹t have an owner.
>>>> 
>>>> Thanks,
>>>> Liz
>>>> 
>>>>>  
>>>>> Piet
>>>>>  
>>>>>  
>>>>>  
>>>>>  
>>>>> From: Nick Chase [mailto:nchase at mirantis.com] 
>>>>> Sent: Thursday, February 13, 2014 7:43 AM
>>>>> To: openstack-personas at lists.openstack.org
>>>>> Subject: Re: [Openstack-personas] Personas project in Launchpad?
>>>>>  
>>>>> +1
>>>>>  
>>>>> ----  Nick
>>>>>  
>>>>> 
>>>>> On Thu, Feb 13, 2014 at 9:16 AM, Dave Neary <dneary at redhat.com> wrote:
>>>>> Hi,
>>>>> 
>>>>> Would there be interest in having a personas project in Launchpad?
>>>>> 
>>>>> This would have a few benefits:
>>>>> * Source control to version control the various documents we'll be
>>>>> working on
>>>>> * Bug tracker to enable issue tracking
>>>>> * Committers would be considered ATCs and get Design Summit invitations
>>>>> and free Summit passes, where we can attend & evangelise Personas to
>>>>> developers
>>>>> 
>>>>> Using Launchpad for the third benefit is kind of a hack - there's no
>>>>> good way to get official recognition of time & effort spent working on
>>>>> personas (and other non-technical subject areas like marketing,
>>>>> documentation), but using source control to track things provides a nice
>>>>> easy way to do so.
>>>>> 
>>>>> Anyone interested? If so, anyone know what's involved?
>>>>> 
>>>>> Thanks,
>>>>> Dave.
>>>>> --
>>>>> Dave Neary - Community Action and Impact
>>>>> Open Source and Standards, Red Hat - http://community.redhat.com
>>>>> Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
>>>>> 
>>>>> _______________________________________________
>>>>> openstack-personas mailing list
>>>>> openstack-personas at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas
>>>>>  
>>>>> _______________________________________________
>>>>> openstack-personas mailing list
>>>>> openstack-personas at lists.openstack.org
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas
>>>> 
>>>> _______________________________________________
>>>> openstack-personas mailing list
>>>> openstack-personas at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas
>>> 
>>> _______________________________________________
>>> openstack-personas mailing list
>>> openstack-personas at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas
>> 
> 
> _______________________________________________
> openstack-personas mailing list
> openstack-personas at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-personas/attachments/20140224/dc147da4/attachment-0001.html>