Tasks from daily community roundtable sessions

As part of the work on the LoCo portal this cycle, we'd like to review the current content in terms of the information we present to newcomers to the site, and ensure the core message of the site and all relevant documentation is up to date. In short, we want to ensure that the LoCo portal has prominent additional sections with brief and visually rich information on: - What a LoCo team is - How to join a LoCo team - ...

A "tablet test-drive" session to encourage Ubuntu-related tablet (and touch screen) development: multiple tablets will be on hand running the following UIs: - Ubuntu / Unity - Ubuntu / Gnome - Kubuntu Active (KDE Plasma Active UI) - WeTab (MeeGo base OS) - Android - Windows 8 We'll set tablets side-by-side and let developers try them: the idea would be to compare and contrast the various tablet UIs to spur (and, hopefully, accelerate) innovation in Ubuntu's tablet OS.

Identify tutorials and documentation needed by upstream developers to port and integrate their applications with Ubuntu and Unity

Promote and run a successful series of online app developer events, including at least: - The Ubuntu App Developer Week - The Ubuntu App Developer Contest

Tasks from daily community roundtable sessions

We want to increase the visibility and awareness of Ubuntu app development outside of the regular Ubuntu channels. This blueprint will serve to discuss initiatives and plan an external outreach campaign. One of the first initiatives will be a series of articles published to a set of targetted media sites or print publications not directly associated with Ubuntu.

Identify which APIs need to be documented for application developers and ways in which we can provide these APIs in a developer friendly way

Plans for the software-center server

Mozilla SUMO is the product that powers support.mozilla.org and we are aiming to transition help.ubuntu.com in its entirety to SUMO in the Q-Cycle or at the very least get excellent work done towards that goal.

The Ubuntu archive administration team has always required direct privileged shell access to the ftpmaster system in order to perform many of its routine tasks. This is a security problem, it prevents us from opening some tasks up to those who are not Canonical employees, and it makes it hard for us to improve our own tools. Improve the Launchpad API to handle all our requirements and write suitable API clients. We will know we have succeeded when archive admins no longer require shell access to do their jobs.

Get more app developers talking about Ubuntu and targeting Ubuntu. Promote Ubuntu as a platform in the places independent app developers socialize.

The App Review Board and its processes were put in place 1.5 years ago. It's time to review how policies and requirements have been working out for us. Daniel H put together some discussion about a key point of these policise, the /opt requirement, at https://wiki.ubuntu.com/OptRequirement which can provide a basis for the discussion

Tasks from daily community roundtable sessions

A change I'd like to make for 12.10 is to use a compositor to control video from boot to shutdown. This gives us the following benefits: - We can have smooth transitions from the splash screen to the greeter to the session and back again - We don't use VT switching anymore which has been shown to be problematic - We use one consistent monitor layout for all stages of the boot - We can use the greeter as the lock screen (couldn't get it to work this cycle for the above reasons) - We can ensure that you can never accidentally switch to a locked session - We can show the greeter while the session loads The technology used will probably be Wayland, and in some ways this change is to implement the Wayland Tech Preview that was proposed for Precise [1]. Note that not all video drivers will support this, and we will continue to support the current system for those that do not support it (primarily the nvidia driver). [1] https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-wayland-tech-preview

Discussion during UDS-Q on the further plans and development for summit.ubuntu.com

Identify and engage targetted upstreams to submit their apps to the Ubuntu Software Centre

With lots of work put into https://myapps.developer.ubuntu.com/ it should be interesting to review MyApps from the ARB perspective and see if there are small tweaks which would speed up the review of free apps.

We want to make the Ubuntu LoCo portal a hub for social LoCo activities. This blueprint proposes the redesign of the portal's homepage to more effectively showcase LoCo team activity and to inspire community members.

Review the processes & how the ARB team is doing.

Tasks from daily community roundtable sessions

Review the existing Unity developer documentation, identify areas for improvement

Identify ways to involve community in the design and implementation of the Ubuntu TV project

Provide support and mentoring resources for upstream app developers who want to port or integrate their application with Ubuntu and Unity

Since Mark Shuttleworth's writings of Ubuntu on mobile devices [1] there will be more and more interest expressed in what hardware is most useful and which software components lead to wh at user experience. This blueprint serves to measure the progress of Ubuntu development toward mobile use cases. Anything concrete can be included in a test plan, otherwise discussion likely involves sharing of knowlege and new ideas. For example, regarding the 'magick rotation' software, just how stable is it and relevant will it continue to be? What are the most important features of Ubuntu on Android and how is this part of the larger goal towards mobility? Being that UDS includes 'Desktop' and 'Server' tracks but nothing relating to mobility, this blueprint best fits between 'Design' and 'Other.' [1] http://www.markshuttleworth.com/archives/820

Mark Shuttleworth announced (a while ago for 11.04) that Canonical would leverage Qt more, and subs equently Qt is found in important parts of Ubuntu like Ubuntu One. Being a relatively new kid on the block, Unity has its work cut out for outreach to existing developers of both Qt and Gnome/Gtk+ interfaces. Without coordination and documentation the advantages of this delicate balance of legacy interface development and ermerging Unity technology are lost. In simple terms, this blueprint serves to consider and unify developers' goals and ideas concerning Unity and legacy Qt and Gnome/Gtk+ bindings. Deliverables could include a wiki page for easy to understand development information applicable to both APIs.

taking the successes on juju to use the hud to search and find computing tasks. users could open the hub, and using natural language, type a question or describe a problem and an appropriate juju "charmling" will help the user solve the problem without the need for appreciable computer knowledge. this would use heuristics to determine possible solutions, choose the most likely correct "charmling", and assist the user. use cases could extend to any desktop usage, including very complex tasks requiring multiple steps and settings. examples might include: * fix a broken wireless connection * install packages * add a printer * connect to a print server for example, a user needs to add a printer. the user would open the hud and type, "how do i add a printer?". heuristics would determine the most probably answer, and start the "charmling" which would open an informational dialogue box telling the user, "The printer dialogue box is being opened. You probably want to select the "+ Add" button" and then opens the printer dialogue box. another example might be a user wanting to create a pdf. user opens the hud, types the question, heuristics are employed, and "charmling" is deployed which opens up a sane tutorial with examples.

Tasks from daily community roundtable sessions

Promote the availability of new apps in the Software Center, both in USC itself and through other channels, to raise awareness of apps targeting Ubuntu

Review the current process and identify which parts of the documentation need to be improved. Also figure out what specifically we expect from upstreams and which help the ARB can provide.

Here we go again!

Etherpad Lite is the future of etherpad, it has a neat integration API, lets look at how tightly we can integrate it wiht summit for single sign on, pad creation and pad content management