FWN/Beats/Announcements: Difference between revisions

     fixed input box alignment issue in login box #579

     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

     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'

     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

     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.

     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"

Search

FWN/Beats/Announcements: Difference between revisions

Latest revision as of 11:18, 31 August 2012

Contents

Announcements

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

Fedora Infrastructure announces status.fedoraproject.org

Beats are open!

Fedora Development News

New bodhi release in production

Build F-18 collection packages for all language translators

Fedora 18 Alpha to slip by another one week

Fedora Events

Upcoming Events (September 2012 - November 2012)

Past Events

Additional information

Fedora Press Releases

@@ Line 2: / Line 2: @@
 ==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/>
-===Fedora Announcement News===
+===Breaking News of the Week and Month===
-====Summer Coding 2010 - now with more time! ====
-[[User:Kwade|Karsten Wade]] <ref>Karsten Wade</ref> - Senior Community Gardener of Red Hat Community Architecture announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002789.html</ref>, “We have pushed back the first part of the Summer Coding 2010 schedule. There wasn't enough time to find sponsors.  Now there is more time for mentors and students to generate ideas and write up good proposals, while people like you and me look for more sponsors.
-Highlights - note all due items now have an entire month more:
+====[Guidelines Change] Changes to the Packaging Guidelines====
-* Ideas page closes 13 May
+* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
-* Proposals are due 20 May
+* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
-* Sponsors must pledge by 21 May
-Projects are set to start on 01 June, which is only a week after the original start date.  Our goal is to be as flexible as we can be after that, contact us if you have any questions about how to make the schedule work for you:
+"A new section has been added to the SysV Initscripts section, discussing
-<ref>https://fedoraproject.org/wiki/Communication_for_Summer_Coding_2010</ref>
+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>
-Here is the updated schedule, reprinted below: <ref>https://fedoraproject.org/wiki/Summer_Coding_2010_schedule</ref>
+---
-<ref>‘’’Full schedule’’’
+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>
-•	April
+---
-April - Students can begin submitting applications
+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>
-    * May
+---
-          Whole month - students, mentors, and sub-projects get to
+A new section on Macros has been added to the Packaging Guidelines,
-          know each other
+covering Packaging of Additional RPM Macros.
-May - Mentors need to finish idea pages
+<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
-May - Students applications + proposals need to be in
-May - Sponsors must pledge funding by this point
-May - Organizers finalize how many applications will be
-          accepted
-May - Mentors + admins finalize rank-ordered list
-May - Students informed yes/no about application
-    * June
+---
-          Whole month - code, interact
+A new section on the Documentation= field in systemd unit files (F17+)
-June - Project begins (depending on proposal)
+has been added.
-	  NOTE: Proposals may have a modified schedule included.
+<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
-    * July
+---
-July - Midterm evaluations period begins
+A short section on the Group tag in Fedora packages has been added.
-July - Midterm evaluations due
+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>
-    * August
+---
-August - Project coding completes
+The RHEL conditionalization has been removed from the Python3 example
-August - Students final report, code snapshot, and
+spec file, as it is no longer valid.
-          evaluations due
+<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
-August - Mentor evaluations due for students
-August - Final evaluations due back to students
-August - Mentor, sub-project evaluations due
-    * September
+---
-September - Sponsors receive report from organizers
+These guidelines (and changes) were approved by the Fedora Packaging
-September - Sponsors release and deliver funds (proposed
+Committee (FPC).
-          date) </ref>
-For more details:
+'''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.'''
-<ref>http://iquaid.org/2010/04/14/more-time-for-fedora-summer-coding-schedule-moved-back-a-month/</ref>
-Thanks,
+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>"
-- Summer Coding SIG
+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/>
-====Request for Comments: Fedora Project Contributor Agreement Draft (Replacement for Fedora Individual Contributor License Agreement)====
+====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====
-[[User:Spot|Tom "spot" Callaway]]<ref> Tom "spot" Callaway</ref> from Fedora Legal announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002790.html</ref>”
-Hello Fedora! (Is this thing on?)
-Sorry for the very wide net, but we wanted to make sure as many members of our community could see this as possible.
+* 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>
-For some time now, Fedora has been working with Red Hat Legal to come up with a replacement for the Fedora Individual Contributor License Agreement (aka, the Fedora ICLA). As a result, the Fedora Project Contributor Agreement (FPCA) has been approved by Red Hat Legal, and is now being presented to the Fedora Community for comments and discussion.
+"Greetings! (...or perhaps I should say.... bonjour!)
-The full text of the FPCA, along with a FAQ, can be found here:
+I'd like to share a few reminders and announcements regarding the
-<ref>https://fedoraproject.org/wiki/Legal:Revised_Fedora_CLA_Draft</ref>
+upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
-Please, take a moment and read the FPCA and the FAQ. It is not a long, or overly complicated document, as legal documents go, but it is important that all Fedora Contributors read it over and make sure they understand it and like it (or can at least agree to it).
+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.
-Fedora Legal wishes to give the Fedora community a window of time for discussion and review of the FPCA. This window is open until May 18, 2010 (2010-05-18). After that point, either a revised FPCA will be released for review, or we will begin the process of phasing in the FPCA and phasing out the Fedora ICLA.
+To place a subsidy request, please follow these steps:
-Thanks in advance,
+: Pre-register at
+<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
+put an X in the $$$ column
+: 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>
-Tom "spot" Callaway, Fedora Legal
+Additionally, a few notes regarding the hotel in Paris:
-P.S. Fedora Legal would like to give a huge thank you to the people involved behind the scenes to make the FPCA possible. The primary author was Richard Fontana, with feedback from Tom Callaway, Pamela Chestek,
+There are other events in Paris during this time period; most notably,
-Paul Frields, and Robert Tiller. Feel free to give them gifts (for example, drinks or tasty snacks) as thank yous, although, this is not a requirement (legal or otherwise). ;)
+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/>
-====F14 Naming====
+====Fedora Infrastructure announces status.fedoraproject.org====
-=====F14 Naming: Constaine -> Goddard -> ???=====
- [[User:Pfrields|Paul W. Frields]]<ref> Paul W. Frields</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002791.html</ref>,
+* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
-“Fedora 13 is just around the corner, so it's time for us to kick off the naming process for the next Fedora release.  You can make a suggestion for the name for Fedora 14 here:
+* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>
-<ref>https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_13</ref>
+"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
+<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
+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.
-Remember that there are *instructions and guidelines* at the page that you must follow if you want your name to be considered.  For instance, there must be an "is-a" link between the name Constantine and the name you suggest.  That link must be different than previous links for Fedora release names.  Please be sure to conduct the required searches for brand and trademark names that might cause us problems.
+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'''.
-Read the full guidelines at that page, where you can also find full schedule details for the release naming process.  Suggestions will be collected until Tuesday, April 27, and voting will happen starting Tuesday, May 4!”
+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/>
-=====F14 Naming: Constantine -> Goddard -> ??? =====
+====Beats are open!====
-[[User:Pfrields|Paul W. Frields]]<ref>Paul W. Frields</ref> on another announcement<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002792.html</ref> mentioned, “
-On Tue, Apr 20, 2010 at 09:32:18PM -0400, Paul W. Frields wrote:
+* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
-> Fedora 13 is just around the corner, so it's time for us to kick off
+* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>
-> the naming process for the next Fedora release.  You can make a
-> suggestion for the name for Fedora 14 here:
->
-And of course, this link should really be:
-<ref>https://fedoraproject.org/wiki/Name_suggestions_for_Fedora_14</ref>
+"The Release Notes beats for Fedora 18 are now open:
+<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
-> Remember that there are *instructions and guidelines* at the page that
+If you're looking for a way to dip your toes in the water, so to
-> you must follow if you want your name to be considered.  For instance,
+speak, writing a beat is a great way to get started. If you're a
-> there must be an "is-a" link between the name Constantine and the name
+regular, don't forget about the checkBeat program:
-> you suggest.  That link must be different than previous links for
+<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
-> Fedora release names.  Please be sure to conduct the required searches
-> for brand and trademark names that might cause us problems.
->
-> Read the full guidelines at that page, where you can also find full
-> schedule details for the release naming process.  Suggestions will be
-> collected until Tuesday, April 27, and voting will happen starting
-> Tuesday, May 4!
-Apologies for the error.”
+As a reminder, the wiki drafts of beats are due on 12 September."
 <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.
-===Fedora Events===
+'''Acceptable Types of Announcements'''
-Fedora events are the 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!
+* Policy or process changes that affect developers.
+* Infrastructure changes that affect developers.
+* Tools changes that affect developers.
+* Schedule changes
+* Freeze reminders
-====Upcoming Events (March 2010 to May 2010)====
+'''Unacceptable Types of Announcements'''
-* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29</ref>
+* Periodic automated reports (violates the INFREQUENT rule)
-* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28March_2010_-_May_2010.29</ref>
+* Discussion
-* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_2</ref>
+* Anything else not mentioned above
-* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_3</ref>
+<references/>
+====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>
+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"
+<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 ===
+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)'''<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/>
@@ Line 159: / Line 366: @@
 ====Additional information====
-* '''[[Reimbursements]] -- reimbursement guidelines.'''
+* [[Reimbursements]] -- reimbursement guidelines.
-* '''[[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).'''
+* [[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).
-* '''[[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.'''
+* [[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.
 * [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
 * [[Event reports]] -- guidelines and suggestions.
 * [[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