No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
<references/> | <references/> | ||
===Fedora Announcement News=== | === Fedora Announcement News === | ||
The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at<ref>https://admin.fedoraproject.org/mailman/listinfo/announce</ref> | The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at<ref>https://admin.fedoraproject.org/mailman/listinfo/announce</ref> | ||
| Line 85: | Line 85: | ||
===Fedora Events=== | === 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! | 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! | ||
Revision as of 00:01, 16 December 2010
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]
Changes to the Packaging Guidelines
Tom "spot" Callaway announced[1]:
"Here are the latest set of changes to the Fedora Packaging Guidelines:
A new page has been added which describes how to deal with bundled libraries when you find them in your package[2]
Some clarification has been added to the sections dealing with bundled libraries, specifically that:
In this RPM packaging context, the definition of the term 'library' includes: compiled third party source code resulting in shared or static linkable files, interpreted third party source code such as Python, PHP and others. At this time JavaScript intended to be served to a web browser is specifically exempted from this but this will likely change in the future[3]
Also, a note was added to make it clear that multiple licensing scenarios may be a good indicator of a bundled library situation[4]
A section has been added to the Packaging:Guidelines#Changelog entry describing the acceptable methods of having multiple changelog entries per release[5]
A new example of a reason an exception for bundling libraries might be granted has been added to the guidelines. If the library is being bundled because it is a snapshot of a newer release of the library needed for new features, you may have grounds for an exception. See the complete policy for details on when an exception might be granted for this reasoning[6]
Fedora has always implied that the update path from Fedora release to Fedora release and from Fedora release to updates should be maintained but there wasn't an explicit statement in the Guidelines. Well, there is now[7]
The guidelines have been updated to indicate that %doc files must not have executable permissions[8]
The section on Requiring Base Package was clarified, as the original language involving -libs packages may have been confusing[9]
These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Many thanks to Steven Garcia, Nils Philippsen, FESCo 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 hereCite error: Closing </ref> missing for <ref> tag 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
- ↑ http://lists.fedoraproject.org/pipermail/announce/2010-December/002898.html
- ↑ https://fedoraproject.org/wiki/Packaging/Treatment_Of_Bundled_Libraries
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries
- ↑ https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#Multiple_Licensing_Scenarios
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Multiple_Changelog_Entries_per_Release
- ↑ https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Needing_unreleased_features
- ↑ https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Package_Versioning
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation
- ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
Call for Fedora 15 Test Days
Adam Williamson announced[1]:
"Hi, everyone! I've already spoken to some developers with big features for F15 to arrange Test Days, but I just wanted to send out a general call to remind developers that the Test Day process is available for any big changes you have landing for F15 (or even little changes, we're not fussy :>). Test Days are testing events where we co-ordinate a set of test cases, and special test images if this is needed / helpful, and try to get a group of testers plus developers online on IRC around the same time to help do some well-organized testing with a short feedback loop between testers and developers. The QA group can organize the event for you (we just tell you when to show up on IRC), help you organize the event, or get out of the way and let you do it yourself - whatever you like.
Here's how the schedule looks so far[2]
It's quite pencil-y right now, so if you really want one of the already-taken days, we can probably arrange it. We can also run Test Days on days other than Thursday if necessary, but we try not to run too many in a single week, and stick to Thursdays when we can as it's quite a convenient day.
Let me know if you have any questions. Thanks!
Here's the Test Day SOP, which tells you how to put a test day together[3]"
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): none
- Europe, Middle East, and Africa (EMEA)[2]
- India, Asia, Australia (India/APJ)[3]
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.