Ubuntu Weekly Newsletter #172

[news 28]

Welcome to the Ubuntu Weekly Newsletter, Issue #172 for the week

December 6th - December 12th, 2009. In this issue we cover: Lucid Alpha

1 released, Call for nominations: Ubuntu Developer Membership Board,

EMEA Regional Membership Board seeking new member, Edubuntu Council

Elections, Ubuntu Women Team - A call for leadership nominations,

Merging ubuntu-sru and motu-sru, New Ubuntu Members: Americas Membership

Board Meeting, LoCo Directory, Introducing The Ubuntu Hour, Ubuntu Hour

Orlando, FL & Salem, NC, Launchpad: Read-only status notification, Phone

interviews about your Launchpad usage, Launchpad: Inline dupe-finding:

an exercise in pain reduction (A call for testing), The Planet: Jono

Bacon, Daniel Holbach, Charles Profitt, & The Ubuntu One Blog, and much

much more!

 

== UWN Translations ==

 

* Note to translators and our readers: We are trying a new way of

linking to our translations pages. Please follow the link below for the

information you need.

 

https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Translations

 

== In This Issue ==

 

* Lucid Alpha 1 released

* Call for nominations: Ubuntu Developer Membership Board

* EMEA Regional Membership Board seeking new member

* Edubuntu Council Elections

* Ubuntu Women Team - A call for leadership nominations

* Merging ubuntu-sru and motu-sru

* New Ubuntu Members: Americas Membership Board Meeting

* Ubuntu Stats

* LoCo Directory

* Introducing The Ubuntu Hour

* Ubuntu Hour Orlando, FL & Salem, NC

* Launchpad: Read-only status notification

* Phone interviews about your Launchpad usage

* Launchpad: Inline dupe-finding: an exercise in pain reduction (A call

for testing)

* The Planet: Jono Bacon, Daniel Holbach, Charles Profitt, & The Ubuntu

One Blog

* In the Press & Blogosphere

* Upcoming Meetings & Events

* Updates & Security

 

== General Community News ==

 

=== Lucid Alpha 1 released ===

 

Welcome to Lucid Lynx Alpha 1, which will in time become Ubuntu 10.04 LTS.

 

Pre-releases of Lucid are *not* encouraged for anyone needing a stable

system or anyone who is not comfortable running into occasional, even

frequent breakage. They are, however, recommended for Ubuntu developers

and those who want to help in testing, reporting, and fixing bugs.

 

Alpha 1 is the first in a series of milestone CD images that will be

released throughout the Lucid development cycle. The Alpha images are

known to be reasonably free of showstopper CD build or installer bugs,

while representing a very recent snapshot of Lucid. You can download it

here:

 

* http://cdimage.ubuntu.com/releases/lucid/alpha-1/ (Ubuntu)

* http://uec-images.ubuntu.com/releases/lucid/alpha-1/ (Ubuntu Server

for UEC and EC2)

* http://cdimage.ubuntu.com/ports/releases/lucid/alpha-1/ (Ubuntu ARM)

* http://cdimage.ubuntu.com/kubuntu/releases/lucid/alpha-1/ (Kubuntu)

* http://cdimage.ubuntu.com/xubuntu/releases/lucid/alpha-1/ (Xubuntu)

 

See http://wiki.ubuntu.com/Mirrors for a list of mirrors.

 

Alpha 1 includes a number of software updates that are ready for wider

testing. Please refer to http://www.ubuntu.com/testing/lucid/alpha1 for

information on changes in Ubuntu.

 

This is quite an early set of images, so you should expect some bugs.

For a list of known bugs (that you don't need to report if you

encounter), please see: http://www.ubuntu.com/testing/lucid/alpha1

 

https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-December/000651.html

 

=== Call for nominations: Ubuntu Developer Membership Board ===

 

Earlier this year, the Technical Board agreed to establish a Developer

Membership Board (DMB) with responsibility for approving new Ubuntu

developers and granting them the appropriate privileges in Launchpad.

 

Previously, this had been the responsibility of the Technical Board

itself. For various reasons, it was prudent to separate this function

into its own governance board, for example:

 

* The Technical Board had been responsible for new core developer

applications, while the MOTU Council was responsible for new MOTU

applications. This was confusing for applicants, as the two groups

evolved different processes, and doesn’t make as much sense in the

context of the reorganization of developer privileges. The DMB will be a

central governing body for all developers, regardless of which teams

they contribute to.

* The Technical Board would prefer to conduct all of its discussions in

public, while DMB may have cause for private deliberation. This means