From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
 
(226 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]]  and/or [[User:Pcalarco|Pascal Calarco]]  
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>


=== Fedora Announcement News ===
===Breaking News of the Week and Month===
====Fedora 11 End of Life====
[[User:Pfrields|Paul W. Frields]], Fedora Project Leader, announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-June/002830.html</ref>, "This announcement is a reminder that as of 2010-06-25, Fedora 11 has reached its end of life for updates.  As planned, last update pushes to Fedora 11 were made in advance<ref>http://lists.fedoraproject.org/pipermail/devel/2010-June/137849.html</ref> of this date.  No further
updates, including security updates, will be available for Fedora 11.


Fedora 12 will continue to receive updates until approximately one month after the release of Fedora 14. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki<ref>https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule</ref>."
====[Guidelines Change] Changes to the Packaging Guidelines==== 
 
* 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>
 
"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>
 
---
 
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>
 
---
 
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>
 
---
 
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>
 
---
 
A new section on the Documentation= field in systemd unit files (F17+)
has been added.
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
 
---
 
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.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>
 
---
 
The RHEL conditionalization has been removed from the Python3 example
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
 
---
 
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:
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
 
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>


<references/>
<references/>


====Deadline for T-Shirt Registration FUDCon Zurich 2010====
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  
 
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</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!)
 
I'd like to share a few reminders and announcements regarding the
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


[[User:jsimon|Joerg Simon]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-June/002831.html</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.


"Dear Fellows,
To place a subsidy request, please follow these steps:


If you plan to attend the FUDCon EMEA in Zurich September 17 - 19, 2010
1: Pre-register at
- and want to pick up a pretty FUDCon-Shirt - designed by Maria (tatica)
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
Leandro - do not forget to register it<ref>
put an X in the $$$ column
https://fedoraproject.org/wiki/FUDCon:Zurich_2010_Pre-registration</ref>
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>


The Deadline for ordering a FUDCon-Shirt is 2010-June-30 12:00 UTC!!!
Additionally, a few notes regarding the hotel in Paris:


After this you can still register yourself for FUDCon but we can not assure you a Shirt matching your Size."
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:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>
<references/>


====Passing the baton====
====Fedora Infrastructure announces status.fedoraproject.org====  
 
* 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>


[[User:Pfrields|Paul W. Frields]], Fedora Project Leader, announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-June/002832.html</ref>:
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


"A leadership change is always momentous, and the Fedora Project is no exception to this rule.  I wanted to share some thoughts about being the Fedora Project Leader, tell the community about the person who will be taking over that role soon, and to let you know what to expect over the next few weeks and months.
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
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


I joined the Fedora Project in 2003 so I could give something back to a free software community from whose work I had benefited for a long time. Fedora gave me the chance to bring my skills and experience and use them to help people I'd never get a chance to meet personally. I had no inkling at the time that one day I'd have the opportunity to serve the community beyond helping write some documentation.
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.


When Max Spevack called me in late 2007 to let me know he was considering stepping down, and was interested in having me succeed him as the Fedora Project Leader, I was surprised and humbled. It was a once in a lifetime opportunity to both serve the community and to contribute as an employee at Red Hat, where I had already made many friends while working on Fedora -- an opportunity I was happy to take. Over the past two and a half years, through many challenges and changes, not once have I regretted that decision.
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'''.  


* * *
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. "


One of the hallmarks of Fedora leadership is that it's open to change. The FPL is not a semi-benevolent dictator for life, but rather a position to which new people can regularly bring their passion for making Fedora better.  And so, just as previous FPLs announced their readiness to search for the next leader, I did so a few months ago, in the spirit of openness and transparency that's a hallmark of the Fedora community.
<references/>


The FPL job is a salaried position at Red Hat, and the Fedora Board members as well as many other stakeholders have been informed and involved with the process of selecting a new FPL.  The job posting brought in numerous applicants from throughout the community.  Through the hiring process we identified a few best qualified candidates. From them the next FPL was selected, based on the qualifications and experience our entire community expects.  At every juncture during that process, the panels were focused on the needs of the Fedora Project, to ensure the next FPL would be a good listener, speaker, and writer; thoughtfully consider solutions to difficult problems; and most importantly, lead effectively.
====Beats are open!====


So it's with great pleasure that I announce Jared Smith will be joining Red Hat in a few weeks as the new Fedora Project Leader.
* 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>


* * *
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


Some of our community already knows Jared, but I want to take a moment to tell everyone a little more about his background. He doesn't like to trumpet his own qualifications, but since he happens to be away on personal business this week, I'll just do that for him. :-)
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:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


Jared's been a long-time user of both Red Hat and Fedora, and an active participant in the the Fedora community since 2007.  He's primarily spent his time working with the infrastructure and documentation teams.  He's helped with the development of Fedora Talk, our community VoIP telephony system.  Fedora Talk allows various Fedora developers and contributors to communicate verbally for free across the internet.
As a reminder, the wiki drafts of beats are due on 12 September."


Jared has also participated in community events such as various FUDCons and Fedora Activity Days.  In addition, he has assisted with toolchain development, release materials, and steering duties as a member of the Fedora Docs team.
<references/>


Jared also brings a wealth of of both technical and community relations expertise from his prior job history. His previous employer is Digium, the commercial sponsor of the open source Asterisk software.  While at Digium, Jared worked as Community Relations Manager, as well as an instructor, lecturer, and training department manager.
=== 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.


Before working for Digium, Jared was a Network Operations Manager for the web analytics company Omniture (since acquired by Adobe Systems), where he managed a network of over 6,500 Linux machines. These experiences as a speaker, evangelist, practitioner, and collaborator make Jared exceptionally well suited for the position of FPL.
'''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


On a more personal note, I've come to know Jared well over the past several years.  He cares deeply about community and family, not the least part of which is the Fedora community and family.  His honesty, integrity, good humor, patience, intelligence, and good old-fashioned common sense will serve him and our growing community well, as we try to take Fedora to the next level.
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


* * *
<references/>


Although Jared is away on personal travel right now, Max and I have already started including him in some important conversations, and the community can expect additional exciting news shortly.  Over the next few months, part of my changing responsibilities in Red Hat will be to ensure a smooth runway for Jared, as he takes over the duties of the FPL job.  Max Spevack will also continue to assist, especially where his role as the manager of Red Hat's Community Architecture team brings strategic benefits to the Fedora Project.
====New bodhi release in production====


Over time, I expect to spend more time on work that's internal to Red Hat, but I will continue to be involved in Fedora to some extent as an individual contributor. That transition will allow Jared to effectively bring his own vision and energy to Fedora, and I look forward to helping him in whatever ways I can.
* 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>


I hope the entire community will join me in welcoming Jared to Red Hat as the FPL, and that you'll gift him with the support and friendship I've enjoyed and treasured over the past two and a half years."
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>


<references/>
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>
 
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)


====FPL travel to LATAM events!====
* Add X-Bodhi mail headers (Till Maas)


[[User:Pfrields|Paul W. Frields]], Fedora Project Leader, announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-June/002833.html</ref>:
* Gracefully handle private bugs (Cole Robinson)


"In just a few weeks, the Fedora community in Latin America will hold a major FUDCon event in Santiago, Chile, from July 15-17, 2010.  You can find all the details on our wiki<ref>https://fedoraproject.org/wiki/FUDCon:Santiago_2010</ref>
* Set the default request for new updates to 'testing' in the web form


Encouraging the growth of Fedora community around the world is important to our project.  That's why the responsibilities of the Fedora Project Leader include lowering barriers and advocating for involvement and participation.  One of the ways the FPL does this is by travelling to different community events and talking about the way that Fedora works, and our dedication to sustainable community and
* 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.
free software development.


So I'm very pleased and excited to announce that our new Fedora Project Leader Jared Smith's first appearance at a community event will be at the FUDCon in Santiago, Chile.  In addition, just a few days afterward Jared will attend the FISL 11 conference in Porto Alegre, Brazil.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Both events represent a unique opportunity for the Fedora Project to support our friends and extend our community in Latin America.  As always, the FUDCon event in Santiago is free and open to everyone to register and attend.  We look forward to seeing the community at these events!


You can find more information about Jared<ref>http://press.redhat.com/2010/06/29/introducing-fedora-project-leader-jared-smith/</ref>"
Full list of changes since 0.8.7
--------------------------------


<references/>
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


===Fedora Development News===
Luke Macken (25):
====Bodhi 0.7.5 release====
      Convert our tags_url to a byte string before passing it to urlgrabber.
Luke Macken announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-June/000626.html</ref>:
      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'


"I just pushed a version 0.7.5 of bodhi into production.  This release
Mathieu Bridon (6):
contains the following notable changes:
      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


proventesters & strict critical path update handling
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.


For critical path<ref>https://fedoraproject.org/wiki/Critical_Path_Packages</ref> updates to be approved for pushing to the stable repository, they now require a minimum karma of 2, consisting of a +1
Till Maas (8):
from a single proventester<ref>https://fedoraproject.org/wiki/QA/JoinProvenTesters</ref>, and a +1 from another authenticated user.
      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"


You can get a list of critical path updates using the bodhi web interface<ref>https://admin.fedoraproject.org/updates/critpath?release=F13&untested=True</ref>
<references/>


You can optionally pass in a specific 'release' or an 'untested' flag,
====Build F-18 collection packages for all language translators====
which will return a list of critical path updates that have yet to be
approved.  I have not added these links to the main interface yet,
because at the moment they are fairly expensive calls.  This will be
addressed in an upcoming release.


The latest command-line client also supports these options as well:
* 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>


    $ bodhi --critpath --untested --release F13
"Hi Fedora package maintainers


Auto-obsoletion re-enabled
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.


I re-enabled the auto-obsoletion code in bodhi.  This means that new
Thank you so much.
updates will automatically obsolete older testing updates containing the
same packages.  The new update will also inherit all of the old updates
bugs and notes.  This code had been disabled for a while now, due to
some nasty edge cases, but those have since been resolved.


If you experience any problems, please file tickets here<ref>https://fedorahosted.org/bodhi/newticket</ref>"
noriko
Fedora Localization Project"


<references/>
<references/>


====Fedora 14 Feature Submission Deadline in Two Weeks====
====Fedora 18 Alpha to slip by another one week====


John Poelstra reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-June/000625.html</ref> the community of the upcoming Fedora 14 feature submission deadline:
* 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>


"Another friendly and brief reminder that the deadline for new features
"Today at Go/No-Go meeting it was decided to slip Fedora 18
for Fedora 14 is July 13, 2010.
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>.  


A list of features accepted so far<ref>https://fedoraproject.org/wiki/Releases/14/FeatureList</ref>
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
will be pushed out by one week.


Wiki pages explaining the feature process<ref>https://fedoraproject.org/wiki/Features/Policy</ref>
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).


Please send any other questions about the feature process or this
If you have an accepted blocker bug, please try to fix it
deadline by replying to this message on the list."
as soon as possible to help us with Fedora 18 Alpha release!"


<references/>
<references/>


===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 (June 2010 - August 2010)====
=== Fedora Events ===
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29</ref>
 
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2</ref>
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.
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3</ref>
 
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4</ref>
====Upcoming Events (September 2012 - November 2012)====
* '''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#FY13_Q3_.28September_2012_-_November_2012.29</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#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 173: 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"