Re: [libreoffice-design] Re: [Libreoffice-ux-advise] Inclusion of Gnome Tango Icons?
Hi all, Am Samstag, 12. Mai 2012, 00:21:29 schrieb Mirek M.: Hi everyone, I've received a response from Lapo, who seems to be ok with relicensing the icons. He also offered to design any icons we need to avoid feeling like a mishmash icon set. This is great news. If we have a willing icon designer, we can actually start to meassure the quality of our existing icons, respecting our international users. This way we can step-by-step increase the quality by replacing the worst icons and hence ensuring a consistent icon quality over time. We would need a small team of perhaps 2 or 3 people who are willing to work on this topic over a longer period of time to get some real results here. We would have to work closely with the localization teams and we would need the icon designers willing to support us in this process, of course. I am willing to mentor the process and help you to do it efficiently. I can provide the needed tools (aGPL) including the hosting of the service. What do you guys think? Anyone interested? Cheers, Björn Here's the message: -- Forwarded message -- From: Lapo Calamandrei calamand...@gmail.com Date: 2012/5/11 Subject: Re: Gnome Icon Set To: Mirek M. maz...@gmail.com Cc: Jakub Steiner jim...@gmail.com Hi Marek, I think every icon here is made by Jakub or myself, so thumbs up for relicensing this stuff whatever license LibreOffice needs. Also feel free to ask any custom icon you may need, I'm a LibreOffice user and I hate mishmash icon sets :-) Ciao Lapo 2012/5/10 Mirek M. maz...@gmail.com: Hi Lapo, Here's the complete list of icons we'd like to use (from Astron): http://nabble.documentfoundation.org/attachment/3645733/0/listoficons.txt. If some of the icons are not authored by you, could you point us to the actual author(s)? Thanks. :) -- www.OpenUsability.org www.OpenSource-Usability-Labs.com -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-design] Think, don't just do - WAS: Impress remote
Hi all, trying to find some answers to the raised questions: # Structure (of artifacts) In my experience we will need to set-up at least the following artifacts (in whichever way we are going to produce them in the end): 1. Vision: Here are two examples of visions: I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the Earth. (John F. Kennedy, May 25, 1961) The iPod will be a portable digital music player that will hold 5000 songs. It will have a battery life measured in days, not hours. You will navigate the thousands of songs with a single finger. You will sync all your music from your computer to the iPod in minutes automatically, so you can have all your music in your pocket. (said to be formulated by Steve Jobs end of the 1990ies - might be an urban myth though...) To sum it up - The vision gives a clear goal (benefit) that helps to unify all people involved into making it become real - It is commonly understandable and does not provide technical solutions - leaves enough room for creativity - helps to provide criteria so that different people in similar situations will likely come to the similar decission - is short and hence present to everyone involved into the process - We would have to involve all LibreOffice people to find this vision. This cannot be tested or validated with users. It provides the frame we want to achieve. 2. Personas: Personas help us to understand and focus on certains users. Personas can be validated and quality assured by the users. Hope creating and working with personas is known to people on this list. 3. Situationas Situationas are the situation / setting equivalent to Personas. They help us to understand in which situations / environments our product is beeing used. These can again be validated and quality assured by the users. 4. Goals / Core Usability Goals When we place a Personas into a Situationa, we can understand the goals a person has in this situation. Yes, this gives a matirx that can be large. But again, we can validate and quality assure these with the users. From these goal we can derive the actual usability goals (e.g. learnability, Error prone, don't feel stupid,...) that can help us to design and later on meassure the success of our designs in usability tests. 5. Features / Szenarios On this basis we can derive the actually needed features by creating szenarios of the usage. Again this can be tested with the users by using imagination techniques. These can also lead to wireframes or other mock-ups of the intended solution, so this is actually the bridge to design... # Do we need to do user research for every project? No. If we have these foundations we can build upon, we only need to do user research if we encounter any gaps. Usually the above mentioned artifacts should be created rather independently to current project. But staying real - it makes most sense to only create the artifacts that are currently needed. This way all the artifacts are created over time. So instead of a workflow for every project, I propose to rather create sets of artifacts that every project would have to refer to, to reason the created solutions - but every project needs a maximum of freedom how to solve the problem. People are very different how they work. The task might be very different and needs different approaches... # Tool? With OpenUsabilily, KDE and other free software products, we are working on a tool, that helps us to actually do these things. This tool (User Weave) will be published under an aGPL soonish. My company wil then sponsor the hosting of this tool, so we can easily use it for our purposes, without having to deal with technical issues... So I would be happy if we would use and improve this tool for our needs. What do you think? # Start? We need to start at the beginning. Let's start to work on a common vision for LibreOffice. We will need a small team that conducts a couple of surveys in order to get feedback from the community - it would be perfect if we would finish this process in time for the LibreOffice Conference - just to give you an idea about the length of such a process... Paralle we could use user-surverys (such as the proposed work on the iconset) to gather information about our users in order to create first sets of personas. Ok, so much for today. I am curious for your thoughts on this Cheers, Björn Am Mittwoch, 9. Mai 2012, 11:58:42 schrieb Jay Lozier: On 05/09/2012 07:14 AM, Mirek M. wrote: Hi Bjorn, 2012/5/9 Björn Balazsb...@lazs.de Hi all, just a short additional note - a more detailed answer will follow in the next days: Please do not mix up user testing user research. :D funny, I was convinced this whole time that you were talking about user testing oh well... RESEARCH is about understanding (and creating
[libreoffice-design] Design Ethos
Hi everyone, As our design team gains members and the number of projects we tackle grows, it increasingly seems like we need some basic principles to guide our designs. That's why I'm starting a wiki page for determining our design ethos [1]. The point of it is to find several key points that define great design. These principles should be generally applicable, whether we're designing something as simple as a remote control app or as complex as a social network like Diaspora. They also shouldn't be weighed against what LibreOffice currently is -- these principles will define the future of LibreOffice, and if we want its future to be excellent, we need to change what LibreOffice is about, turn it from an MS Office-wannabe to an application suite that can stand its own. Anyway, please submit your suggestions to the wiki [1]. [1] https://wiki.documentfoundation.org/Design/Ethos -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-design] Re: [Libreoffice-ux-advise] Inclusion of Gnome Tango Icons?
2012/5/14 Björn Balazs b...@lazs.de Hi all, Am Samstag, 12. Mai 2012, 00:21:29 schrieb Mirek M.: Hi everyone, I've received a response from Lapo, who seems to be ok with relicensing the icons. He also offered to design any icons we need to avoid feeling like a mishmash icon set. This is great news. If we have a willing icon designer, we can actually start to meassure the quality of our existing icons, respecting our international users. This way we can step-by-step increase the quality by replacing the worst icons and hence ensuring a consistent icon quality over time. I'm not sure if I would see Lapo as a willing icon designer -- he's involved in other projects, most notably Gnome, and his time and energy is limited (at least that's the way I see it). I agree with replacing the worst icons first, though, of course. We would need a small team of perhaps 2 or 3 people who are willing to work on this topic over a longer period of time to get some real results here. We would have to work closely with the localization teams and we would need the icon designers willing to support us in this process, of course. Why the localization teams? Both Gnome and Tango discourage against localizing icons. Rather, to represent text, they use the A glyph, which is the first letter in the Latin, Greek, and Cyrillic alphabets. It has been thoroughly tested in a variety of projects using the Tango icons, like LibreOffice, Inkscape, GIMP, etc. I am willing to mentor the process and help you to do it efficiently. I can provide the needed tools (aGPL) including the hosting of the service. What service? What do you actually propose to do? How would the team work? What do you guys think? Anyone interested? Icon design isn't really my turf, so not me. Cheers, Björn Here's the message: -- Forwarded message -- From: Lapo Calamandrei calamand...@gmail.com Date: 2012/5/11 Subject: Re: Gnome Icon Set To: Mirek M. maz...@gmail.com Cc: Jakub Steiner jim...@gmail.com Hi Marek, I think every icon here is made by Jakub or myself, so thumbs up for relicensing this stuff whatever license LibreOffice needs. Also feel free to ask any custom icon you may need, I'm a LibreOffice user and I hate mishmash icon sets :-) Ciao Lapo 2012/5/10 Mirek M. maz...@gmail.com: Hi Lapo, Here's the complete list of icons we'd like to use (from Astron): http://nabble.documentfoundation.org/attachment/3645733/0/listoficons.txt. If some of the icons are not authored by you, could you point us to the actual author(s)? Thanks. :) -- www.OpenUsability.org www.OpenSource-Usability-Labs.com -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-design] Think, don't just do - WAS: Impress remote
Hi Björn, 2012/5/14 Björn Balazs b...@lazs.de Hi all, trying to find some answers to the raised questions: # Structure (of artifacts) In my experience we will need to set-up at least the following artifacts (in whichever way we are going to produce them in the end): 1. Vision: Here are two examples of visions: I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to the Earth. (John F. Kennedy, May 25, 1961) The iPod will be a portable digital music player that will hold 5000 songs. It will have a battery life measured in days, not hours. You will navigate the thousands of songs with a single finger. You will sync all your music from your computer to the iPod in minutes automatically, so you can have all your music in your pocket. (said to be formulated by Steve Jobs end of the 1990ies - might be an urban myth though...) To sum it up - The vision gives a clear goal (benefit) that helps to unify all people involved into making it become real - It is commonly understandable and does not provide technical solutions - leaves enough room for creativity - helps to provide criteria so that different people in similar situations will likely come to the similar decission - is short and hence present to everyone involved into the process - We would have to involve all LibreOffice people to find this vision. This cannot be tested or validated with users. It provides the frame we want to achieve. Of course. How would you propose we do this? On the IRC? Across mailing lists? How would we agree on a common vision? I believe we should agree on something unanimously... My vision would probably be to make LibreOffice popular not as an alternative to MS Office, but on its own right, as a set of simple and straightforward tools that each do their one job as well as possible (i.e. Writer helps you produce great-looking documents, Impress helps you supplement a great speech, Calc helps you interpret your data, etc.). 2. Personas: Personas help us to understand and focus on certains users. Personas can be validated and quality assured by the users. Hope creating and working with personas is known to people on this list. 3. Situationas Situationas are the situation / setting equivalent to Personas. They help us to understand in which situations / environments our product is beeing used. These can again be validated and quality assured by the users. 4. Goals / Core Usability Goals When we place a Personas into a Situationa, we can understand the goals a person has in this situation. Yes, this gives a matirx that can be large. But again, we can validate and quality assure these with the users. From these goal we can derive the actual usability goals (e.g. learnability, Error prone, don't feel stupid,...) that can help us to design and later on meassure the success of our designs in usability tests. 5. Features / Szenarios On this basis we can derive the actually needed features by creating szenarios of the usage. Again this can be tested with the users by using imagination techniques. These can also lead to wireframes or other mock-ups of the intended solution, so this is actually the bridge to design... # Do we need to do user research for every project? No. If we have these foundations we can build upon, we only need to do user research if we encounter any gaps. Usually the above mentioned artifacts should be created rather independently to current project. But staying real - it makes most sense to only create the artifacts that are currently needed. This way all the artifacts are created over time. So instead of a workflow for every project, I propose to rather create sets of artifacts that every project would have to refer to, to reason the created solutions - but every project needs a maximum of freedom how to solve the problem. People are very different how they work. The task might be very different and needs different approaches... I'd be open to having a centralized page for personas and situationas. However, I still believe having a workflow for each topic is key to getting work done. # Tool? With OpenUsabilily, KDE and other free software products, we are working on a tool, that helps us to actually do these things. This tool (User Weave) will be published under an aGPL soonish. My company wil then sponsor the hosting of this tool, so we can easily use it for our purposes, without having to deal with technical issues... So I would be happy if we would use and improve this tool for our needs. What do you think? Possibly. I'd need to know more about the tool to determine whether it would be useful. # Start? We need to start at the beginning. Let's start to work on a common vision for LibreOffice. We will need a small team that conducts a couple of surveys in order to get feedback from the
[libreoffice-design] Resources page and updating what is there
I notice that there is a lot or organizing going. Could someone also note that what is present on the Design Resources page should be re-examined and updated[1]? Some of the designs may need the motif added to them. I am not sure as to what policy you would have re: the use of the motif, but, designs with and without the motif would also be appreciated where it makes sense to do so. The resources page is important to the Marketing team as this is often where we go to get our design resources for use in marketing materials. Thanks to whoever worked on the Design wiki landing page where it mentions the Call for submission for web banners and buttons. Most of all, we are in need of a variety of buttons so that external websites can start promoting LibreOffice. We need to start promoting this even more now that AOO is out. Once the buttons are available we can start promoting the availability on blogs etc., we need to get our brand out there on websites! Cheers Marc [1] http://wiki.documentfoundation.org/Visual_Elements -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-design] Profile picture for G+ page
Hi everyone, we now have a Google+ page which is probably going to be used to announce some of our designs or ask for user input. Facebook basically says 'piss off if you don't have an account' and Twitter might make it harder to follow a conversation between several people. I didn't find a way how to let people comment that aren't logged in, but we can at least present some information that way and link to our mailing list. https://plus.google.com/102673546895803839652/posts I created a preliminary profile picture, if anyone wants something else, please voice your critizism or come up with another design. It'd be nice if we could tick this off pretty fast. Alex -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
