From Fedora Project Wiki

< FWN‎ | Beats

Line 9: Line 9:
  
 
===Breaking News of the Week===
 
===Breaking News of the Week===
====[Guidelines Change] Changes to the Packaging Guidelines==== 
 
Tom Callaway<ref>tcallawa at redhat.com</ref> on Thu Apr 12 20:57:29 UTC 2012 announced<ref>lists.fedoraproject.org/pipermail/announce/2012-April/003057.html</ref>,
 
  
"A bundling exception for boost within Passenger was granted, due to the
+
====New FAmSCo election guidelines==== 
intrusive nature of the forked changes, the efforts of the maintainer to
+
Christoph Wickert<ref>christoph.wickert at googlemail.com</ref> on Thu Apr 26 11:19:10 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003063.html</ref>,
merge as many of them as possible into the upstream boost source tree,
 
and the visible efforts of the upstream to keep the bundled copy of
 
boost in sync with the current boost releases.
 
  
The package must also include a Requires: bundled(boost) = $VERSION
+
"after months of - sometimes controversial - discussion I am am happy to
where $VERSION is the boost version being bundled.
+
announce the new FAmSCo election guidelines <ref>https://fedoraproject.org/wiki/FAmSCo_election_rules</ref>. For those of you, who
 +
did not follow the discussion, here is a brief summary of the three most
 +
important changes:
  
<ref>https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_granted_exceptions</ref>
+
=====More continuity=====
 +
Instead of electing all seats once a year, we follow the example of the
 +
Fedora Board and FESCo and elect half of the committee every 6 months or
 +
with every release of Fedora.  FAmSCo will not change over sudden and
 +
new members can easily catch up with their new duties by learning from
 +
others.
  
Packages which have SysV initscripts that contain 'non-standard service
+
=====Easier filling of vacant seats=====
commands' (commands besides start, stop, reload, restart, or
+
Every committee is in danger of members becoming inactive.  This can
try-restart) must convert those commands into standalone helper scripts.
+
happen to all of us for various reasons such as our dayjobs or personal
Systemd does not support non-standard unit commands.
+
problems.  Under the old guidelines  <ref>https://fedoraproject.org/w/index.php?title=FAmSCo_election_rules&oldid=269322  </ref>, we had to wait until only 3
 +
members left - even with 2 left the committee is hardly operational -
 +
and then call a supplementary election - which never happened even
 +
though we had only 4 active members. Now we are filling vacant seat
 +
when necessary, either with runner-up candidates from the previous
 +
elections or by appointing new members.
  
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Unit_Files</ref>
+
=====Wider electorate=====
 +
The ambassadors represent the whole Fedora Project, this is why now not
 +
only ambassadors are eligible to vote for FAmSCo, but everybody who has
 +
signed the Contributors License Agreement and is member of (at least)
 +
one other group in the Fedora Account System (FAS) is allowed to vote.
 +
This will not only strengthen FAmSCo's position but also help candidates
 +
who are active in other groups of the Fedora project.
  
A section was added to the systemd Packaging Guidelines page with a link
+
Last but not least the guidelines have been massively cleaned up.
to the Tmpfiles.d Packaging Guidelines page, since systemd uses Tmpfiles.d.
 
  
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Tmpfiles.d</ref>
+
We think that the new guidelines are a big improvement and want them to
 +
come into effect as soon as possible. Therefor we will have a special
 +
election for Fedora 18 (the next regular elections were scheduled for
 +
F19).  All 7 seats in FAmSCo are open for election.  In order to make
 +
the transition to the new alternating terms, the top 4 vote-getters will
 +
serve 2 Fedora releases, the bottom 3 will have to run for re-election
 +
after one release.
  
The Ruby Packaging Guidelines were almost completely rewritten. If you
+
More about the upcoming ambassadors elections to come later this week as
maintain ruby packages in Fedora, we advise that you review the new
+
part of the general Fedora 18 elections announcement. Please help us
guidelines.
+
getting a better, stronger and more active FAmSCo by casting your votes.
  
<ref>https://fedoraproject.org/wiki/Packaging:Ruby</ref>
+
If you have feedback or questions, please don't hesitate to ask. We are
 
+
looking for your input on the Fedora ambassadors mailing list<ref>https://admin.fedoraproject.org/mailman/listinfo/ambassadors</ref>."
An informational note about Software Collection macros in Fedora
 
Packages was added:
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macros</ref>
 
 
 
The guidelines relating to PIE and Hardened Packages were updated. Now,
 
if your package meets the following critera you MUST enable the PIE
 
compiler flags:
 
 
 
* Your package is long running. This means it's likely to be started and
 
keep running until the machine is rebooted, not start on demand and quit
 
on idle.
 
 
 
* Your package has suid binaries, or binaries with capabilities.
 
 
 
* Your package runs as root.
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#PIE</ref>
 
 
 
Rules involving appropriate scripting within Fedora Package spec files
 
were added to the Guidelines:
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Scripting_inside_of_spec_files</ref>
 
 
 
The section in the systemd guidelines covering EnvironmentFiles and
 
support for /etc/sysconfig files was revised for clarification.
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#EnvironmentFiles_and_support_for_.2Fetc.2Fsysconfig_files</ref>
 
 
 
The Ada Packaging Guidelines were updated for new rules on packaging
 
source files and updated macros.
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Ada</ref>
 
 
 
The section of the Packaging Guidelines describing the "bootstrapping"
 
binary exception was amended for clarification:
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions</ref>
 
 
 
The section of the Packaging Guidelines describing Duplication of system
 
libraries was amended to clarify the exceptions for Javascript and
 
parallel stacks.
 
 
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries</ref>
 
 
 
These guidelines (and changes) were approved by the Fedora Packaging
 
Committee (FPC).
 
 
 
Many thanks to Kevin Fenzi, Bohuslav Kabrda, Brett Lentz, Marcela
 
Mašláňová, Bill Nottingham, Vít Ondruch, Mamoru Tasaka, and all of the
 
members of the FPC, for assisting in drafting, refining, and passing
 
these guidelines.
 
 
 
As a reminder: The Fedora Packaging Guidelines are living documents! If
 
you find something missing, incorrect, or in need of revision, you can
 
suggest a draft change. The procedure for this is documented here:
 
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
 
 
 
Thanks"
 
  
 
<references/>
 
<references/>
  
====Announcing the release of Fedora 18 Beta!====   
+
====Fedora Elections: General information, and questionnaire opening.====   
Dennis Gilmore<ref>dennis at ausil.us</ref> on Tue Apr 17 14:17:02 UTC 2012 announced in two thread<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003058.html</ref><ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003059.html</ref>,
+
Robyn Bergeron-Fedora Project Leader<ref>rbergero at redhat.com</ref> on Fri Apr 27 11:52:50 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003065.html</ref>,
 
 
"Look, up in the sky! It's a bird, it's a plane, it's... the Beta
 
release of Beefy Miracle! Flying 'round the world at the speed of the
 
intertubes, delivering progress, mustard, and freedom to the masses.
 
 
 
We are delighted to announce the availability of the Beta release of
 
Fedora 17.  Want to get a taste of the future?  Download it now:
 
 
 
<ref>http://fedoraproject.org/get-prerelease</ref>
 
 
 
===== What is the Beta Release? =====
 
 
 
The Beta release is the last important milestone of Fedora 17.  Only
 
critical bug fixes will be pushed as updates leading to the general
 
release of Fedora 17 in May. We invite you to join us in making Fedora
 
17 a solid release by downloading, testing, and providing your valuable
 
feedback.
 
  
Of course, this is a beta release, meaning that some problems may still
+
"It is once again time for election season to begin.  As noted in the
be lurking. A list of the problems we already know about is found at
+
elections schedule<ref>http://fedoraproject.org/wiki/Elections#Committee_Elections_Schedule</ref>, the elections questionnaire is now open to
the Common F17 bugs page, seen here:
+
populate with questions for candidates, and will close on May 8th.  The
 +
elections nomination period will begin AFTER the questionnaire period
 +
has closed.
  
<ref>http://fedoraproject.org/wiki/Common_F17_bugs</ref>
+
You may add your burning questions for candidates to answer here:
 +
http://fedoraproject.org/wiki/F18_elections_questionnaire<ref>http://fedoraproject.org/wiki/F18_elections_questionnaire
 +
</ref>
  
===== Features =====
 
  
This release of Fedora includes a variety of features both over and
+
The following seats are available in this election:
under the hood that show off the power and flexibility of the advancing
 
state of free software.  Here are just a few of the new features:
 
 
 
On the desktop: GNOME 3.4 introduces many user experience improvements,
 
including new search capabilities in the activities overview, improved
 
themes, and enhancements to the Documents and Contacts applications.  A
 
new application, GNOME-boxes, provides easy access to virtual
 
machines. Additionally, GIMP 2.8, the newest version of the GNU Image
 
Manipulation Program, brings new improvements such as single-window
 
mode, layer groups, and on-canvas editing.
 
 
 
For developers: You never sausage a great array of development tools!
 
Fedora 17 includes a pre-release of Juno, the release of the Eclipse
 
SDK expected in June 2012.  Java 7 (and OpenJDK 7) is the default Java
 
runtime and Java build toolset, and GCC 4.7.x is now the primary
 
compiler in Fedora.  Other language refreshes include shipping Ruby
 
1.9.3, the latest stable version of the Ruby language, PHP 5.4, the
 
latest PHP stack, and Erlang has also been updated to the R15 release.
 
 
 
Under the hood, and in the cloud: The Cluster stack in Fedora includes
 
numerous and significant updates for both high availability and
 
load-balancing applications.  Fedora 17 utilizes Linux kernel 3.3, with
 
improved btrfs and ext4 filesystems, GMA (poulsbo) graphics and
 
Broadcom wireless chipset support, and numerous other bug fixes and
 
enhancements. Firewalld is now the default firewall solution in Fedora,
 
providing dynamic firewall configuration capabilities.  Finally,
 
OpenStack, a collection of services that can be used to set up and run
 
cloud compute and storage infrastructure, has been updated to the
 
latest release, 2012.1 (Essex).
 
 
 
And that's only the beginning. A more complete list and details of all
 
the new features in Fedora 17 is available here:
 
 
 
<ref>http://fedoraproject.org/wiki/Releases/17/FeatureList</ref>
 
 
 
We have nightly composes of alternate spins available here:
 
 
 
<ref>http://dl.fedoraproject.org/pub/alt/nightly-composes/</ref>
 
 
 
===== Contributing to Fedora =====
 
 
 
For more information on common and known bugs, tips on how to report
 
bugs, and the official release schedule, please refer to the release
 
notes:
 
 
 
<ref>http://docs.fedoraproject.org</ref>
 
 
 
There are many ways to contribute beyond bug reporting. You can help
 
translate software and content, test and give feedback on software
 
updates, write and edit documentation, help with all sorts of
 
promotional activities, and package free software for use by millions
 
of Fedora users worldwide. To get started, visit
 
<ref>http://join.fedoraproject.org</ref> today!"
 
 
 
<references/>
 
  
====Fedora 18 Release name voting and Poll for whether to continue naming releases====
+
* '''Fedora Project Board: 3 seats'''
Toshio Kuratomi <ref>a.badger at gmail.com</ref> on Fri Apr 20 00:04:15 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003060.html</ref>,
+
* '''FESCo (Fedora Engineering Steering Committee): 5 seats'''
 +
* '''FAmSCo (Fedora Ambassadors Steering Committee): 7 seats'''
  
"Voting for the Fedora 18 release names has begun.  You can find the
+
Please take note of the following changes for this election:
potential names in the voting application:
 
<ref>https://admin.fedoraproject.org/voting/</ref>
 
  
If you are a Fedora contributor (defined as having signed the FPCA and being
+
* All questions for the questionnaire must be submitted by May 8th,
in one other Fedora group in the account system) then you are eligilbe to
+
prior to the beginning of nominations. As seen in the schedule above,
vote.
+
the nomination period does not start until May 9th.
 +
* As noted on announce-list<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003063.html</ref>, FAmSCo is electing all 7 seats this
 +
cycle, with the goal of having staggered elections similar to the Board
 +
and FESCo. Additionally, voting eligibility has been widened to allow
 +
anyone who has signed the FPCA AND is a member of at least one
 +
additional non-FPCA/CLA group. (In other words: No longer just
 +
ambassadors, but those part of other teams as well.)
  
This cycle, the Board is also asking contributors to let us know if we
+
Full election information may be seen here:
should continue to have release names for future Fedora releases.  Even
+
http://fedoraproject.org/wiki/Elections<ref>http://fedoraproject.org/wiki/Elections</ref>
though the interface is the same, this portion is intended to be a poll
 
rather than a straight up vote.  The Fedora Board will look at the answers
 
to determine if enough contributors value continuing to create release names
 
to make it worthwhile in the future. If it does seem desirable, the Board
 
will likely look into forming a working group to come up with a new method
 
for creating release names for future releases.
 
  
The poll for keeping release names is also found in the voting application:
+
Participating in these bodies are one of many ways to contribute to
<ref>https://admin.fedoraproject.org/voting/</ref>
+
Fedora; I encourage you to consider running, or to urge those you
 +
believe are excellent candidates to run.  Additionally, your
 +
contributions are welcomed in helping to keep the elections running
 +
smoothly; volunteers are needed to help collect questionnaire answers
 +
from candidates, as well as for scheduling and moderating town halls. 
 +
If you are interested in helping with those efforts, please contact John
 +
Rose<ref>http://fedoraproject.org/wiki/User:Inode0</ref>.
  
Eligibility to answer the poll is the same as for being able to vote on the
+
And a big thank you! to John for coordinating the elections thus far,
names themselves (having signed the FPCA and being in one other group)."
+
your efforts are very much appreciated."
  
 
<references/>
 
<references/>

Revision as of 11:47, 29 April 2012

Announcements

Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

Breaking News of the Week

New FAmSCo election guidelines

Christoph Wickert[1] on Thu Apr 26 11:19:10 UTC 2012 announced[2],

"after months of - sometimes controversial - discussion I am am happy to announce the new FAmSCo election guidelines [3]. For those of you, who did not follow the discussion, here is a brief summary of the three most important changes:

More continuity

Instead of electing all seats once a year, we follow the example of the Fedora Board and FESCo and elect half of the committee every 6 months or with every release of Fedora. FAmSCo will not change over sudden and new members can easily catch up with their new duties by learning from others.

Easier filling of vacant seats

Every committee is in danger of members becoming inactive. This can happen to all of us for various reasons such as our dayjobs or personal problems. Under the old guidelines [4], we had to wait until only 3 members left - even with 2 left the committee is hardly operational - and then call a supplementary election - which never happened even though we had only 4 active members. Now we are filling vacant seat when necessary, either with runner-up candidates from the previous elections or by appointing new members.

Wider electorate

The ambassadors represent the whole Fedora Project, this is why now not only ambassadors are eligible to vote for FAmSCo, but everybody who has signed the Contributors License Agreement and is member of (at least) one other group in the Fedora Account System (FAS) is allowed to vote. This will not only strengthen FAmSCo's position but also help candidates who are active in other groups of the Fedora project.

Last but not least the guidelines have been massively cleaned up.

We think that the new guidelines are a big improvement and want them to come into effect as soon as possible. Therefor we will have a special election for Fedora 18 (the next regular elections were scheduled for F19). All 7 seats in FAmSCo are open for election. In order to make the transition to the new alternating terms, the top 4 vote-getters will serve 2 Fedora releases, the bottom 3 will have to run for re-election after one release.

More about the upcoming ambassadors elections to come later this week as part of the general Fedora 18 elections announcement. Please help us getting a better, stronger and more active FAmSCo by casting your votes.

If you have feedback or questions, please don't hesitate to ask. We are looking for your input on the Fedora ambassadors mailing list[5]."

Fedora Elections: General information, and questionnaire opening.

Robyn Bergeron-Fedora Project Leader[1] on Fri Apr 27 11:52:50 UTC 2012 announced[2],

"It is once again time for election season to begin. As noted in the elections schedule[3], the elections questionnaire is now open to populate with questions for candidates, and will close on May 8th. The elections nomination period will begin AFTER the questionnaire period has closed.

You may add your burning questions for candidates to answer here: http://fedoraproject.org/wiki/F18_elections_questionnaire[4]


The following seats are available in this election:

  • Fedora Project Board: 3 seats
  • FESCo (Fedora Engineering Steering Committee): 5 seats
  • FAmSCo (Fedora Ambassadors Steering Committee): 7 seats

Please take note of the following changes for this election:

  • All questions for the questionnaire must be submitted by May 8th,

prior to the beginning of nominations. As seen in the schedule above, the nomination period does not start until May 9th.

  • As noted on announce-list[5], FAmSCo is electing all 7 seats this

cycle, with the goal of having staggered elections similar to the Board and FESCo. Additionally, voting eligibility has been widened to allow anyone who has signed the FPCA AND is a member of at least one additional non-FPCA/CLA group. (In other words: No longer just ambassadors, but those part of other teams as well.)

Full election information may be seen here: http://fedoraproject.org/wiki/Elections[6]

Participating in these bodies are one of many ways to contribute to Fedora; I encourage you to consider running, or to urge those you believe are excellent candidates to run. Additionally, your contributions are welcomed in helping to keep the elections running smoothly; volunteers are needed to help collect questionnaire answers from candidates, as well as for scheduling and moderating town halls. If you are interested in helping with those efforts, please contact John Rose[7].

And a big thank you! to John for coordinating the elections thus far, your efforts are very much appreciated."

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above

Fedora 17 for Power Alpha Announcement

David Aquilina[1] on Tue Apr 10 19:51:42 UTC 2012 announced[2],

"Time flies like the wind...

As it's already time again for another Fedora release on Power, this time for Fedora 17 Alpha.

We've hit a couple of bumps along the road to the Alpha, but at long last we're finally at a state where we're ready to release it to the public.

Due to lack of developer time and hardware, Apple hardware support is at this point completely untested. Especially with the switch to grub2 we rely on community feedback and participation to make this work for this release. So if you have the hardware and want it to work, patches welcome! :)

The bits are available from your closest mirror:

[3]

More details about this Alpha release can be found here:

[4]

One of our focuses in the lead up to the beta of Fedora 17 for Power will be addressing architecture-specific packaging issues in as many packages as possible. If you own a package in Fedora which has ExclusiveArch or ExcludeArch set, please take a moment to verify that the architectures you've excluded or are exclusive to are still correct and sane.

I want to thank everyone involved in making this happen once more. Many Fedora packagers and contributors have again stepped up and helped fix issues that only appeared on Power hardware. Moreover the whole Fedora Secondary Arch team has been doing a fantastic job to get us to where we are now, especially considering that we had a complete switch of builders and hub hardware, mass rebuild and a hub failure along the way!

As usual, you can reach the whole team on the #fedora-ppc IRC channel on FreeNode and via our email list:

[5]

And we have our Secondary Arch wiki with (decently) updated information:

[6]

For Phil, Karsten, and the entire Fedora for Power team, Thanks & regards, David"

Fedora 17 Beta Go/No-Go Meeting, Round 3, Wednesday, April 11, @17:00 Eastern

Fedora New Project Leader, Robyn Bergeron[1] on Wed Apr 11 03:23:31 UTC 2012 announced[2],

"Please join us on irc.freenode.net in #fedora-meeting-1 for this important meeting. This will be Round 3 of this meeting for the Beta release of F17.

Wednesday, April 11, 2012 @21:00 UTC (17:00 EDT/14:00 PDT)

"Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting."

"Verifying that the Release criteria are met is the responsibility of the QA Team."

For more details about this meeting see: [3]

In the meantime, keep an eye on the Fedora 17 Beta Blocker list: [4]

Ongoing Beta RC test results can be seen here: [5]

See you there, Wednesday, in #fedora-meeting-1.

-Robyn, fingers and toes crossed thoroughly"

Fedora 17 Beta is declared GOLD

Robyn Bergeron - Fedora Project Leader[1] on Thu Apr 12 05:11:27 UTC 2012 announced[2],

"At today's F17 Beta Go/No-Go meeting, the Fedora 17 Beta release was declared gold. F17 Beta will be released Tuesday, April 17, 2012.

Thanks to everyone involved for pulling this one together and participating in the meetings, things came together well this week. :)

For those interested in the details:

Minutes: [3] Logs: [4]

Full minutes follow below.


Fedora-meeting-1: F17 Beta go no go meeting

Meeting started by rbergeron at 21:00:32 UTC. The full logs are available at [5]"

Fedora Events

The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (December 2011 - May 2012)

  • North America (NA)[1]
  • Central & South America (LATAM): [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Past Events

Archive of Past Fedora Events[1]

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.