FWN/Beats/Announcements: Difference between revisions

Revision as of 18:15, 30 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]

↑ https://admin.fedoraproject.org/mailman/listinfo/announce

Changes to the Packaging Guidelines

Tom 'Spot' Callaway announced^[1],

"Here are the changes to the Fedora Packaging Guidelines for this week:

The Packaging:PHP guidelines have been updated to reflect that PEAR documentation provided by upstream are installed in %{pear_docdir}, should stay there, and must be marked as %doc.

Additionally, the definition of pear_docdir has been defined as %{_docdir}/pear.

https://fedoraproject.org/wiki/Packaging:PHP

---

The Java guidelines have been updated to add information and sample template for Maven 3 (Fedora 15+).

https://fedoraproject.org/wiki/Packaging:Java

---

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

Many thanks to Remi Collet, Stanislav Ochotnicky, 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 ^[2]

Thanks,

~spot"

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

↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce

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?

setuptool: ^[4]
pam_krb5: ^[5]
pkinit-nss: ^[6]

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]

↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents

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.

@@ Line 14: / Line 14: @@
 <references/>
-====Fedora accepted in to Google Summer of Code 2011!====
+====Changes to the Packaging Guidelines====
-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:Spot|Tom 'Spot' Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-March/002942.html</ref>,
-"Heya folks :)
+"Here are the changes to the Fedora Packaging Guidelines for this week:
-So... after a year's hiatus, Fedora's been accepted in to Google's Summer of
+The Packaging:PHP guidelines have been updated to reflect that PEAR
-Code program for summer 2011!
+documentation provided by upstream are installed in %{pear_docdir},
+should stay there, and must be marked as %doc.
-If you're a university student looking for a job this summer, start thinking
+Additionally, the definition of pear_docdir has been defined as %{_docdir}/pear.
-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!
-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
+https://fedoraproject.org/wiki/Packaging:PHP
-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!"
-<references/>
-====[Guidelines Change] Changes to the Packaging Guidelines====
-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>
----
-The Scriptlet Snippets section dealing with the order that scriptlets
-are invoked has been updated to include %trigger scripts.
-<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
+The Java guidelines have been updated to add information and sample template for Maven 3 (Fedora 15+).
-in the Packaging Guidelines has been amended to add the following:
-Packages which are built in such a bootstrapping mode must not be tagged
+https://fedoraproject.org/wiki/Packaging:Java
-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
+These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
-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>
+Many thanks to Remi Collet, Stanislav Ochotnicky, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.
----
-These guidelines (and changes) were approved by the Fedora Packaging
+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
-Committee (FPC).
+<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
-Many thanks to Hans Niedermann, Jonathan Underwood, Pavel Zhukov, and
+Thanks,
-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
+~spot"
-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/>

Search