From Fedora Project Wiki

< FWN‎ | Beats

 
(38 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
<references/>
 
<references/>
  
===Breaking News of the Week===
+
===Breaking News of the Week and Month===
  
====FUDCon APAC 2012 will be in lovely Kuala Lumpur, Malaysia!====   
+
====[Guidelines Change] Changes to the Packaging Guidelines====   
  
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Mon Mar 5 12:55:23 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-March/003045.html</ref>,
+
* 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>
  
"I'm delighted to announce that the '''APAC FUDCon for 2012 will be in Kuala
+
"A new section has been added to the SysV Initscripts section, discussing
Lumpur, Malaysia'''.
+
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>
  
Thanks to all of those who submitted bids for this FUDCon - I am very
+
---
happy to see so much interest, and I believe the recent APAC FUDCon in
 
Pune truly helped to show the high interest in having ongoing FUDCons in
 
this region of the world.
 
  
Please stay tuned for further announcements clarifying the details of  
+
The review guidelines now reflect the use of sha256sum (instead of
attendance, including dates/times/places, registration, as well as
+
md5sum) to confirm upstream source integrity.
information for those seeking subsidies for attendance.
+
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
  
Cheers!"
+
---
  
<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,
====FUDCon Kuala Lumpur travel subsidy requests are now open==== 
+
how to handle explicit Requires on PHP extensions, and how to handle a
 
+
Requires for a minimum PHP version.
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Thu Mar 15 14:41:44 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-March/003046.html</ref>,
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
 
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
"Greetings,
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>
 
 
As you may know, there is a planned '''APAC FUDCon in Kuala Lumpur coming
 
up soon, May 18-20 in Kuala Lumpur, Malaysia'''<ref>https://fedoraproject.org/wiki/FUDCon:KualaLumpur_2012
 
</ref>.
 
 
 
https://fedoraproject.org/wiki/FUDCon:KualaLumpur_2012
 
  
If you are planning to attend FUDCon Kuala Lumpur and need a travel
+
---
subsidy, the ticketing system is currently open for requests. Requests
 
will be accepted through March 27, 2012. Please note that funding
 
requests without a ticket will not be considered.  The travel budget is
 
limited, and preference will be given to attendees from the APAC region
 
who are actively contributing to Fedora, and have detailed their
 
participation plans for FUDCon in their subsidy request.
 
  
To place a subsidy request, please follow these steps:
+
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>
  
1: Pre-register at<ref>https://fedoraproject.org/wiki/FUDCon:KualaLumpur_2012#Pre-registration
+
---
</ref>
 
https://fedoraproject.org/wiki/FUDCon:KualaLumpur_2012#Pre-registration
 
  
2: Put an X in the $$$ column
+
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>
  
3: 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>:
 
  
'''https://fedorahosted.org/fudcon-planning/wiki/FundingRequest'''
+
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>
  
Thank you!"
+
---
  
<references/>
+
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>
  
====Fedora is featuring on GSoC 2012==== 
+
---
  
Fedora Ambassador from Srilanka - Buddhike Kurera<ref>bckurera at fedoraproject.org</ref> on Fri Mar 16 19:10:32 UTC 2012 announced broadly<ref>http://lists.fedoraproject.org/pipermail/announce/2012-March/003047.html</ref> the GSoC 2012 program with the following details,
+
These guidelines (and changes) were approved by the Fedora Packaging
 +
Committee (FPC).
  
"I am delighted to announce that the Fedora Project has been accepted
+
'''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.'''
for the GSoC 2012 program<ref>http://www.google-melange.com/gsoc/accepted_orgs/google/gsoc2012</ref>.
 
This would be the 7th time where the Fedora project represents the
 
program since 2005.
 
  
The students' application procedure and other relevant information will be published soon. If you are interested in joining with the Fedora project as a student or a mentor please explore following URLs.
+
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>"
  
First of all subscribe for the summer-coding mailing list<ref>https://admin.fedoraproject.org/mailman/listinfo/summer-coding</ref> and explore the Idea list<ref>https://fedoraproject.org/wiki/Summer_coding_ideas_for_2012</ref>, feel free to contact us for more information."
+
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/>
  
 +
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 
  
====It is time for another episode of: NAME THAT FEDORA RELEASE==== 
+
* 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>
  
Robyn Bergeron
+
"Greetings! (...or perhaps I should say.... bonjour!)
Robyn Bergeron rbergero at redhat.com
 
Tue Mar 20 06:08:07 UTC 2012
 
http://lists.fedoraproject.org/pipermail/announce/2012-March/003048.html
 
  
"Oh, Beefy Miracle, I have relished your name for months, but as your day
+
I'd like to share a few reminders and announcements regarding the  
for widespread consumption (release day) approaches, it is time for the
+
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
community to choose the name of Fedora 18.  This process begins with
 
*you,* dear readers and contributors, as potential names are accepted
 
for submission over the course of the next week, beginning now, March
 
20th, and ending March 27th (at 23:59:59 UTC, for those of you who can't
 
mustard up any ideas until the last possible second).
 
  
Frankly, I'm expecting an a-bun-dance of suggestions, and not just from
+
If you are planning to attend FUDCon and need a travel subsidy to do so,  
people who cannot take my punni-ness any longerRules and guidelines
+
the ticketing system is now open for those requestsRequests will be
for suggestions, as well as the location in which you may make your name
+
accepted through August 15, 2012. Please note that funding requests
suggestions, are on this wiki page:
+
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.
  
http://fedoraproject.org/wiki/Name_suggestions_for_Fedora_18
+
To place a subsidy request, please follow these steps:
 
 
A quick word on details:
 
  
You *must* follow the guidelines at the page listed above for your name
+
1: Pre-register at
to be considered.  These guidelines include the following items:
+
<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>
  
* There must be an "is-a" link between the name "Beefy Miracle" (the
+
Additionally, a few notes regarding the hotel in Paris:
name of F17) and your suggested name.
 
* That link must be different from any previous links between release names.
 
* Names of living people and well-known trademarks will likely be
 
rejected as well.
 
  
Schedule details for release naming are also shown on the F18 naming
+
There are other events in Paris during this time period; most notably,
wiki page.
+
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. :)
  
I know that it may be hard to *top* Beefy Miracle (ahahahaha, get it? As
+
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
in toppings!) but I do have every bit of faith that many of you have
+
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October.
already thought of name suggestions that may or may not be more mature,  
+
However, this rate will expire at the end of August, and any remaining
or more neutral with regards to dietary restrictions. :) I do look
+
rooms in our block will expire.
forward to seeing your suggested names and recommend, as always, to have
 
fun.
 
 
 
Cheers,"
 
  
 +
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/>
  
====Outage: fedorapeople.org - 2012-03-26 21:00 UTC====   
+
====Fedora Infrastructure announces status.fedoraproject.org====   
  
Kevin Fenzi
+
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
Kevin Fenzi kevin at scrye.com
+
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>
Wed Mar 21 22:17:27 UTC 2012
 
http://lists.fedoraproject.org/pipermail/announce/2012-March/003049.html
 
  
"Outage: fedorapeople.org - 2012-03-26 21:00 UTC
+
"I'm happy to announce the general availability of our
 +
status.fedoraproject.org site.
  
There will be an outage starting at 2012-03-26 21:00 UTC, which will
+
This site provides an easy way for Fedora contributors and users to
last approximately 2 hours.
+
check on the status of services provided by Fedora Infrastructure.
  
To convert UTC to your local time, take a look at
+
The site auto reloads every minute, and also provides a rss feed at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
+
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
or run:
 
  
date -d '2012-03-26 21:00 UTC'
+
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.
  
Reason for outage:
+
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'''.
  
We are moving the main fedorapeople.org host to another site. This site
+
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
will allow us to provide additional group storage for various groups
+
issues with outages in our infrastructure affecting status reporting. "
that need download space, as well as being closer to our backup server
 
to allow for quicker backups.
 
  
Affected Services:
+
<references/>
  
Fedora People - http://fedorapeople.org/
+
====Beats are open!====
  
Unaffected Services:
+
* 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>
  
Ask Fedora - http://ask.fedoraproject.org/
+
"The Release Notes beats for Fedora 18 are now open:
 +
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
  
BFO - http://boot.fedoraproject.org/
+
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>
  
Bodhi - https://admin.fedoraproject.org/updates/
+
As a reminder, the wiki drafts of beats are due on 12 September."
  
Buildsystem - http://koji.fedoraproject.org/
+
<references/>
  
GIT / Source Control
+
=== 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.
  
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
+
'''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
  
Docs - http://docs.fedoraproject.org/
+
'''Unacceptable Types of Announcements'''
 +
* Periodic automated reports (violates the INFREQUENT rule)
 +
* Discussion
 +
* Anything else not mentioned above
  
Email system
+
<references/>
  
Fedora Account System - https://admin.fedoraproject.org/accounts/
+
====New bodhi release in production====
  
Fedora Community - https://admin.fedoraproject.org/community/
+
* 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>
  
Fedora Hosted - https://fedorahosted.org/
+
"A new release of Bodhi has just been deployed to production.
 +
<ref>https://admin.fedoraproject.org/updates</ref>
  
Fedora Insight - https://insight.fedoraproject.org/
+
Bugs and enhancement requests can be filed here:
 +
<ref>http://bodhi.fedorahosted.org</ref>
  
Main Website - http://fedoraproject.org/
+
Major changes in bodhi 0.9.2
 +
---------------------------------
  
Mirror List - https://mirrors.fedoraproject.org/
+
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  
Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
+
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  
Package Database - https://admin.fedoraproject.org/pkgdb/
+
* The submitter of an update can no longer effect the karma (Till Maas)
  
QA Services
+
* Fix duplicate status change email notifications. (Till Maas)
  
Secondary Architectures
+
* Mention age of updates in testing digest mails (Till Maas)
  
Smolt - http://smolts.org/
+
* Support e-mail threading in notification e-mails (Till Maas)
  
Spins - http://spins.fedoraproject.org/
+
* Add X-Bodhi mail headers (Till Maas)
  
Start - http://start.fedoraproject.org/
+
* Gracefully handle private bugs (Cole Robinson)
  
Torrent - http://torrent.fedoraproject.org/
+
* Set the default request for new updates to 'testing' in the web form
  
Wiki - http://fedoraproject.org/wiki/
+
* 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.
  
Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/3213
+
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
  
Contact Information:
 
  
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
+
Full list of changes since 0.8.7
comments to the ticket for this outage above."
+
--------------------------------
  
<references/>
+
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'
  
=== Fedora Development News ===
+
Mathieu Bridon (6):
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.
+
      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
  
'''Acceptable Types of Announcements'''
+
Ralph Bean (19):
* Policy or process changes that affect developers.
+
      Sending messages with fedmsg.
* Infrastructure changes that affect developers.
+
      No longer using fedmsg schema/validation.
* Tools changes that affect developers.
+
      fedmsg.ini -> fedmsg-config.py
* Schedule changes
+
      More detail in the update.complete message.
* Freeze reminders
+
      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.
  
'''Unacceptable Types of Announcements'''
+
Till Maas (8):
* Periodic automated reports (violates the INFREQUENT rule)
+
      Add X-Bodhi mail headers
* Discussion
+
      Support e-mail threading in notification e-mails
* Anything else not mentioned above
+
      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/>
  
====Please pull latest translation, re-package and push to koji for L10N QA test====  
+
====Build F-18 collection packages for all language translators====
  
From Fedora Localization Project Noriko Mizumoto<ref>noriko.mizumoto at gmail.com</ref> on Thu Mar 1 02:37:44 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-March/000901.html</ref>,
+
* 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
 
"Hi Fedora package maintainers
  
Could you please pull latest translation for your package, re-package
+
Please build and push your package with latest translation file (e.g.
with it and push to koji for L10N QA test by 2-Mar?
+
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
We will have a live image to be composed for this particular test on
+
Your packages with latest translation will be composed into test live
5-Mar. The focus is to test translations availability and accuracy in
+
image on 3-Sep Monday. Then various language translators worldwide will
desktop applications. This test covers all Fedora packages. This is only
+
test the image in their own languages. Any issue will be filed as bug.
one chance for translators to check translation quality. It is highly
+
This is only one chance for translators to check and modify Localization
appreciated your help."
+
quality of your packages by checking UI, and we need your help.
 +
 
 +
Thank you so much.
 +
 
 +
noriko
 +
Fedora Localization Project"
  
 
<references/>
 
<references/>
  
====Bodhi comment emails issue fixed====  
+
====Fedora 18 Alpha to slip by another one week====
  
Kevin Fenzi<ref>kevin at scrye.com</ref> on Sat Mar 10 23:40:00 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-March/000902.html</ref>,
+
* 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>
  
"Greetings.  
+
"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>.  
  
In the last week or so, there was an issue with bodhi sending emails to
+
As a result, ALL MAJOR MILESTONES, and their dependent tasks,  
update submitters when comments were left on their updates. Note that
+
will be pushed out by one week.
this issue did not effect bodhi comments (ie, pushed to testing, pushed
 
to stable, being pushed, etc), only comments left by users / autoqa.
 
  
This issue has been corrected, so any comments left should now email
+
The next Go/No-Go meeting is on Thursday Sep 06, same place
correctly.  
+
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
 +
#fedora-meeting).
  
Maintainers may wish to look over their pending updates for any
+
If you have an accepted blocker bug, please try to fix it
comments they may have missed.
+
as soon as possible to help us with Fedora 18 Alpha release!"
  
Sorry for the trouble,"
+
<references/>
  
<references/>
 
  
 
=== Fedora Events ===
 
=== Fedora Events ===
  
The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning.
+
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.
Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding.
 
In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
 
  
====Upcoming Events (December 2011 - May 2012)====
+
====Upcoming Events (September 2012 - November 2012)====
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.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#FY13_Q1_.28March_2012_-_May_2012.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#FY12_Q4_.28December_2012_-_February_2013.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_Q1_.28March_2012_-_May_2012.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 297: 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

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]

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

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

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

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

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"

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"

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


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]

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.

Fedora Press Releases

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