No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
=== Fedora Announcements === | === Fedora Announcements === | ||
==== | ==== Changes to the Packaging Guidelines ==== | ||
[[User: | [[User:spot|Tom Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-July/002985.html</ref>: | ||
" | "Here are the latest changes to the Fedora Packaging Guidelines: | ||
--- | |||
Some rpm versions pass pathnames to the automatic filtering macros, so a | |||
section has been added to the guidelines to help packagers deal with it<ref>https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Pathnames</ref> | |||
-- | --- | ||
For a while, Fedora considered mono packages to be | |||
architecture-specific, and installed assemblies to %{_libdir}. However, | |||
after discussions with upstream, we now consider mono packages to be | |||
architecture (and platform) independent. This means that mono packages | |||
should be correctly installed into the GAC in /usr/lib or installed into | |||
/usr/lib/PACKAGENAME. | |||
As a notable exception, any ELF binary libraries generated in a mono | |||
package must be correctly installed into %{_libdir}, because these files | |||
are architecture-specific. | |||
" | Also, even though we consider mono packages to be architecture | ||
independent, they must not be marked as "noarch". Although the | |||
assemblies are the same, the files may differ due to strings referring | |||
to the build architecture.<ref>https://fedoraproject.org/wiki/Packaging:Mono#File_Locations</ref> | |||
--- | |||
It was decided that gnome shell extension packages should have the | |||
prefix gnome-shell-extension (with no "s" on the end).<ref>https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28gnome_shell_extensions.29</ref> | |||
--- | |||
The section in the Fedora Packaging Guidelines concerning libexecdir has | |||
been improved and expanded<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir</ref>. | |||
--- | |||
The Fedora Java Packaging Guidelines have been updated to reflect the | |||
latest macros for Maven 3.<ref>https://fedoraproject.org/wiki/Packaging:Java</ref> | |||
--- | |||
These guidelines (and changes) were approved by the Fedora Packaging | |||
Committee (FPC). | |||
Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar, | |||
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<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>. | |||
Thanks, | |||
~spot" | |||
<references/> | <references/> | ||
| Line 113: | Line 91: | ||
<references/> | <references/> | ||
==== Fedora 16 | ==== Call for Test Days for Fedora 16 ==== | ||
[[User: | [[User:Adamw|Adam Williamson]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-July/000813.html</ref>: | ||
" | "Hi, folks. The Test Day cycle for Fedora 16 will open shortly, and we're putting out the call for anyone who has an idea for a Test Day. There are many open slots on the schedule<ref>https://fedoraproject.org/wiki/QA/Fedora_16_test_days</ref> - and if they all fill up or you would like to run a set of Test Days on related topics, we can organize events outside of the scheduled Thursday windows too. | ||
It's often a good idea to have a Test Day for a major change or new feature you're introducing to the distribution, but we can run a Test Day on just about any topic. There is a full guide to organizing Test Days available<ref>https://fedoraproject.org/wiki/QA/SOP_Test_Day_management</ref> - and the QA team is happy both to help you run a Test Day and to butt out and let you run it yourself, whichever you prefer! If you're interested in running a Test Day, please contact QA via the test mailing list, file a ticket in QA trac<ref>https://fedorahosted.org/fedora-qa</ref> and/or pencil in your event on the schedule, create a Wiki page based on the template (see the SOP for details), and get down to work. Thanks! | |||
-- | |||
Adam Williamson | |||
Fedora QA Community Monkey | |||
IRC: adamw | |||
http://www.happyassassin.net" | |||
<references/> | <references/> | ||
Revision as of 13:10, 21 July 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 Announcements
Changes to the Packaging Guidelines
Tom Callaway announced[1]:
"Here are the latest changes to the Fedora Packaging Guidelines:
---
Some rpm versions pass pathnames to the automatic filtering macros, so a section has been added to the guidelines to help packagers deal with it[2]
---
For a while, Fedora considered mono packages to be architecture-specific, and installed assemblies to %{_libdir}. However, after discussions with upstream, we now consider mono packages to be architecture (and platform) independent. This means that mono packages should be correctly installed into the GAC in /usr/lib or installed into /usr/lib/PACKAGENAME.
As a notable exception, any ELF binary libraries generated in a mono package must be correctly installed into %{_libdir}, because these files are architecture-specific.
Also, even though we consider mono packages to be architecture independent, they must not be marked as "noarch". Although the assemblies are the same, the files may differ due to strings referring to the build architecture.[3]
---
It was decided that gnome shell extension packages should have the prefix gnome-shell-extension (with no "s" on the end).[4]
---
The section in the Fedora Packaging Guidelines concerning libexecdir has been improved and expanded[5].
---
The Fedora Java Packaging Guidelines have been updated to reflect the latest macros for Maven 3.[6]
---
These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar, 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[7].
Thanks,
~spot"
- ↑ http://lists.fedoraproject.org/pipermail/announce/2011-July/002985.html
- ↑ https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Pathnames
- ↑ https://fedoraproject.org/wiki/Packaging:Mono#File_Locations
- ↑ https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28gnome_shell_extensions.29
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir
- ↑ https://fedoraproject.org/wiki/Packaging:Java
- ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
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
Call for Test Days for Fedora 16
Adam Williamson announced[1]:
"Hi, folks. The Test Day cycle for Fedora 16 will open shortly, and we're putting out the call for anyone who has an idea for a Test Day. There are many open slots on the schedule[2] - and if they all fill up or you would like to run a set of Test Days on related topics, we can organize events outside of the scheduled Thursday windows too.
It's often a good idea to have a Test Day for a major change or new feature you're introducing to the distribution, but we can run a Test Day on just about any topic. There is a full guide to organizing Test Days available[3] - and the QA team is happy both to help you run a Test Day and to butt out and let you run it yourself, whichever you prefer! If you're interested in running a Test Day, please contact QA via the test mailing list, file a ticket in QA trac[4] and/or pencil in your event on the schedule, create a Wiki page based on the template (see the SOP for details), and get down to work. Thanks!
-- Adam Williamson Fedora QA Community Monkey IRC: adamw 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 (June - August 2011)
- North America (NA)[1]
- Central & South America (LATAM): [2]
- Europe, Middle East, and Africa (EMEA)[3]
- India, Asia, Australia (India/APJ)[4]
- ↑ http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29
- ↑ http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_2
- ↑ http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_3
- ↑ http://fedoraproject.org/wiki/Events#FY12_Q2_.28June_2011_-_August_2011.29_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.