From Fedora Project Wiki

< FWN‎ | Beats

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


<references/>
<references/>


=== Fedora Announcements ===
===Breaking News of the Week and Month===


====retiring blogs.fedoraproject.org on 2011-07-01====
====[Guidelines Change] Changes to the Packaging Guidelines====  


Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-May/002969.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>


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


There has been some confusion and misunderstanding around
---
blogs.fedoraproject.org recently. This email will hopefully clear them up.


At the Tempe Fudcon, the Fedora Infrastructure team determined that we should retire our blogs.fedoraproject.org service. The reasons for this
The review guidelines now reflect the use of sha256sum (instead of
were:  
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>


* We currently have no infrastructure members who are driving support of this service. (Fixing bugs, following upstream or improving the service).
---


* Wordpress has a long history of security issues, requiring frequent, custom patches or updates to keep it secure.  
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>


* Many other sites out there are providing blog services as their core mission, likely resulting in a more feature-full and compelling offering. Some of these sites like wordpress.com are commited to free software, like Fedora is.
---


* Usage of the service was quite low. We have 92 blogs, but only 39 of them had more than 5 posts. Only 6 of them had posts in the last month, and only 23 had posts in 2011.  
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>


While we are open to interested parties stepping forward to help us maintain the service, currently there is no compelling reason to keep the service running.
---


We will be happy to help any user wishing to transition their blog to  another service. We will provide web site redirects and dumps of their posts.
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>


Please contact fedora infrastructure (infrastructure at lists.fedoraproject.org)
---
with further questions or concerns.


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


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


====Appointment to the Fedora Board and reminder of upcoming elections====
---


[[User:Jsmith|Jared K. Smith]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-June/002970.html</ref>,
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


"The Fedora Board consists of five elected seats and four appointed seats.  In this elections cycle, there will be two openings for appointed Board seats and three opening for elected Board seats.  As part of the normal Board succession process<ref>http://fedoraproject.org/wiki/Board/SuccessionPlanning</ref>, one Board appointment
'''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.'''
is made before Board elections and the other is made after the election cycle.


I'm happy to announce that Guillermo Gomez has accepted the
As a reminder: The Fedora Packaging Guidelines are living documents! If
responsibility of serving on the Fedora Board.  Guillermo has demonstrated his commitment to Fedora through his tireless efforts on a number of different fronts, including working on packaging, development, and ambassador programs.  He has also shown his ability
you find something missing, incorrect, or in need of revision, you can
to mentor new contributors and help grow the Fedora community. I have no doubt that he'll continue these efforts while on the Board, and that he'll bring his perspective to help the Board as it makes decisions affecting the direction that Fedora takes. I would like to
suggest a draft change. The procedure for this is documented here:
publicly thank Guillermo for his willingness to serve, and I hope the entire Fedora community will join me in welcoming him to the Board.
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"


Guillermo will fill seat A4 (see the Board History<ref>http://fedoraproject.org/wiki/Board/History</ref> for a list of the seats), which has been held by Stephen Smoogen for the past year. I'd also like to take this opportunity to publicly thank Stephen for the work he's done on behalf of the Fedora Board.
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>


Elections for the three open elected seats on the Board (as well as FESCo elections) will begin on June 2nd at UTC 0001, as shown on the Fedora wiki's Elections page<ref>http://fedoraproject.org/wiki/Elections</ref>.  All community members are encouraged to cast their vote until the elections close at the end of the day (UTC time) on June 8th.  Within a week or two of the end of elections,
<references/>
another appointment will be made for the remaining Board seat (seat A3).  If you have interest in serving on the Fedora Board, please don't hesitate to contact me directly to indicate your willingness to serve.


--
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 
Jared Smith
Fedora Project Leader"


<references/>
* 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!)


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


[[User:Jsmith|Jared K. Smith]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-June/002971.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 requestsRequests 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.


"FUDCon (the Fedora Users and Developers Conference) is the premier Fedora event.  We typically have a FUDCon event in North America, Latin America, and Europe each year.  This year, I'm pleased to announce that we'll also be having a FUDCon event in the Asia-Pacific region.
To place a subsidy request, please follow these steps:


I've confirmed that we have budget set aside for a FUDCon in the Asia-Pacific region, and I'm now soliciting bids for FUDCon APAC. Bids should be created on the Fedora wiki, and a link to the bid mailed to the fudcon-planning list.  All bids should be completed by June 23rd.  Soon after the bidding process has closed, I'll meet together with FAMSCo, the Ambassadors in that region, and our primary corporate sponsor to pick the winning location.  After the location has been selected, we'll invite people to start registering and due to the details of our budget, the time frame for FUDCon APAC this year will likely be in either November or December.  Next year, I'll work to try to spread the FUDCon events around a bit more evenly, so that we can have one FUDCon event roughly each quarter.
1: Pre-register at
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and  
put an X in the $$$ column
2: Read about the funding request process and place a funding request
ticket in the FUDCon-planning ticket tracker here:
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>


The bidding process is described in more detail at<ref>https://fedoraproject.org/wiki/FUDCon_bid_process</ref>.  Any interested
Additionally, a few notes regarding the hotel in Paris:
parties are invited to submit their bids up until June 23rd.  If you
have any questions or concerns, please bring them up on the
fudcon-planning mailing list.


I look forward to seeing your proposals!
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
Jared Smith
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
Fedora Project Leader
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/>


====Elections: Notice of change in voting period and correction of eligibility for the Board election====
====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>
 
"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>.


David Nalley announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-June/002972.html</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.


"Hi folks,
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'''.


Wanted to make you aware of a situation that was discovered last night and responded to this morning.
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. "


A number of people caught an issue in the eligibility configuration for voters in the Board Election. Per the Board's Succession Planning<ref>https://fedoraproject.org/wiki/Board/SuccessionPlanning</ref> document this election is open to any person in the Fedora Accounts System who has completed the CLA. I mistakenly configured
<references/>
this election for CLA+1 which means that in addition to completing the CLA a person would have to be a member of an additional group. Members of the infrastructure team noted this and created a ticket in the Board's trac system late last night (no link as it's not visible to non-board members). That mis-configuration has now been corrected, and to ensure that we have not unduly disenfranchised any potential voters, the Board election period only has been extended by 24 hours from 08 June 23:59:59  to 09 June 23:59:59. Please note that the election period for the FESCo election remains unchanged.


I apologize for mis-configuring the election app, and thank the vigilant members of our community and infrastructure team who caught the issue so early in the process and helped to correct the problem in a timely manner.
====Beats are open!====


Thanks,
* 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>
 
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>
 
As a reminder, the wiki drafts of beats are due on 12 September."


David Nalley"
<references/>
<references/>


Line 123: Line 194:
<references/>
<references/>


====Reminder: Fedora Engineering Steering Committee election town hall is today====  
====New bodhi release in production====
[[User:Rbergereo|Robyn Bergereon]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000802.html</ref>,
 
"Greetings!


As previously announced, the town hall for the Fedora Engineering Steering Committee (FESCo) is today, May 31, 2011.
* 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>


The town hall will be taking place at 1800 UTC (2pm US-Eastern).
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>


For information on how to participate, please see<ref>http://fedoraproject.org/wiki/Elections#How_to_Join</ref>
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


Further information about the elections, including the schedule and process, can be seen here<ref>http://fedoraproject.org/wiki/Elections</ref>
Major changes in bodhi 0.9.2
---------------------------------


There are 5 seats open in this FESCo election, and 8 candidates. Please consider attending the town hall today, and bringing your questions to be asked of the nominees during the course of the town hall.
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


A summary and the IRC log will be posted and linked from the wiki after the discussion, if you're unable to watch it live.
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines


FESCo candidates and their information can be seen here<ref>http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations</ref>
* The submitter of an update can no longer effect the karma (Till Maas)


Cheers,
* Fix duplicate status change email notifications. (Till Maas)


Robyn"
* Mention age of updates in testing digest mails (Till Maas)


<references/>
* Support e-mail threading in notification e-mails (Till Maas)


====Changes to the Packaging Guidelines====
* Add X-Bodhi mail headers (Till Maas)


[[User:Spot|Tom Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000801.html</ref>:
* Gracefully handle private bugs (Cole Robinson)


"Here is this week's change to the Fedora Packaging Guidelines:
* 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.


The systemd guidelines on naming unit files have been amended to tell packagers how to make compatibility symlinks for alternate service names should their service have had a different name in the past.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


http://fedoraproject.org/wiki/Packaging:Systemd#Naming


---
Full list of changes since 0.8.7
--------------------------------


These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


Many thanks to the Fedora Community, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.
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'


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


Thanks,
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.


~spot"  
Till Maas (8):
      Add X-Bodhi mail headers
      Support e-mail threading in notification e-mails
      Mention age of updates in testing digest mails
      Use format string instead of string concatenation
      Import exceptions from sqlite3
      Remove files used by mercurial
      model.py: Change karma from Submitter to 0
      Fix notification on automatic status change"


<references/>
<references/>


====Outage: Upgrades/Reboots - 2011-05-31 18:00 UTC====
====Build F-18 collection packages for all language translators====


Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000800.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>


"Outage: Upgrades/Reboots - 2011-05-31 18:00 UTC
"Hi Fedora package maintainers


There will be an outage starting at 18:00 UTC on 2011-05-31,  which will last approximately 2 hours. During this time there may be very short outages of services as machines are updated and rebooted into new kernels.
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.


Machines will be rebooted in an order that allows for least disruption to services.  
Thank you so much.


In many cases, there will be no noticeable downtime due to redundancy and fail-over.
noriko
Fedora Localization Project"


To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref>
<references/>
or run:


date -d '2011-05-31 18:00 UTC'
====Fedora 18 Alpha to slip by another one week====


Reason for outage:  
* 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>


System updates/Reboots.  
"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>.  


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


* BFO - http://boot.fedoraproject.org/
The next Go/No-Go meeting is on Thursday Sep 06, same place
* Bodhi - https://admin.fedoraproject.org/updates/
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
* Buildsystem - http://koji.fedoraproject.org/
#fedora-meeting).
* GIT / Source Control
* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
* Docs - http://docs.fedoraproject.org/
* Email system
* Fedora Account System - https://admin.fedoraproject.org/accounts/
* Fedora Community - https://admin.fedoraproject.org/community/
* Fedora Hosted - https://fedorahosted.org/
* Fedora Insight - https://insight.fedoraproject.org/
* Fedora People - http://fedorapeople.org/
* Fedora Talk - http://talk.fedoraproject.org/
* Main Website - http://fedoraproject.org/
* Mirror List - https://mirrors.fedoraproject.org/
* Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
* Package Database - https://admin.fedoraproject.org/pkgdb/
* Smolt - http://smolts.org/
* Spins - http://spins.fedoraproject.org/
* Start - http://start.fedoraproject.org/
* Torrent - http://torrent.fedoraproject.org/
* Wiki - http://fedoraproject.org/wiki/


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


Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2790
<references/>


Contact Information:


Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above."
=== Fedora Events ===
 
<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.


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.
====Upcoming Events (September 2012 - November 2012)====
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.  
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
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!
* '''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>


====Upcoming Events (March - May 2011)====
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29</ref>
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4</ref>


<references/>
<references/>
Line 256: 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