Difference between revisions of "Lutz Hoeger"
Lutz Hoeger (Talk | contribs) m |
Lutz Hoeger (Talk | contribs) m |
||
| Line 2: | Line 2: | ||
==On our way to build up a vibrant User Experience community== | ==On our way to build up a vibrant User Experience community== | ||
| − | Sun's StarOffice User Experience (UX) team is about to evolve into an OOo UX | + | Sun's '''StarOffice User Experience''' (UX) team is about to evolve into an '''OOo UX community'''. Some small steps already have been taken ([http://specs.openoffice.org/ feature specifications], [http://wiki.services.openoffice.org/wiki/User_Experience_Community#Guidelines guidelines], etc.), but these are all rather dispersed, and the '''"glue" is still missing'''. Even more important, so far this is a Sun-only activity, and the '''community''' hasn't been involved yet. |
| − | That's why Stefan Taxhet and I met to discuss steps towards founding or becoming part of an OOo UX | + | That's why Stefan Taxhet and I met to discuss '''steps''' towards founding or becoming part of an OOo UX community. We didn't finish, and I would like to '''open the discussion''' at this point, to get broader feedback and to involve more people. |
| − | When thinking about these steps, I am always keen to know, how | + | When thinking about these steps, I am always keen to know, how we can find out if any of the steps is successful, how we can '''measure success'''. Also, I would like to '''distinguish''' between steps that lead to '''real contributions''' vs. steps that '''just generate "activity"''' but do not contribute directly to the product or project OOo. With '''contributions''', I do not refer to code contributions, but to anything that the Sun '''UX team contributes to the normal development process''' of StarOffice (specs, competitive analyses, usability tests, ...; see [[User Experience Community here]]). |
Revision as of 14:11, 19 October 2006
On our way to build up a vibrant User Experience community
Sun's StarOffice User Experience (UX) team is about to evolve into an OOo UX community. Some small steps already have been taken (feature specifications, guidelines, etc.), but these are all rather dispersed, and the "glue" is still missing. Even more important, so far this is a Sun-only activity, and the community hasn't been involved yet.
That's why Stefan Taxhet and I met to discuss steps towards founding or becoming part of an OOo UX community. We didn't finish, and I would like to open the discussion at this point, to get broader feedback and to involve more people.
When thinking about these steps, I am always keen to know, how we can find out if any of the steps is successful, how we can measure success. Also, I would like to distinguish between steps that lead to real contributions vs. steps that just generate "activity" but do not contribute directly to the product or project OOo. With contributions, I do not refer to code contributions, but to anything that the Sun UX team contributes to the normal development process of StarOffice (specs, competitive analyses, usability tests, ...; see User Experience Community here).
