Tasks from daily community roundtable sessions

Based on feedback from the Ubuntu Community Survey (http://www.jonobacon.org/2011/10/24/ubuntu-community-survey-results/), the community get really motivated by seeing their contributions acknowledged and users thanking them because of them. This session is to discuss how we can improve this in the community.

We want to start building a support community around application development topics and start promoting the resources we're going to use for that: - The ubuntu-app-devel mailing list - Askubuntu - ...

Discussion about how we build experiences in Ubuntu from the design to implementation level.

Goals for the Ubuntu Women UDS-P cycle Add your ideas here for consideration in this formal blueprint: http://wiki.ubuntu-women.org/Roadmap-P

Translations roundtable discussion where to fit all other topics not covered in dedicated sessions

Informational Sessions

This will detail the plan for the Council for loco teams, approval, any new guidance pages to be written, goals to help get locoteams more involved in the community

Need to ensure that 100% of the "Desktop" is translated into Chinese/Simplified for the LTS release

The usual. :)

Harvest hasn't seen much development recently, but we still need a good place to summarise all the needed work in the distribution. Problems both in representation and data should be discussed.

Informational Session

Tuesday roundtable

Meet with the Ubuntu desktop designers, hear what they love about Ubuntu, what they'd like to do better, and what they dream about.

We want to discuss the plans to start growing an Ubuntu app developer community

Ask Ubuntu is an up-and-coming source of for Q&A in the Ubuntu Community - lets figure out how to integrate it into the community at large!

It'd be worth to discuss the list of open issues of our developer documentation and review the results of the recent survey.

Grow this site

We want to build upon the current resources section of the app developer site and develop it to become a point of reference for anyone developing applications for Ubuntu. Some ideas for discussion: - Review of the current IA - Compare how other developer sites structure their resources/reference sections - Feedback on the current content and structure of the current section

Wednesday

Review ARB activity, and plan for the next cycle. Introducing new members.

How to use Ask Ubuntu More effectively - show the experts in the field; the kind of people we want participating more often, how they can use the site to help answer everyday user questions

Discussion and action items coming from UDS-P for the direction and development of the LoCo Team Portal during the "P" Cycle This to discuss: Bug #878593

Discussion during UDS-P on the further plans and development for summit.ubuntu.com Discussion Items:  * Header links and navigation, currently too many links in the header  * Setting up summit to run concurrent summits allowing for the removal of the Linaro hard coding All items which were not completed last cycle have been added to this list.

We'd like the tutorials section of the app developer site to grow with interesting content for Ubuntu app developers. In this session we'll discuss and come up with a plan to do that. Ideas: - Brainstorming of topics where we need tutorials - Structure the list of topics in a shortlist of essential ones - Reach out to the community to assign at least one person to a tutorial - Set up editorial permissions and process in place on the app developer site

Based on the results of the Ubuntu Community Survey (http://www.jonobacon.org/2011/10/24/ubuntu-community-survey-results/) a common area of de-motivation is with community members often bickering about Ubuntu and it's focus and direction. Many felt like this was frustrating because many of those who bicker contribute little.

Jay's plenary, but as a session

The goals for the Accessibility Team community for the Precise cycle. Please add items for discussion to the whiteboard!

Discussion about Ubuntu on phones.

Goals for the UDS-P cycle to help the Ubuntu Leadership Team establish relationships with formal Ubuntu Leadership Councils, Boards, and leaders throughout the community in a effort to provide resources for mentoring new leadership and encourage and motivate current leadership to become even more effective and efficient.

A review of past activity and future plans for the Ubuntu-Hams team. Open to all amateur radio operators and anyone else who is interested.

Grow the contributions of community submitted charms for juju

Thursday

We have a weekly development update already, so it can serve as a good piece of news infrastructure. We need to put the project on broader feet and figure out submissions processes, etc. Also are we going to talk about new interesting news bits we might want to include.

Just a brain dump of some of the ideas we discussed so far:  - LTS release  - Improve LTSP live  - Re-base installer step on current LTSP live  - Fix package selection to work with all locales  - Add directory integration step  - Refresh artwork  - Switch away from iTalc  - Get Wubi working  - Upgrade website to Drupal 7 - Migrating to dh_python2 for everything on the DVD

Executive Summary: The main idea is to make discovery of Ubuntu community automatic, and not an accident. Community is meant in the whole and general sense of "anyone who uses or contributes to Ubuntu." Problem Statement: "Houston we have a problem." Most people who have discovered Ubuntu community have done so accidentally. Most people (who are on the other side of the chasm) have no idea that community is central to the growth and development of Ubuntu. Most people have no idea whether others in their town/city are using Ubuntu. We need to make community obvious and make community formation easy. Proposal: One possible solution is to create a "Community Lens" or (similarly obvious desktop element). Make it prominent. Connect it to one's local community, beginning with those who use and enjoy Ubuntu in our town/city. Over time, expand it to include additional nearby non-Ubuntu social connections: family, friends, neighbourhood, city...

How are we going to manage community submitted charms? Peer review? etc.

This will detail the plan for the Council for loco teams, approval, any new guidance pages to be written, goals to help get locoteams more involved in the community

Addressing concerns from community members about (lack of) involvement in user experience and design, and concern from designers that they only have time to work on a tiny fraction of the Ubuntu user experience (in the shell). Exploring practical steps we can take, so interests get paired to tasks, and the whole user experience of the distro is improved.

There is a huge interest in getting involved in Ubuntu development. We want to better reach out to everybody who is interested. The recent survey data will probably help with the discussion of this.

We'll review the activities about LoCo Testing, with the results from the Italian Team, and the Laptop testing project. We'll also discuss about the an idea in the Italian LoCo about a Triage Team with mentoring in native language and team's adoption.

Friday

Translations roundtable discussion where to fit all other topics not covered in dedicated sessions

Discuss ideas to improve the community understanding of bug reporting and triage.

Charm authors will need first class documentation to write charms

The Ubuntu Translations Portal was created at the end of the Natty cycle: https://blueprints.launchpad.net/ubuntu/+spec/ubuntutheproject-community-n-translations-portal On the Oneiric cycle work on other projects has put proomoting and using the portal on hold, but this cycle we'd like to relaunch it with more content useful to Ubuntu translators.

This session is to discuss how we plan work for an Ubuntu Accomplishments specification.

How can we get better at celebrating contributions to Ubuntu development? There is massive amounts of great work going into Ubuntu, some of this is under the radar because it is less visible. Celebrating this more publicly would be both inspiring for those who did the good work, and others who didn't know about the great work before.

As opposed to having fully-fledged 1-on-1 mentoring, we might want to think of a much more light-weight approach and coordinate efforts such as: 1) reach out to new contributors, thank them for their work and get feedback, 2) reach out to people who might be ready to apply for upload rights and help them, 3) reach out to contributors that went inactive and get feedback from them and offer help. This should be easily manageable by a small team and would make the developer world a much more social experience.

Open Week, Developer Week, Application Developer Week, User Days

During the Oneiric cycle a set of tools to create localized ISOs were developed. We'd like to expand on those tools, get some community feedback and a wider adoption of those tools to create ISOs adapted to a particular region. This will be a community-based effort, and to kick it off we'll need to: - Create a policy for these images: -- What can be changed and what cannot -- Where should the images be published -- How can the images be tested - Create documentation on how to build these images - Create documentation on how to test them In this session we'll discuss and elaborate on this topics to come up with a clear plan on how the community can create localized ISO images

If we are to grow Ubuntu's user base by a factor of 10, we need to look at ways to scale the community. Community growth is a key to taking Ubuntu to people who have never seen it or heard of it. Here's one powerful way to scale: Build local communities at a town/city level. Make Ubuntu more of an in-person phenomenon, and less of a virtual one. We should gather and discuss how to make this happen, as well as any other thoughts for scaling.

We built a great tool, let's tell the world!

Goals for improving the News Team over all, clean up documentation for UWN and Fridge, as well as update Front Page for Fridge and Branding efforts.

Dealing with Ubuntu and governments