From Fedora Project Wiki

< FWN‎ | Beats

(Development beat done)
No edit summary
 
(116 intermediate revisions by 2 users not shown)
Line 2: Line 2:
==Announcements==
==Announcements==


In this section, we cover announcements from the Fedora Project, including general announcements<ref>
Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements<ref>http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Fedora Events<ref>http://fedoraproject.org/wiki/Events</ref>.
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.


Contributing Writer: [[User:Rashadul|Rashadul Islam]]
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>


=== Fedora Announcement News ===
===Breaking News of the Week and Month===
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>


<references/>
====[Guidelines Change] Changes to the Packaging Guidelines==== 


====FUDCon EMEA Bidding now open==== 
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>


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>,
"A new section has been added to the SysV Initscripts section, discussing
the proper use of subsys locking. Even though Fedora packages should no
longer be using SysV Initscripts as a primary service mechanism, Red Hat
Enterprise Linux and EPEL do. Additionally,
Red Hat points partners to the Fedora Guidelines when they build for RHEL.
<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref>


"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<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.
The review guidelines now reflect the use of sha256sum (instead of
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>


We look forward to seeing your proposals!"
---


<references/>
The PHP Packaging guidelines have been updated to include guidance about
when it is appropriate to have an explicit Requires on httpd & mod_php,
how to handle explicit Requires on PHP extensions, and how to handle a
Requires for a minimum PHP version.
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>


====[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:
A new section on Macros has been added to the Packaging Guidelines,
covering Packaging of Additional RPM Macros.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>


---
---
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>


---
A new section on the Documentation= field in systemd unit files (F17+)
Many implementations of md5 originate in a program and then end up
has been added.
copied to other programs with compatible license terms.  These
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
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
A short section on the Group tag in Fedora packages has been added.
where it does matter:
All current versions of Fedora (and their respective RPM versions) treat
the Group tag as optional. Packages may include a Group: field for
compatibility with EPEL, but are not required to do so.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>


* 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
The RHEL conditionalization has been removed from the Python3 example
reflect that %{?_isa} must be used for Explicit Requires and Provides
spec file, as it is no longer valid.
that match those situations.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


<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>


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


Previously, there was a change made to the Documentation guidelines
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these 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.
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>"


In addition, %doc files must not have executable permissions.
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>


This has been revised to:
<references/>


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).
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 


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.
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Documentation</ref>
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>


---
"Greetings! (...or perhaps I should say.... bonjour!)
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.
I'd like to share a few reminders and announcements regarding the  
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Test_Suites</ref>
If you are planning to attend FUDCon and need a travel subsidy to do so,
the ticketing system is now open for those requests.  Requests will be
accepted through August 15, 2012. Please note that funding requests
without a ticket will not be considered. Preference will be given to
attendees from the EMEA region who are actively contributing to Fedora,
and have detailed their participation plans for FUDCon in their request.


---
To place a subsidy request, please follow these steps:
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>
1: Pre-register at
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
put an X in the $$$ column
2: Read about the funding request process and place a funding request
ticket in the FUDCon-planning ticket tracker here:
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>


---
Additionally, a few notes regarding the hotel in Paris:
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
There are other events in Paris during this time period; most notably,
assisting in drafting, refining, and passing these guidelines.
our first day of FUDCon will be taking place at the Open World Forum
conference, on the day in which the public is encouraged to participate
in and learn about open source projects.  OWF had nearly 2000 attendees
last year.  Accordingly, rooms might be in short supply as we approach
FUDCon; please, book your hotel as soon as possible, not only for  
affordability purposes, but also so that you have a bed to sleep in. :)


As a reminder: The Fedora Packaging Guidelines are living documents! If
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
you find something missing, incorrect, or in need of revision, you can
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
suggest a draft change. The procedure for this is documented here:
However, this rate will expire at the end of August, and any remaining
<ref>http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
rooms in our block will expire.


For instructions on booking your hotel, please read the Lodging/Hotel
section of the FUDCon: Paris wiki:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>
<references/>


====Updating SSL keys on fedorahosted.org====   
====Fedora Infrastructure announces status.fedoraproject.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.
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>


The first server to be updated will be fedorahosted.org.
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


The old certificate came from Equifax, was a 1024 bit key and had the fingerprint:
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


SHA1 Fingerprint=CC:64:67:BE:90:50:79:ED:23:E8:C1:18:02:AB:AC:83:88:FC:6C:D8
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


The new certificate is issued by GeoTrust, Inc and is a 4096 bit key with the fingerprint:
If you run into a problem or issue that is not reflected at
status.fedoraproject.org, please do report it to us in #fedora-admin on
irc.freenode.net or via ticket at
<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref>
We update the site status information manually so we need to be aware
of the issue in order to keep the site accurate.


SHA1 Fingerprint=D1:54:82:77:77:F9:11:DF:E0:B1:14:37:B9:36:E2:09:20:B6:54:1D
As with everything in Fedora Infrastructure, this application is open
source. Source is available from:
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
and is released under a '''GPLv2+ license'''.


Please report any problems with these certificates to '''admin at fedoraproject.org'''"
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
issues with outages in our infrastructure affecting status reporting. "


<references/>
<references/>


====GSoC 2011 Ideas Needed!====  
====Beats are open!====


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>,
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>


"Hey guys gals and other hackerfolk!
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


Google's Summer of Code is coming up ever so close. We have 20 days until the
If you're looking for a way to dip your toes in the water, so to
org application opens up, and we need a '''LOT''' more ideas if we are going to  
speak, writing a beat is a great way to get started. If you're a
have any hope of being accepted. I know there are a lot of awesome ideas out
regular, don't forget about the checkBeat program:
there in the community, we just need folks to step up and tell us about them.  
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
It's free labour, and a great chance to attract new Fedora contributors.  


So, folks, go add ideas to the Ideas page at:
As a reminder, the wiki drafts of beats are due on 12 September."
<ref>https://fedoraproject.org/wiki/Summer_coding_ideas_for_2011</ref>"


<references/>
<references/>


=== Fedora Development News ===
=== Fedora Development News ===
 
The Development Announcement<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
The development list<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref> is intended to be a LOW TRAFFIC announce-only list for Fedora development.


'''Acceptable Types of Announcements'''
'''Acceptable Types of Announcements'''
Line 175: Line 194:
<references/>
<references/>


====Mass rebuild starting monday Feb 7====  
====New bodhi release in production====
 
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
 
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>
 
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


The two separate threat has been made for the announcement of '''Mass rebuild starting monday Feb 7'''.  
Major changes in bodhi 0.9.2
---------------------------------


Dennis Gilmore<ref>Dennis Gilmore dennis at ausil.us</ref> on Sat Feb 5 06:00:07 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-February/000751.html</ref>,
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


"for gcc-4.6, xz compression changes, and to a lesser extent we will be doing a
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
mass rebuild starting monday. it will be done in a side tag with a lower than
normal priority so that you can still submit builds and not have to wait for
the mass rebuild to finish. we will then tag into  rawhide the builds after
unless you do a build in the meantime


* The submitter of an update can no longer effect the karma (Till Maas)


Please note that mass branching will be occuring soon after the mass rebuild
* Fix duplicate status change email notifications. (Till Maas)
as the Alpha freeze is 2011-02-15"


Peter Robinson<ref>Peter Robinson pbrobinson at gmail.com</ref> on Sun Feb 6 20:31:01 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-February/000752.html</ref>,
* Mention age of updates in testing digest mails (Till Maas)


"Can we ensure that the fix for the NOPL issue on Geode processors gets
* Support e-mail threading in notification e-mails (Till Maas)
in before the mass rebuild to ensure we don't have any issues with
 
packages using that instruction in the XO-1."
* Add X-Bodhi mail headers (Till Maas)
 
* Gracefully handle private bugs (Cole Robinson)
 
* Set the default request for new updates to 'testing' in the web form
 
* Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
 
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
 
 
Full list of changes since 0.8.7
--------------------------------
 
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579
 
Luke Macken (25):
      Convert our tags_url to a byte string before passing it to urlgrabber.
      Add a script to detect when older builds become the 'latest' in stable
      Update our test suite to reproduce ticket [ticket:683]
      Fix a bug in our critpath policy ([ticket:683]).
      Set the default request for new updates to 'testing'
      Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
      Fix a busted unit test (test_push_EPEL_critpath_before_tested)
      Add pkg_resources __requires__ hacks to bodhi tools to mitigate version
conflicts
      Handle the case where a release doesn't have any overrides
      Change our X-Bodhi-Update-Release header to use the short name
      Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
      Update our unit tests to assume submitters cannot alter karma
      Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
      Merge branch 'feature/bodhi1-fedmsg' into develop
      Fix a typo in the metrics tool
      Fix a typo in the new mail headers
      Re-organize our links, and add one to the new update feedback guidelines
      Clean up stray buildroot overrides
      Version bump for 0.9.2
      Our build script uses bz2
      Merge branch 'release/0.9.2'
 
Mathieu Bridon (6):
      Have bodhi-init create all the tables
      masher: Fix the comparison
      masher: Reuse variable
      setup: Fix the Turbogears version requirement
      Don't version control auto-generated files
      setup: Add missing dependencies
 
Ralph Bean (19):
      Sending messages with fedmsg.
      No longer using fedmsg schema/validation.
      fedmsg.ini -> fedmsg-config.py
      More detail in the update.complete message.
      More concise send_message calls.
      Ignore dev db.
      Merge branch 'master' into bodhi1-fedmsg
      Updates for the latest fedmsg.  Getting tests passing.
      Merge branch 'master' into bodhi1-fedmsg
      Ignore mashing fedora file.
      Fixed what I think is a regression in login template.
      Merge branch 'master' into bodhi1-fedmsg
      Update to test fedmsg config.  Work with both tests and under WSGI.
      Version bump for fedmsg in staging.
      Only send the comment with a comment is added, not the whole update.
      Using a "bodhi" user/group for mod_wsgi.
      fedmsg+ssl changes to bodhi.spec.
      Use modern fedmsg config format.
      Disable message signing for bodhi tests.
 
Till Maas (8):
      Add X-Bodhi mail headers
      Support e-mail threading in notification e-mails
      Mention age of updates in testing digest mails
      Use format string instead of string concatenation
      Import exceptions from sqlite3
      Remove files used by mercurial
      model.py: Change karma from Submitter to 0
      Fix notification on automatic status change"


<references/>
<references/>
====Build F-18 collection packages for all language translators====
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>
"Hi Fedora package maintainers
Please build and push your package with latest translation file (e.g.
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
Your packages with latest translation will be composed into test live
image on 3-Sep Monday. Then various language translators worldwide will
test the image in their own languages. Any issue will be filed as bug.
This is only one chance for translators to check and modify Localization
quality of your packages by checking UI, and we need your help.
Thank you so much.
noriko
Fedora Localization Project"
<references/>
====Fedora 18 Alpha to slip by another one week====
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
"Today at Go/No-Go meeting it was decided to slip Fedora 18
Alpha release by one week due to remaining open blocker bugs<ref>http://qa.fedoraproject.org/blockerbugs/current</ref> and incomplete test matrices for Alpha <ref>https://fedoraproject.org/wiki/Test_Results:Current_Base_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test</ref>. Meeting's
full log is at <ref>http://bit.ly/PC16PF</ref>.
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
will be pushed out by one week.
The next Go/No-Go meeting is on Thursday Sep 06, same place
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).
If you have an accepted blocker bug, please try to fix it
as soon as possible to help us with Fedora 18 Alpha release!"
<references/>


=== 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!
The purpose of Fedora 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 and press releases.


====Upcoming Events (Dec 2010 - Feb 2011)====
====Upcoming Events (September 2012 - November 2012)====
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29</ref>
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_2</ref>
* '''Central & South America (LATAM)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_2</ref>
* '''Europe, Middle East, and Africa (EMEA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q4_.28Dec._2010_-_Feb._2011.29_3</ref>
* '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref>
 
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>


<references/>
<references/>
Line 223: Line 372:
* [[Event reports]] -- guidelines and suggestions.
* [[Event reports]] -- guidelines and suggestions.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
===Fedora Press Releases===
Fedora press releases will be found at the link:
http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Latest revision as of 11:18, 31 August 2012

Announcements

Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
  3. ↑ http://fedoraproject.org/wiki/Events

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

  • Contributor: [[User:Spot|Tom Callaway][1]
  • Posted Date: Wed Aug 1 19:28:57 UTC 2012[2]

"A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. [3]

---

The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. [4]

---

The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. [5] [6] [7]

---

A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. [8]

---

A new section on the Documentation= field in systemd unit files (F17+) has been added. [9]

---

A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. [10]

---

The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. [11]

---

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

Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, 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]"

Enclosure: Here is one late change to the Fedora Packaging Guidelines:[13] [14] [15]

  1. ↑ Tom Callaway tcallawa at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html
  3. ↑ https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism
  4. ↑ https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review
  5. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement
  6. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires
  7. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version
  8. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros
  9. ↑ https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field
  10. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag
  11. ↑ https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file
  12. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
  13. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html
  14. ↑ https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
  15. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

  • Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron][1]
  • Posted Date: Fri Aug 3 17:00:53 UTC 2012[2]

"Greetings! (...or perhaps I should say.... bonjour!)

I'd like to share a few reminders and announcements regarding the upcoming FUDCon in Paris, France, on October 13-15, 2012.

If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request.

To place a subsidy request, please follow these steps:

1: Pre-register at [3] - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: [4]

Additionally, a few notes regarding the hotel in Paris:

There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :)

We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire.

For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: [5]"

  1. ↑ rbergero at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html
  3. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration
  4. ↑ https://fedorahosted.org/fudcon-planning/wiki/FundingRequest
  5. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel

Fedora Infrastructure announces status.fedoraproject.org

  • Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ][1]
  • Posted Date: Thu Aug 30 20:31:24 UTC 2012[2]

"I'm happy to announce the general availability of our status.fedoraproject.org site.

This site provides an easy way for Fedora contributors and users to check on the status of services provided by Fedora Infrastructure.

The site auto reloads every minute, and also provides a rss feed at [3].

If you run into a problem or issue that is not reflected at status.fedoraproject.org, please do report it to us in #fedora-admin on irc.freenode.net or via ticket at [4] We update the site status information manually so we need to be aware of the issue in order to keep the site accurate.

As with everything in Fedora Infrastructure, this application is open source. Source is available from: [5] and is released under a GPLv2+ license.

This application is hosted at the link[6] to avoid any issues with outages in our infrastructure affecting status reporting. "

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html
  3. ↑ http://status.fedoraproject.org/changes.rss of any changes
  4. ↑ https://fedorahosted.org/fedora-infrastructure/newticket
  5. ↑ http://git.fedorahosted.org/git/fedora-status.git
  6. ↑ https://openshift.redhat.com

Beats are open!

  • Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton][1]
  • Posted Date: Tue Aug 28 15:35:59 UTC 2012[2]

"The Release Notes beats for Fedora 18 are now open: [3]

If you're looking for a way to dip your toes in the water, so to speak, writing a beat is a great way to get started. If you're a regular, don't forget about the checkBeat program: [4]

As a reminder, the wiki drafts of beats are due on 12 September."

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html
  3. ↑ https://fedoraproject.org/wiki/Category:Documentation_beats
  4. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html

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
  1. ↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce

New bodhi release in production

  • Contributor: [[User:Lmacken|Luke Macken ][1]
  • Posted Date: Thu Aug 9 21:53:41 UTC 2012[2]

"A new release of Bodhi has just been deployed to production. [3]

Bugs and enhancement requests can be filed here: [4]

Major changes in bodhi 0.9.2

  • fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  • Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  • The submitter of an update can no longer effect the karma (Till Maas)
  • Fix duplicate status change email notifications. (Till Maas)
  • Mention age of updates in testing digest mails (Till Maas)
  • Support e-mail threading in notification e-mails (Till Maas)
  • Add X-Bodhi mail headers (Till Maas)
  • Gracefully handle private bugs (Cole Robinson)
  • Set the default request for new updates to 'testing' in the web form
  • Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  • Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Full list of changes since 0.8.7

Kalpa Welivitigoda (1): 

     fixed input box alignment issue in login box #579

Luke Macken (25): 

     Convert our tags_url to a byte string before passing it to urlgrabber.
     Add a script to detect when older builds become the 'latest' in stable
     Update our test suite to reproduce ticket [ticket:683]
     Fix a bug in our critpath policy ([ticket:683]).
     Set the default request for new updates to 'testing'
     Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
     Fix a busted unit test (test_push_EPEL_critpath_before_tested)
     Add pkg_resources __requires__ hacks to bodhi tools to mitigate version

conflicts 

     Handle the case where a release doesn't have any overrides
     Change our X-Bodhi-Update-Release header to use the short name
     Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
     Update our unit tests to assume submitters cannot alter karma
     Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
     Merge branch 'feature/bodhi1-fedmsg' into develop
     Fix a typo in the metrics tool
     Fix a typo in the new mail headers
     Re-organize our links, and add one to the new update feedback guidelines
     Clean up stray buildroot overrides
     Version bump for 0.9.2
     Our build script uses bz2
     Merge branch 'release/0.9.2'

Mathieu Bridon (6): 

     Have bodhi-init create all the tables
     masher: Fix the comparison
     masher: Reuse variable
     setup: Fix the Turbogears version requirement
     Don't version control auto-generated files
     setup: Add missing dependencies

Ralph Bean (19): 

     Sending messages with fedmsg.
     No longer using fedmsg schema/validation.
     fedmsg.ini -> fedmsg-config.py
     More detail in the update.complete message.
     More concise send_message calls.
     Ignore dev db.
     Merge branch 'master' into bodhi1-fedmsg
     Updates for the latest fedmsg.  Getting tests passing.
     Merge branch 'master' into bodhi1-fedmsg
     Ignore mashing fedora file.
     Fixed what I think is a regression in login template.
     Merge branch 'master' into bodhi1-fedmsg
     Update to test fedmsg config.  Work with both tests and under WSGI.
     Version bump for fedmsg in staging.
     Only send the comment with a comment is added, not the whole update.
     Using a "bodhi" user/group for mod_wsgi.
     fedmsg+ssl changes to bodhi.spec.
     Use modern fedmsg config format.
     Disable message signing for bodhi tests.

Till Maas (8): 

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial
     model.py: Change karma from Submitter to 0
     Fix notification on automatic status change"
  1. ↑ lmacken at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html
  3. ↑ https://admin.fedoraproject.org/updates
  4. ↑ http://bodhi.fedorahosted.org

Build F-18 collection packages for all language translators

  • Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto][1]
  • Posted Date: Thu Aug 30 09:17:01 UTC 2012[2]

"Hi Fedora package maintainers

Please build and push your package with latest translation file (e.g. pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. Your packages with latest translation will be composed into test live image on 3-Sep Monday. Then various language translators worldwide will test the image in their own languages. Any issue will be filed as bug. This is only one chance for translators to check and modify Localization quality of your packages by checking UI, and we need your help.

Thank you so much.

noriko Fedora Localization Project"

  1. ↑ noriko.mizumoto at gmail.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html

Fedora 18 Alpha to slip by another one week

  • Contributor: [[User:JaroslavReznik|Jaroslav Reznik][1]
  • Posted Date: Thu Aug 30 23:26:35 UTC 2012[2]

"Today at Go/No-Go meeting it was decided to slip Fedora 18 Alpha release by one week due to remaining open blocker bugs[3] and incomplete test matrices for Alpha [4][5][6]. Meeting's full log is at [7].

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week.

The next Go/No-Go meeting is on Thursday Sep 06, same place but different time (19:00 UTC, 3 PM EDT, 21:00 CEST

  1. fedora-meeting).

If you have an accepted blocker bug, please try to fix it as soon as possible to help us with Fedora 18 Alpha release!"

  1. ↑ jreznik at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html
  3. ↑ http://qa.fedoraproject.org/blockerbugs/current
  4. ↑ https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
  5. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
  6. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
  7. ↑ http://bit.ly/PC16PF


Fedora Events

The purpose of Fedora 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 and press releases.

Upcoming Events (September 2012 - November 2012)

  • North America (NA)[1]
  • Central & South America (LATAM)[2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Guideline to write Fedora Press Releases[5]

  1. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29
  3. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2
  4. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3
  5. ↑ https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release

Past Events

Archive of Past Fedora Events[1]

  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.

Fedora Press Releases

Fedora press releases will be found at the link: http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Announcements&oldid=300097"