1
edit
Changes
→Open Communities in Own Project
==== Product & User Experience Design in Open Communities ====
Mike Beltzner's presentation was focused on products and the user's experience with those products in an open community context. He essentially summed it up with his three “maxims”. The first being listening to your community which is basically focusing on what the community wants or needs. His second maxim was leading your community which is essentially to provide organization and structure to direct contributions from the community. Utilizing small focused teams is another approach to leading your community. Mike's final maxim is to allow the community to play and experiment with the product. Community feedback is extremely useful to ensure a higher quality of software. He also pointed out how Microsoft was making an effort to gather user's experience with their products by highlighting the “Happy face” and “Frown face” icons that appear in the task bar. Mike's presentation was filled useful information about relatively new software such as CoScripter and TheCoop. His presentation successfully influence me enough to give these products a run and see what the hype is about. I'm happy to say that I found the experience very enlightening.
===== Background & Point of View (M.Beltzner) Open Communities in Own Project =====Since my own project involves working with an existing localization community I knew that Mike Beltzner 's presentation would give me more insight into how to work with them. The community in my own project is responsible for the experience anyone gets when they touch anything related to Firefoxrelatively large and is being led by a few Mozilla employees. They have been leading us with structure and organization by providing us with scripts, such as the websitetools, the add-on site or anything else related contacts and possible approaches to Mozillareaching our main goals and objectives. Before I get to In addition, we have also been following Mike's views on open sourcefirst maxim, listen to your community, I feel compelled by adding and removing features according to mention that Mike was probably one of what we believe the most colorful characters I had community would want as well as their direct input through tools such as Bugzilla. Throughout the fortune development of seeing during the FSOSS eventour project, we tried to keep our tool simple and not overly complex to use. Mike's view on open source is We knew that if you are working on an open source project and you take we made a complex tool, the time to listen to your community, lead your community, would simply reject it and allow the community to experiment project would not progress any further in the future. With the help of Mozilla's Axel Hecht and Michal Berman (deeply involved in localization) and support from our professors Dave Humphrey and Chris Tyler - who have helped us considerably by providing us with your product, that your final product will be of high value strong guidance and quality because it has contacts - we have been embraced by able to get our project off the ground and have built the foundation for a tool that the open source communitycan put to good use in the near future. Mike We have also emphasized how had a small taste of the some negative things from the open source community . To put it briefly, our project is chaotic somewhat dependent on scripts and tools already built by Mozilla's localization team as well as the surrounding community. Axel Hecht had recommended that we use a priority for any open source project should be particular script to bring order to that chaos and to take advantage of that community when it is acting more like help with a “chorus”specific aspect in our system. Mike sees the advantages of gathering user data For nearly a month and how building a community around a product is half we tried to get in contact with the most effective way of sustaining script's owner for information regarding the product over Python script. We finally got in touch - through Bugzilla - and are in the long-termprocess of incorporating their tools with our new tool as recommended by Mozilla's localization team.
===== Open Communities in Own Project =====
Since I my own project involves working with an existing localization community I knew that Mike's presentation would give me more insight into how to work with them. The community in my own project is relatively large and is being led by a few Mozilla employees. They have been leading us with structure and organization by providing us with scripts, tools, contacts and possible approaches to reaching our main goals and objectives. Conversely, we have also been following Mike's first maxim, listen to your community, by adding and removing features according to what we believe the community would want. Throughout the development of our project, we tried to keep our tool simple and not overly complex to use. We knew that if we made a complex tool, the community would reject it and the project would not progress any further in the future. With the help of Mozilla's Axel Hecht and Michal Berman (localization) and support from our professors Dave Humphrey and Chris Tyler - who have helped us considerably by providing us with considerable guidance and contacts - we have been able to get our project off the ground and have built the foundation for a tool that the community can put to good use in the near future.
