Ubuntu EMEA Regional Membership Board seeking new member

The Ubuntu EMEA Regional Membership Board (EMEA RMB) is seeking an
additional Ubuntu community member to join as a member of the board. More details about the RMB can be found at the following links:

Regional Boards Membership Wiki
Regional Boards EMEA Wiki
EMEA Membership Board Launchpad

The Regional Membership Boards are responsible for considering Ubuntu member applications and do this via a regular public meeting held on IRC. Ideally the candidate should reside in an timezone which is conducive to attending one hour online meetings which are typically held at around 20:00 UTC, and can commit to attending those meetings wherever possible.

The EMEA RMB will collate nominations and pass the list (in full) to the Community Council who will select one person from the list supplied. The plan looks like this:-

* Nominations open with this mail on 10th December 2009
* Nominations close on 17th December 2009
* EMEA RMB to collate nominees and pass to the Community Council by
24th December
* Community Council to select from above pool and announce accordingly

If you are an Ubuntu member and are interested in joining the EMEA RMB, or know someone else who is an existing member and might be suitable, please drop an email to the board at the following address: EMEA mailing list

Note: This is a private mailing list so your mail will be held in moderation, and you may be notified of this via a reply. We will approve all nomination mails to the list.

Please pass this notification on to your teams.

Many thanks,
For the Community Council and EMEA Regional Membership Board

Unified SRU policy and team for main/universe

Attention Ubuntu developers! During the course of general archive re-organization, and a recent (short) discussion on ubuntu-devel@ [1] and on IRC, the SRU teams for main (ubuntu-sru) and universe (motu-sru) have now joined together in: ubuntu-sru

This now means that any member can review/approve/reject any SRU request. However, only the archive administrators amongst the team members can actually press the buttons to accept uploads, but that’s the smallest part of SRU review really.

The policy was already updated a while ago to uniquely apply to the entire archive: Stable Release Updates

In particular, you now should just subscribe “ubuntu-sru” to all SRU requests. “motu-sru” will still work, since ubuntu-sru is now the sole member of motu-sru, but its usage should be phased out.

[1] ubuntu-devel mailing list archive.

Launchpad Read Only Notification

Launchpad’s web interface will be read-only for one hour from 22.00 UTC on Wednesday the 16th December 2009 for the release of Launchpad 3.1.12. During that time, other services, including PPAs, code hosting and the email interface, will be offline.

Starts: 22.00 UTC 16th December
Expected back: 23.00 UTC 16th December

This is the final Launchpad code release of 2009! We’ll post the 2010 release calendar to the Launchpad blog in the next few days: Launchpad Blog

Follow Launchpad’s official status feed for full status information:Launchpad Status

Edubuntu Council Elections

Recently, the current Edubuntu Council announced the Edubuntu Council nominations and elections. The nomination round has been completed and even though later than originally anticipated, the voting will soon commence.

6 polls have been set up on Launchpad. Each poll has two choices, “yes” and “no”. The poll starts at 01:00:00 UTC (around 12 hours from now) on 11th December 2009 and runs for 7 days.

Poll Links:

If you have any questions, feel free to contact the current Edubuntu Council on the edubuntu-devel mailing list.

Originally sent to the ubuntu-news-team mailing list by Jonathan Carter on Thu Dec 10 12:17:03 GMT 2009

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 that the TB mailing list can be public now.
  • The TB had difficulty keeping up with applications in addition to serving its other functions. In particular, TB meetings were difficult to keep on schedule.

Now that the DMB is formally established and active, we would like to hold an election to determine its membership. Until now, the members of the Technical Board have been standing in to fulfill the functions of the DMB.

Because the DMB comprises the functions previously served by the Technical Board and the MOTU Council, the current members of those teams are automatically nominated. Any members of the Technical Board or MOTU Council who *do not* wish to stand for election to the DMB will need to explicitly decline the nomination.

This is an open election, so anyone else may be nominated as well. Candidates should be well qualified to evaluate prospective Ubuntu developers and decide when to entrust them with developer privileges.

There will be a total of 7 seats on the board, chosen by Condorcet voting, similar to the Technical Board election earlier this year.

Nominations should be sent to developer-membership-board@lists.ubuntu.com.

[Discuss the Ubuntu DBM Call for nominations on the Forum]

Originally posted by Matt Zimmerman here on 8 December, 2009 at 19:04