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 - ...

Q&A / BoF on Qt Project governance, community, contributions, state of the project, etc.

Shows we're hitting up.

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

This specification is to plan the work of the Ubuntu Accomplishments releases over the coming release cycle. Goals discussed so far include: * Maturing our API. you can see a list of these goals at https://wiki.ubuntu.com/Accomplishments/NewAPI * Getting Local Accomplishments support to a level of quality that matches Global Accomplishments. * Expanding our help and guidance for how to get started using the system. Please join the session, particularly if you are interested in contributing to the project.

The Packaging Guide has seen a lot of changes and improvements of the past few cycles. Let's keep this momentum going and discuss next steps.

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

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.

We should review all our charm processes and make sure they are low-barrier. We also need to figure out github integration.

Started during the P cycle, the Developer Advisory Team has been reaching to development contributors and while things have worked out quite well, there are surely things we can improve. https://wiki.ubuntu.com/DeveloperAdvisoryTeam Agenda: - team meetings - outreach - improve feedback collection process - get notified about contributor status changes (active→inactive, new→experienced) - following up with contributors who don't reply - avoiding trello craziness

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

Growing the amount of charms in the charm store

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

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.

This session is designed to discuss which accomplishments we want to focus on for the forthcoming cycle to expand the Ubuntu Community Accomplishments collection.

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.

A roundtable to discuss any issues, improvements, ideas around the Ubuntu Translations community

Things to accomplish for this cycle

As ever

Tasks from daily community roundtable sessions

a discussion of where we are at and what the major work items are for the Q cycle including operator recruitment IRCC council member election

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

Our usual Edubuntu session to discuss the plans for the next 6 months. Please note that this time around a separate session has been booked for LTSP (foundations-q-ltsp)

Reviewing and discussing all the feedback we've received on the CoC V 2

Charms Schools, webinars, and IRC, oh my!

The Stack Overflow affiliated website Askubuntu.com has yielded volumes of user information and valuable direct community involvement. It's likely worth the effort to pay special attention to this resource particularly with upcoming future challanges requiring informing of users confused by Unity, trying out Ubuntu TV or server cloud features, or installing Ubuntu on a tablet device, for example. Discussion will likely involve new concepts to better serve question askers and answer providers alike. Automation of question keyword filtering and responsible person notification, search machine optimization, topic separation according to UX, application development, and API enrichment are subtopic candidates.

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

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

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

We'll talk about amateur radio, and promoting Ubuntu-hams. In particular, there is interest in using gnuradio with some of the TV receiver USB dongles which are supported.

Easy docs and stuff for people

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!

Building upon the foundations of the initial Ubuntu App Developer site, we'd like to expand it on a second design phase. Depending on the resource allocation from design, the scope might be reduced, so this blueprint is also to discuss the incremental improvements that can make a substantial impact and that we can work on next cycle.

We reach out to potential new Ubuntu Developers in a number of ways. We have the weekly Developer update, public Hangouts, Ubuntu Developer Week, announcement of initiatives, interviews and other bits. Let's plan how we approach new contributors this cycle.

A lot of our development processes involve a review or approval step. Let's review how we've done in the P release and see what we can improve for Q.

Planning what the Accessibility Community Team is going to do for the next cycle. We were over ambitious last cycle, so it's time to pare down and look at what's realistic for this next cycle.

Review of the Precise cycle and brainstorming on how to improve.

The Ubuntu Youth team has been dead for a few years. It was a place where youth people can find others from their ages, and discuss about Ubuntu and what can they do about it. My intention with this session would be to find ways to revive this group, and also to define this group purpose and main vision for now on. Also, discussing how to promote it, how its leadership is going to be taken (Point for Philip Ballew, current Team leader) and how to give it an useful position in the community are points that are important to be taken care of during this session.

In the past we have had great interest from new contributors in getting involved through organised initiatives. Both clarity in instructions and a clear set of targets have helped a lot here. In the session we should discuss possible targets for bug fixing initiatives, who can help and set up an initial schedule.

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