From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 14: Line 14:
<references/>
<references/>


====Outage: Serverbeach servers downtime 2011-03-16 03:00 UTC -> 2011-03-16 09:00 UTC==== 
====Fedora accepted in to Google Summer of Code 2011!====
Ryan Rix<ref>ry at n.rix.si</ref> on Sat Mar 19 06:45:46 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002939.html</ref>,


[[User:smooge|Stephen Smoogen]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002937.html</ref>
"Heya folks :)


"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
So... after a year's hiatus, Fedora's been accepted in to Google's Summer of
the window for the outage is 6 hours thus the large window.]
Code program for summer 2011!


To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
If you're a university student looking for a job this summer, start thinking
or run:
about some awesome idea that you'd like to make happen in Fedora this
summer. Applications will open March 28, so start talking with developers in
IRC and mail, and find something awesome to do! We have a list of some ideas
at: <ref>http://fedoraproject.org/wiki/Summer_coding_ideas_for_2011</ref> but don't
limit yourself to that list. Find a mentor, and make your idea happen!


date -d '2011-03-16 03:00 UTC'
Mentors should apply to be a mentor<ref>http://www.google-melange.com/gsoc/org/apply_mentor/google/gsoc2011</ref>  in Google's Melange instance. be inviting those who are listed on the Ideas page. We've still some work to do
before the student applications open, some scaffolding to build, and some
things to decide, so please join in. I'll be sending mentors more information
soon.


Reason for outage:
we're listed as The Fedora Project


===== Affected Services: =====
Congratulations, everyone, for the Awesome we're doing!"


DNS - ns1.fedoraproject.org,
<references/>
Fedora Hosted - https://fedorahosted.org/
 
Fedora Talk - http://talk.fedoraproject.org/
====[Guidelines Change] Changes to the Packaging Guidelines====
Email for fedoraproject.org
 
Tom Callaway<ref>tcallawa at redhat.com</ref> on Tue Mar 22 01:40:43 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002940.html</ref>,
 
"Here are the latest set of changes to the Fedora Packaging Guidelines:
 
---
 
The Emacs packaging guidelines were updated to handle cases where a
package's principal functionality does not require (X)Emacs, but the
package also includes some auxiliary Elisp files to provide support for
the package in (X)Emacs.
 
<ref>https://fedoraproject.org/wiki/Packaging:Emacs</ref>


===== Contact Information: =====
---


Please join #fedora-admin in irc.freenode.net or respond to this email to
The Scriptlet Snippets section dealing with the order that scriptlets
track the status of this outage.
are invoked has been updated to include %trigger scripts.


Smooge [Temporary Interim Chief Cat Wranglger]
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering</ref>
 
---
 
A subsection was added to the Packaging Guidelines section on Filesystem
Layout in which it is made explicit that binaries in /bin or /sbin must
NOT depend on any libraries in /usr/lib or /usr/lib64.
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Binaries_in_.2Fbin_and_.2Fsbin</ref>
 
---
 
The section on Epochs was improved, and clarifying language about Epoch
use in Requires was added to the Packaging Guidelines.
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Use_of_Epochs</ref>
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Requires</ref>
 
---
 
New guidelines were added covering the packaging of Ada programs.
<ref>https://fedoraproject.org/wiki/Packaging:Ada</ref>
 
---
 
The section on Boostrapping in the Treatment of Bundled Libraries page
in the Packaging Guidelines has been amended to add the following:
 
Packages which are built in such a bootstrapping mode must not be tagged
for a final release (or pushed as an update for any stable release). FPC
will track the progress of approved bootstrapping exceptions via the
ticket requesting the bootstrap bundling exception.
 
<ref>https://fedoraproject.org/wiki/Packaging:Treatment_Of_Bundled_Libraries#Bootstrapping</ref>
 
---
 
Macro forms of system executables (such as %{__rm}) should not be used
except when there is a need to allow the location of those executables
to be configurable.
 
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Macros</ref>
 
---
 
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
 
Many thanks to Hans Niedermann, Jonathan Underwood, Pavel Zhukov, 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>"


<references/>
<references/>
Line 61: Line 136:
<references/>
<references/>


====Reminder: today is GNOME 3 Test Day #2====  
====Your package translation====
 
Noriko<ref>noriko at fedoraproject.org</ref> on Mon Mar 21 23:57:43 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000769.html</ref>,
 
"Dear Fedora package maintainers
 
Could you all please take a few minutes and check if your packages are
on the list<ref>http://www.transifex.net/projects/p/fedora/r/fedora-15/l/en/</ref>and set to allow Fedora Localization Project to translate?


[[User:Adamw|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000766.html</ref>,
* setuptool: <ref>http://www.transifex.net/projects/p/setuptool/</ref>
* pam_krb5: <ref>http://www.transifex.net/projects/p/pam_krb5/</ref>
* pkinit-nss: <ref>http://www.transifex.net/projects/p/pkinit-nss/</ref>


"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
* The above packages are on the list but do not allow Fedora
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!
Localization teams to upload the translated files. This means that these
--
packages will not receive any translation from FLP. Please change the  
Adam Williamson
setting to allow FLP, or advise us if the maintainers choose having
Fedora QA Community Monkey
their own translation teams. In that case, the packages may be removed
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
from the list of Fedora Project on tx.net."
http://www.happyassassin.net"


<references/>
<references/>

Revision as of 04:02, 24 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]

Fedora accepted in to Google Summer of Code 2011!

Ryan Rix[1] on Sat Mar 19 06:45:46 UTC 2011 announced[2],

"Heya folks :)

So... after a year's hiatus, Fedora's been accepted in to Google's Summer of Code program for summer 2011!

If you're a university student looking for a job this summer, start thinking about some awesome idea that you'd like to make happen in Fedora this summer. Applications will open March 28, so start talking with developers in IRC and mail, and find something awesome to do! We have a list of some ideas at: [3] but don't limit yourself to that list. Find a mentor, and make your idea happen!

Mentors should apply to be a mentor[4] in Google's Melange instance. be inviting those who are listed on the Ideas page. We've still some work to do before the student applications open, some scaffolding to build, and some things to decide, so please join in. I'll be sending mentors more information soon.

we're listed as The Fedora Project

Congratulations, everyone, for the Awesome we're doing!"

[Guidelines Change] Changes to the Packaging Guidelines

Tom Callaway[1] on Tue Mar 22 01:40:43 UTC 2011 announced[2],

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

---

The Emacs packaging guidelines were updated to handle cases where a package's principal functionality does not require (X)Emacs, but the package also includes some auxiliary Elisp files to provide support for the package in (X)Emacs.

[3]

---

The Scriptlet Snippets section dealing with the order that scriptlets are invoked has been updated to include %trigger scripts.

[4]

---

A subsection was added to the Packaging Guidelines section on Filesystem Layout in which it is made explicit that binaries in /bin or /sbin must NOT depend on any libraries in /usr/lib or /usr/lib64.

[5]

---

The section on Epochs was improved, and clarifying language about Epoch use in Requires was added to the Packaging Guidelines.

[6] [7]

---

New guidelines were added covering the packaging of Ada programs. [8]

---

The section on Boostrapping in the Treatment of Bundled Libraries page in the Packaging Guidelines has been amended to add the following:

Packages which are built in such a bootstrapping mode must not be tagged for a final release (or pushed as an update for any stable release). FPC will track the progress of approved bootstrapping exceptions via the ticket requesting the bootstrap bundling exception.

[9]

---

Macro forms of system executables (such as %{__rm}) should not be used except when there is a need to allow the location of those executables to be configurable.

[10]

---

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

Many thanks to Hans Niedermann, Jonathan Underwood, Pavel Zhukov, 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: [11]"

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

Your package translation

Noriko[1] on Mon Mar 21 23:57:43 UTC 2011 announced[2],

"Dear Fedora package maintainers

Could you all please take a few minutes and check if your packages are on the list[3]and set to allow Fedora Localization Project to translate?

  • The above packages are on the list but do not allow Fedora

Localization teams to upload the translated files. This means that these packages will not receive any translation from FLP. Please change the setting to allow FLP, or advise us if the maintainers choose having their own translation teams. In that case, the packages may be removed from the list of Fedora Project on tx.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.