From Fedora Project Wiki

< FWN‎ | Beats

mNo edit summary
(Fedora Announcement Beat done)
Line 14: Line 14:
<references/>
<references/>


====Want to get to FUDCon Tempe on time? Take a Tour!====
====FUDCon EMEA Bidding now open====  
Clint Savage<ref>herlo1 at gmail.com</ref> on Sat Jan 29 08:13:52 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-January/002915.html</ref>,


"If you are coming to FUDCon Tempe and have never been to the ASU campus, we don’t want you to get lost. Let the FUDCon tour guides help you out on your way over to the barcamp pitches tomorrow morning.
Jared K. Smith<ref>Jared K. Smith jsmith at fedoraproject.org</ref> on Fri Feb 4 13:49:31 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-February/002917.html</ref>,


Every 10 minutes, starting at 7:45am, meet in the lobby of the Courtyard Marriott.  You will be directed on a walking tour as we head toward the Center for Design North (CDN), also known as the Architecture and Environmental Design Building (AED).
"Now that FUDCon Tempe has successfully finished, it's time to open the bidding process for FUDCon EMEA 2011.


=====On the tour=====
The bidding process is described at<ref>https://fedoraproject.org/wiki/FUDCon_bid_process</ref>.  Any interested parties are invited to submit their bids. Once you have prepared a bid, please send an email to the fudcon-planning list.  Bids will be accepted up until the end of the day on March 15th, 2011.
you will see the following items:


* A short tour of Mill Avenue, with restaurants and pubs
We look forward to seeing your proposals!"
* The Brickyard Artisan Court (where the Barcamp sessions will be held)
* The Center for Design North (where the Barcamp pitches will be held)


In addition to all this, you’ll be on time to the barcamp pitches! But don’t miss out, the last tour will begin at 8:45 so we can all get there before 9am.
<references/>


If you don’t get the tour, you can still make it on your own. Here’s a map with information to make it simple and straightforward<ref>http://ur1.ca/31gne</ref>. It’s a google map and works well by searching for the url right in your maps program on a smart phone."
====[Guidelines Change] Changes to the Packaging Guidelines==== 
 
Tom Callaway<ref>Tom Callaway tcallawa at redhat.com</ref> on Fri Feb 4 17:18:07 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-February/002918.html</ref>,
 
"Here are the latest set of changes to the Fedora Packaging Guidelines:
 
---
The rules for substituting dots with dashes in package names have been
clarified to make explicit that they apply to python modules and that
they do not apply to version numbers in compat libraries.
<ref>https://fedoraproject.org/wiki/Packaging:NamingGuidelines</ref>
 
---
Many implementations of md5 originate in a program and then end up
copied to other programs with compatible license terms.  These
implementations have been granted a bundling exception.  The usual
requirement to set a Virtual Provides: if bundling are in effect and
have some special notes due to the many implementations out there.  Note
that copying the implementation from a library is not covered under this
exception.
<ref>https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Packages_granted_exceptions</ref>
 
---
rpm and yum treat a dependency on a package of the form Requires: foo as
being fulfilled by any available package foo, regardless of arch. On
multilib architectures, this means that there are often two packages
with the same name: one for each of the multilib arches. When yum is
asked to satisfy a dependency for that package name it could pull in the
package for the wrong arch. This happens when the correct architecture
is not available to yum. That might be the case if, due to some
malfunction, the Fedora repositories are out of synch. It can also
happen if a user has installed a package that is treated as "newer" than
the corresponding package in the currently enabled set of repositories;
in attempting to resolve otherwise-unresolvable dependency chains, yum
may decide to pull in the dependency chain for a different arch.
 
In some situations, this is not a problem, but there are some situations
where it does matter:
 
* A library that is explicitly Required (example a dlopen'd library)
* The dependency from one -devel packages that is not noarch to another -devel package.
* A non-noarch subpackage's dependency on its main package or another subpackage (e.g., libfoo-devel depends on libfoo, or fooapp-plugins depends on foo-app).
 
The Packaging Guidelines (and Naming Guidelines) have been amended to
reflect that %{?_isa} must be used for Explicit Requires and Provides
that match those situations.
 
<ref>http://fedoraproject.org/wiki/Packaging:Guidelines#Requires</ref>
<ref>http://fedoraproject.org/wiki/Packaging:Guidelines#Explicit_Requires</ref>
<ref>http://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package</ref>
<ref>https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Renaming.2Freplacing_existing_packages</ref>
 
---
 
Previously, there was a change made to the Documentation guidelines
which stated that:
 
If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present.
 
In addition, %doc files must not have executable permissions.
 
This has been revised to:
 
Files marked as documentation must not cause the package to pull in more dependencies than it would without the documentation. One simple way to ensure this is to remove all executable permissions from %doc files (chmod -x).
 
Also, if a package includes something as %doc, it must not affect the runtime of the packaged application(s). To summarize: If it is in %doc, the included programs must run properly if it is not present.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation</ref>
 
---
A new section has been added to the Packaging Guidelines concerning test suites included with source code:
 
If the source code of the package provides a test suite, it should be executed in the %check section, whenever it is practical to do so.
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Test_Suites</ref>
 
---
A new section has been added to the Packaging Guidelines concerning the proper packaging of tmpfiles.d configurations and directories:
 
<ref>https://fedoraproject.org/wiki/Packaging:Tmpfiles.d</ref>
 
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
 
Many thanks to Jochen Schmitt 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>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
 
<references/>
 
====Updating SSL keys on fedorahosted.org==== 
 
Stephen Smoogen<ref>Stephen Smoogen smooge at gmail.com</ref> on Tue Feb 8 20:27:24 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-February/002919.html</ref>,
 
"Various SSL keys are aging out so we will be updating them before anyone gets a <This CERT is not valid.> page.
 
The first server to be updated will be fedorahosted.org.
 
The old certificate came from Equifax, was a 1024 bit key and had the fingerprint:
 
SHA1 Fingerprint=CC:64:67:BE:90:50:79:ED:23:E8:C1:18:02:AB:AC:83:88:FC:6C:D8
 
The new certificate is issued by GeoTrust, Inc and is a 4096 bit key with the fingerprint:
 
SHA1 Fingerprint=D1:54:82:77:77:F9:11:DF:E0:B1:14:37:B9:36:E2:09:20:B6:54:1D
 
Please report any problems with these certificates to '''admin at fedoraproject.org'''"
 
<references/>
 
====GSoC 2011 Ideas Needed!==== 
 
Ryan Rix<ref>Ryan Rix ry at n.rix.si<ref> on Tue Feb 8 23:17:49 UTC 2011 <ref>http://lists.fedoraproject.org/pipermail/announce/2011-February/002920.html</ref>,
 
"Hey guys gals and other hackerfolk!
 
Google's Summer of Code is coming up ever so close. We have 20 days until the  
org application opens up, and we need a '''LOT''' more ideas if we are going to
have any hope of being accepted. I know there are a lot of awesome ideas out
there in the community, we just need folks to step up and tell us about them.
It's free labour, and a great chance to attract new Fedora contributors.  
 
So, folks, go add ideas to the Ideas page at:
<ref>https://fedoraproject.org/wiki/Summer_coding_ideas_for_2011</ref>"


<references/>
<references/>

Revision as of 16:47, 9 February 2011

Announcements

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

Contributing Writer: Rashadul Islam

Fedora Announcement News

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

FUDCon EMEA Bidding now open

Jared K. Smith[1] on Fri Feb 4 13:49:31 UTC 2011 announced[2],

"Now that FUDCon Tempe has successfully finished, it's time to open the bidding process for FUDCon EMEA 2011.

The bidding process is described at[3]. Any interested parties are invited to submit their bids. Once you have prepared a bid, please send an email to the fudcon-planning list. Bids will be accepted up until the end of the day on March 15th, 2011.

We look forward to seeing your proposals!"

[Guidelines Change] Changes to the Packaging Guidelines

Tom Callaway[1] on Fri Feb 4 17:18:07 UTC 2011 announced[2],

"Here are the latest set of changes to the Fedora Packaging Guidelines:

--- The rules for substituting dots with dashes in package names have been clarified to make explicit that they apply to python modules and that they do not apply to version numbers in compat libraries. [3]

--- Many implementations of md5 originate in a program and then end up copied to other programs with compatible license terms. These implementations have been granted a bundling exception. The usual requirement to set a Virtual Provides: if bundling are in effect and have some special notes due to the many implementations out there. Note that copying the implementation from a library is not covered under this exception. [4]

--- rpm and yum treat a dependency on a package of the form Requires: foo as being fulfilled by any available package foo, regardless of arch. On multilib architectures, this means that there are often two packages with the same name: one for each of the multilib arches. When yum is asked to satisfy a dependency for that package name it could pull in the package for the wrong arch. This happens when the correct architecture is not available to yum. That might be the case if, due to some malfunction, the Fedora repositories are out of synch. It can also happen if a user has installed a package that is treated as "newer" than the corresponding package in the currently enabled set of repositories; in attempting to resolve otherwise-unresolvable dependency chains, yum may decide to pull in the dependency chain for a different arch.

In some situations, this is not a problem, but there are some situations where it does matter:

  • A library that is explicitly Required (example a dlopen'd library)
  • The dependency from one -devel packages that is not noarch to another -devel package.
  • A non-noarch subpackage's dependency on its main package or another subpackage (e.g., libfoo-devel depends on libfoo, or fooapp-plugins depends on foo-app).

The Packaging Guidelines (and Naming Guidelines) have been amended to reflect that %{?_isa} must be used for Explicit Requires and Provides that match those situations.

[5] [6] [7] [8]

---

Previously, there was a change made to the Documentation guidelines which stated that:

If a package includes something as %doc, it must not affect the runtime of the application. To summarize: If it is in %doc, the program must run properly if it is not present.

In addition, %doc files must not have executable permissions.

This has been revised to:

Files marked as documentation must not cause the package to pull in more dependencies than it would without the documentation. One simple way to ensure this is to remove all executable permissions from %doc files (chmod -x).

Also, if a package includes something as %doc, it must not affect the runtime of the packaged application(s). To summarize: If it is in %doc, the included programs must run properly if it is not present. [9]

--- A new section has been added to the Packaging Guidelines concerning test suites included with source code:

If the source code of the package provides a test suite, it should be executed in the %check section, whenever it is practical to do so.

[10]

--- A new section has been added to the Packaging Guidelines concerning the proper packaging of tmpfiles.d configurations and directories:

[11]

--- These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).

Many thanks to Jochen Schmitt 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: [12]"

Updating SSL keys on fedorahosted.org

Stephen Smoogen[1] on Tue Feb 8 20:27:24 UTC 2011 announced[2],

"Various SSL keys are aging out so we will be updating them before anyone gets a <This CERT is not valid.> page.

The first server to be updated will be fedorahosted.org.

The old certificate came from Equifax, was a 1024 bit key and had the fingerprint:

SHA1 Fingerprint=CC:64:67:BE:90:50:79:ED:23:E8:C1:18:02:AB:AC:83:88:FC:6C:D8

The new certificate is issued by GeoTrust, Inc and is a 4096 bit key with the fingerprint:

SHA1 Fingerprint=D1:54:82:77:77:F9:11:DF:E0:B1:14:37:B9:36:E2:09:20:B6:54:1D

Please report any problems with these certificates to admin at fedoraproject.org"

GSoC 2011 Ideas Needed!

Ryan RixCite error: Closing </ref> missing for <ref> tag,

"Hey guys gals and other hackerfolk!

Google's Summer of Code is coming up ever so close. We have 20 days until the org application opens up, and we need a LOT more ideas if we are going to have any hope of being accepted. I know there are a lot of awesome ideas out there in the community, we just need folks to step up and tell us about them. It's free labour, and a great chance to attract new Fedora contributors.

So, folks, go add ideas to the Ideas page at: [1]"

Fedora Development News

The development list[1] 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 GNOME 3 Test Day #1 coming up tomorrow

Adam Williamson[1] on Wed Feb 2 18:58:27 UTC 2011 announced[2]

"QA and Desktop teams are running three Test Days to test out GNOME 3 ahead of F15 (and GNOME 3.0) releases, and the first is tomorrow!

[3]

Please come along and help test - there will be live images so you won't need a Rawhide installation, the testing will be easy, and you don't have to do every single test - you can help out even with ten or fifteen minutes (plus the time to download and burn an image). Please note that right now the wiki page is in considerable flux - I have to write a whole bunch of test cases which aren't up there yet - and desktop team are in the middle of trying to land GNOME 2.91.6 in Rawhide, so please hold off on testing for now, we should have everything in order by tomorrow morning. If you're busy tomorrow, you can certainly come by and do the tests later - all you'll miss is the IRC communication, but you can do all the testing based on the Wiki page. IRC channel is #fedora-test-day on Freenode. Please grab me if you have any questions or suggestions! Thanks everyone."

Fedora Events

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.