From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
Line 5: Line 5:
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.


Contributing Writer: [[User:Rashadul|Rashadul Islam]]
Contributing Writer: [[User:pcalarco|Pascal Calarco]]


<references/>
<references/>
Line 14: Line 14:
<references/>
<references/>


====Fedora 16 Naming: Nominations are now open. Submit your suggestion!====   
====Outage: Serverbeach servers downtime 2011-03-16 03:00 UTC -> 2011-03-16 09:00 UTC====   
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Thu Mar 3 16:34:02 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002931.html</ref>


"Hear ye, hear ye! Attention, all Fedora fans and release naming enthusiasts:
[[User:smooge|Stephen Smoogen]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002937.html</ref>


The time has come once again to choose the name for the next
"There will be an outage starting at 2011-03-16 03:00 UTC, which will last approximately 6 hours. [Outages should be only 10-30 minutes long but
release of Fedora.  Potential names will be accepted for consideration
the window for the outage is 6 hours thus the large window.]
beginning March 3rd (in other words, NOW) through March 10.


<ref>https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_16</ref>
To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
or run:


Please note that you *must* follow the instructions and guidelines at
date -d '2011-03-16 03:00 UTC'
the page listed above if you want your name to be considered.  For
instance, there must be an "is-a" link between the name Lovelock (from
Fedora 15) and the name you suggest. That link must be different than
previous links for Fedora release names.  Also, we ask that you please
conduct the required searches for brand and trademark names that might
cause us problems.


Read the full guidelines at that page, where you can also find full
Reason for outage:
schedule details for the release naming process.


For those of you interested in reviewing the history of Fedora
===== Affected Services: =====
release names, there is an appropriately named wiki page for doing so:


<ref>http://fedoraproject.org/wiki/History_of_Fedora_release_names</ref>
DNS - ns1.fedoraproject.org,
Fedora Hosted - https://fedorahosted.org/
Fedora Talk - http://talk.fedoraproject.org/
Email for fedoraproject.org


Be fun. Be creative. Help pick out an awesome name for Fedora 16! I am
===== Contact Information: =====
looking forward to your suggestions."


<references/>
Please join #fedora-admin in irc.freenode.net or respond to this email to
 
track the status of this outage.
====Announcing the release of Fedora 15 Alpha!!==== 
Dennis Gilmore<ref>Dennis Gilmore dennis at ausil.us</ref> on Tue Mar 8 15:00:56 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002932.html</ref>,
 
"The Fedora 15 "Lovelock" Alpha release is available! This release
offers a preview of some of the best free and open source technology
currently under development. Catch a glimpse of the future:
 
<ref>http://fedoraproject.org/get-prerelease</ref>
 
=====What is the Alpha release?=====
 
The Alpha release contains all the beefy features of Fedora 15 in a
form that anyone can help test. This testing, guided by the Fedora QA
team, helps us target and identify bugs. When these bugs are fixed, we
make a Beta release available. A Beta release is code-complete, and
bears a very strong resemblance to the third and final release. The
final release of Fedora 15 is due in May.
 
We need your help to make Fedora 15 the best release yet, so please
take a moment of your time to download and try out the Alpha and make
sure the things that are important to you are working. If you find a
bug, please report it -- every bug you uncover is a chance to improve
the experience for millions of Fedora users worldwide. Together, we
can make Fedora a rock-solid distribution. (Read down to the end of
the announcement for more information on how to help.)
 
=====Features=====
 
This release of Fedora includes a variety of features both over and
under the hood that show off the power and flexibility of the
advancing state of free software. Examples include:
 
* Updated Desktop Environments. Fedora 15 will ship with GNOME 3, the
next major version of the GNOME desktop. If you're interested in other
experiences, KDE and Xfce will also be showcasing the latest and
greatest in desktop technology from their respective projects.
* System and session management. Previously available as a technology
preview in F14, systemd makes its full-fledged debut in Fedora 15.
systemd is a smarter, more efficient way of starting up and managing
the background daemons relied on by services we all use every day -
such as NetworkManager and PulseAudio.
* Cloud. Looking to create appliances for use in the Cloud? BoxGrinder
creates appliances (virtual machines) for various platforms (KVM, Xen,
EC2) from simple plain text appliance definition files for various
virtual platforms.
* Updated programming languages and tools. Fedora 15 features new
versions of Rails, OCaml, and Python. GDB and GCC have also been
updated. (Fedora 15 was built with GCC 4.6.0, too!)
* Productivity Applications. LibreOffice is filled with tools for
everyday use, including word processing, spreadsheet, and presentation
applications.
* Consistent Network Device Naming. Server management just got even
easier. Fedora 15 uses BIOS-provided, non-arbitrarily given names for
network ports, taking the burden off of system administrators.
* Dynamic Firewall. Fedora 15 adds support for the optional firewall
daemon, that provides a dynamic firewall management with a D-Bus
interface.
* eCryptfs in Authconfig. Fedora 15 brings in improved support for
eCryptfs, a stacked cryptographic filesystem for Linux. Starting with
Fedora 15, authconfig can be used to automatically mount a private
encrypted part of the home directory when a user logs in.
* DNSSEC for workstations. NetworkManager now uses the BIND nameserver
as a DNSSEC resolver. All received DNS responses are proved to be
correct. If particular domain is signed and failed to validate then
resolver returns SERFVAIL instead of invalidated response, which means
something is wrong.
* Go Green. Power Management improvements include the PowerTOP tool,
which identifies the software components that make your computer use
more energy than necessary while idle. Automatic tuning of power
consumption and performance helps conserve on laptop battery usage,
too!
* Business Management tools. Tryton is a three-tier high-level general
purpose application platform, providing solutions for accounting,
invoicing, sale management, purchase management, analytic accounting,
and inventory management.
* New Package Suite Groups. The Graphics suite group has been renamed
to the Design group, and the Robotics SIG has created the Robotics
Package Suite, a collection of software that provides an
out-of-the-box usable robotic simulation environment featuring a
linear demo to introduce new users.
 
These and many other improvements provide a wide and solid base for
future releases, further increasing the range of possibilities for
developers and helping to maintain Fedora's position at the leading
edge of free and open source technology.
 
A more complete list and details of each new cited feature is available here:
<ref>http://fedoraproject.org/wiki/Releases/15/FeatureList</ref>
 
We have nightly composes of alternate spins available here:
<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/</ref>
 
=====Issues and Details=====
 
For more information including common and known bugs, tips on how to
report bugs, and the official release schedule, please refer to the
release notes:
<ref>http://fedoraproject.org/wiki/Fedora_15_Alpha_release_notes</ref>
 
A shorter list of common bugs can be found here:
<ref>https://fedoraproject.org/wiki/Common_F15_bugs</ref>
 
=====Contributing=====


Bug reports are helpful, especially for Alpha. If you encounter any
Smooge [Temporary Interim Chief Cat Wranglger]
issues please report them and help make this release of Fedora the
best ever."
 
<references/>
 
====Update on FUDCons in 2011==== 
Jared K. Smith, Fedora Project Leader,<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Wed Mar 9 18:53:00 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002933.html</ref>,
 
"I want to take this opportunity to bring your attention to a few
important matters regarding FUDCon events in 2011.
 
Travel subsidy deadline for FUDCon Panama 2011 on March 14th
----
Planning is in full swing for FUDCon Panama in May, and it's time for
the FUDCon planning team to begin evaluating subsidy requests.  The
deadline for the first round of travel subsidies is the end of the day
(UTC time) on March 14th, and the FUDCon planning team will be meeting
on March 15th to evaluate those requests.  Any subsidy requests made
after that time will be handled in a future subsidy meeting.  I
encourage anyone interested in attending FUDCon Panama and requiring
travel assistance to refer to the instructions at
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref> to learn
about the subsidy process and open a Trac ticket with their details.
We'll be giving priority to those travelers in Latin America who
actively contribute to Fedora in meaningful ways.
 
Bids for FUDCon EMEA 2011 due March 15th.
----
I'm happy to see several bids starting to come in for FUDCon EMEA
2011.  This is a reminder that any bids for FUDCon EMEA 2011 are due
by the end of the day (UTC time) on March 15th.  If you're interested
in submitting a bid, please create a wiki page with the details and
send an email to the fudcon-planning list letting us know about your
bid.  Refer to <ref>http://fedoraproject.org/wiki/FUDCon_bid_process</ref> for
more details, or
<ref>http://fedoraproject.org/wiki/FUDCon:Bid_for_Tempe_2011</ref> for an example
of a very thorough bid page.
 
Bids for FUDCon North America 2011/2012
----
I'd also like to formally open up bidding for FUDCon North America for
the December 2011/January 2012 time frame.  Bids will be due by the
end of the day (UTC time) on April 8th.  Again, please refer to
<ref>http://fedoraproject.org/wiki/FUDCon_bid_process</ref> for more details.
 
If you have any questions, please ask for help on the '''fudcon-planning'''
mailing list or in the '''#fudcon-planning''' channel on IRC."


<references/>
<references/>
Line 218: Line 61:
<references/>
<references/>


====Fedora 15 Alpha Go/No-Go Meeting Wednesday, March 2, 2011 @ 22:00 UTC==== 
====Reminder: today is GNOME 3 Test Day #2====   
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Wed Mar 2 16:20:15 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000760.html</ref>,
 
"Join us on irc.freenode.net #fedora-meeting for this important meeting.
 
Wednesday, March 2, 2011 @22:00 UTC (17:00 EST/14:00 PST)
 
"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:
<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
 
In the meantime, keep an eye on the Fedora 15 Alpha Blocker list:
 
<ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=657616&hide_resolved=1</ref>
 
Talk to you today (sorry for the late notice; I think I've touched base
with it on most folks about it for this week, though. I'm officially ill.)"
 
<references/>
 
====Fedora 15 Alpha declared GOLD!==== 
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Wed Mar 2 22:42:25 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000761.html</ref>,
 
"At the F15 Alpha Go/No-Go Meeting that just occurred, the Fedora 15
Alpha release was declared GOLD.
 
Thanks to all of those who helped out to make this happen!
 
Meeting notes can be found here:
Minutes:
<ref>http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora_15_alpha_gono-go_meeting.2011-03-02-22.00.txt</ref>
Full Log:
<ref>http://meetbot.fedoraproject.org/fedora-meeting/2011-03-02/fedora_15_alpha_gono-go_meeting.2011-03-02-22.00.log.html</ref>
 
Cheers! And onwards we go to Beta :)"
 
<references/>
 
====ACTION REQUIRED: Important hanges to Fedora translation workflow==== 
Jared K. Smith<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Thu Mar 3 15:46:28 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000762.html</ref>,
 
"Quick Summary
---
The Fedora translation workflow has changed.  If you are a developer
of a package being translated by the Fedora Translation (L10n)
Project, you must change your workflow slightly if you want translated
strings to appear in your software package. Tools and assistance are
available to make this workflow as simple as possible for developers.
Read below for details.
 
Details
---
Over the past couple of weeks, we've made some improvements and
infrastructure changes to the Fedora translation system.  We've moved
from a self-hosted version 0.7 instance of the Transifex software to a
hosted version of the 1.1-dev version at Transifex.net. The upgrade
from version 0.7 to version 1.0 (and beyond) introduces a number of
important changes for developers and packagers.  Please pay close
attention to this email, particularly if your software package uses
translations provided by the Fedora Translation team.  While the
changes aren't terribly complicated, they do have a bigger impact on
the developer than they do on the translation team.
 
The most visible change is that Transifex’s native integration with
source code management systems has been replaced by a mechanism for
automatic updates.  Transifex now watches an HTTP view of a repository
for change notifications.  In addition, there is now a more secure
command-line tool for project maintainers and translators.  This new
command-line tool has been packaged for Fedora in the
"transifex-client" package.  It is currently available in Rawhide
(pre-F16), and in the "updates-testing" repositories for Fedora 13,
14, and 15, and EPEL 5 and 6.
 
Here's the new workflow:
 
This series of steps only needs to be run once for a project.
* The developer installs the "transifex-client" package:
yum --enablerepo=updates-testing install transifex-client
* The developer runs the "tx init" command in the top level folder of
the project.
* The developer runs the "tx set" command according  to the
transifex-client user guide found at
 
<ref>http://help.transifex.net/user-guide/client/client-0.4.html</ref>.  This
creates a small config file, .tx/config, which can be committed in the
repository for re-use, if desired.
 
This series of steps are run on as as-needed basis:
* The developer updates and commits his or her POT file to the
project's repository at string-freeze time or as needed.
* Transifex watches an HTTP link to that POT file and auto-updates its
English strings regularly, *OR* the developer can also push the POT
file to Transifex (either manually or as part of a
build script) by using the "tx push" command.
* Translators work inside Transifex.  Translated strings are stored
inside of Transifex, and are *not* pushed automatically to the
developer's repo.
* Before rolling a release, the developer runs 'tx pull' (either
manually or from a build script) to fetch the latest translation files
from Transifex. Translation files do not need to live in
the repo, although the developer may commit and store copies if desired.
 
For more details on the features of the new version of Transifex and
more help on using the transifex client, please refer to either
<ref>http://help.transifex.net/user-guide/one-dot-zero.html</ref> or the
Fedora-specific wiki page at <ref>https://fedoraproject.org/wiki/FAQ_on_migration_to_transifex.net</ref>. If you have technical questions, feel free to ask questions in the #fedora-l10n or #transifex IRC channels or on the devel mailing list."
 
<references/>
 
====poppler soname bump in F15 and rawhide==== 
Marek Kasik<ref>Marek Kasik mkasik at redhat.com</ref> on Fri Mar 4 14:30:33 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000763.html</ref>,
 
"I plan to rebase poppler in Fedora 15 and rawhide to poppler-0.16.3.
There is one API change (in PreScanOutputDev.h) and 1 soname bump
(libpoppler.so.12 to libpoppler.so.13).
You can test it against your package with this scratch-build:
<ref>http://koji.fedoraproject.org/koji/taskinfo?taskID=2884655</ref>
I'll do chain-build of poppler and packages requiring it next Thursday
(10th of March)."
 
<references/>
 
====xerces-c soname bump in Rawhide====   
Kalev Lember<ref>Kalev Lember kalev at smartlink.ee</ref> on Wed Mar 9 22:35:22 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000765.html</ref>,
 
"Jonathan Robie and I are planning to update xerces-c from 3.0.1 to 3.1.1
in Rawhide, which includes a soname bump; F-15 will stay on 3.0.1.


I will handle the rebuilds of affected packages:
[[User:Adamw|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000766.html</ref>,


* blahtexml-0.8-2.fc15
"Hi, everyone! Just a quick reminder that today is the second Test Day for GNOME 3:<ref>https://fedoraproject.org/wiki/Test_Day:2011-03-10_GNOME3_Beta</ref> . Please do come along and help with testing if you can. We're having trouble with the 32-bit live image, but a 64-bit image is available now and all
* cegui-0.7.5-5.fc15
the test instructions are in place. We'll be in #fedora-test-day on IRC all day long to help out with testing, so come along and join us there. Thanks a lot!
* enigma-1.01-12
--  
* frepple-0.8.1-3.fc15
Adam Williamson
* gdal-1.7.3-2.fc15
Fedora QA Community Monkey
* glest-3.2.2-7.fc15
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
* libdigidocpp-0.3.0-3.fc15
http://www.happyassassin.net"
* opensaml-2.3-3.fc15
* ovaldi-5.6.4-1.fc14
* qpid-cpp-0.8-6.fc16
* xalan-c-1.10.0-8.fc15
* xmlcopyeditor-1.2.0.2-4.fc15
* xml-security-c-1.5.1-4.fc15
* xmltooling-1.3.3-2.fc15
* xqilla-2.2.3-8.fc14
* xsd-3.3.0-4.fc15"


<references/>
<references/>

Revision as of 12:45, 17 March 2011

Announcements

In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

Fedora Announcement News

The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]

Outage: Serverbeach servers downtime 2011-03-16 03:00 UTC -> 2011-03-16 09:00 UTC

Stephen Smoogen announced[1]

"There will be an outage starting at 2011-03-16 03:00 UTC, which will last approximately 6 hours. [Outages should be only 10-30 minutes long but the window for the outage is 6 hours thus the large window.]

To convert UTC to your local time, take a look at[2] or run:

date -d '2011-03-16 03:00 UTC'

Reason for outage:

Affected Services:

DNS - ns1.fedoraproject.org, Fedora Hosted - https://fedorahosted.org/ Fedora Talk - http://talk.fedoraproject.org/ Email for fedoraproject.org

Contact Information:

Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.

Smooge [Temporary Interim Chief Cat Wranglger]

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

Reminder: today is GNOME 3 Test Day #2

Adam Williamson announced[1],

"Hi, everyone! Just a quick reminder that today is the second Test Day for GNOME 3:[2] . Please do come along and help with testing if you can. We're having trouble with the 32-bit live image, but a 64-bit image is available now and all the test instructions are in place. We'll be in #fedora-test-day on IRC all day long to help out with testing, so come along and join us there. Thanks a lot! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net"

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 (Dec 2010 - Feb 2011)

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