From Fedora Project Wiki

< FWN‎ | Beats

 
(20 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===
  
====New FAmSCo election guidelines====   
+
====[Guidelines Change] Changes to the Packaging Guidelines====   
[[User:Cwickert|Christoph Wickert]]<ref>christoph.wickert at googlemail.com</ref> on Thu Apr 26 11:19:10 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003063.html</ref>,
 
  
"after months of - sometimes controversial - discussion I am am happy to
+
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
announce the new FAmSCo election guidelines <ref>https://fedoraproject.org/wiki/FAmSCo_election_rules</ref>. For those of you, who
+
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
did not follow the discussion, here is a brief summary of the three most
 
important changes:
 
  
=====More continuity=====
+
"A new section has been added to the SysV Initscripts section, discussing
Instead of electing all seats once a year, we follow the example of the
+
the proper use of subsys locking. Even though Fedora packages should no
Fedora Board and FESCo and elect half of the committee every 6 months or
+
longer be using SysV Initscripts as a primary service mechanism, Red Hat
with every release of Fedora. FAmSCo will not change over sudden and
+
Enterprise Linux and EPEL do. Additionally,
new members can easily catch up with their new duties by learning from
+
Red Hat points partners to the Fedora Guidelines when they build for RHEL.
others.
+
<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref>
  
=====Easier filling of vacant seats=====
+
---
Every committee is in danger of members becoming inactive.  This can
 
happen to all of us for various reasons such as our dayjobs or personal
 
problems.  Under the old guidelines  <ref>https://fedoraproject.org/w/index.php?title=FAmSCo_election_rules&oldid=269322  </ref>, we had to wait until only 3
 
members left - even with 2 left the committee is hardly operational -
 
and then call a supplementary election - which never happened even
 
though we had only 4 active members.  Now we are filling vacant seat
 
when necessary, either with runner-up candidates from the previous
 
elections or by appointing new members.
 
  
=====Wider electorate=====
+
The review guidelines now reflect the use of sha256sum (instead of
The ambassadors represent the whole Fedora Project, this is why now not
+
md5sum) to confirm upstream source integrity.
only ambassadors are eligible to vote for FAmSCo, but everybody who has
+
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
signed the Contributors License Agreement and is member of (at least)
 
one other group in the Fedora Account System (FAS) is allowed to vote.
 
This will not only strengthen FAmSCo's position but also help candidates
 
who are active in other groups of the Fedora project.
 
  
Last but not least the guidelines have been massively cleaned up.
+
---
  
We think that the new guidelines are a big improvement and want them to
+
The PHP Packaging guidelines have been updated to include guidance about
come into effect as soon as possible.  Therefor we will have a special
+
when it is appropriate to have an explicit Requires on httpd & mod_php,
election for Fedora 18 (the next regular elections were scheduled for
+
how to handle explicit Requires on PHP extensions, and how to handle a
F19). All 7 seats in FAmSCo are open for election. In order to make
+
Requires for a minimum PHP version.
the transition to the new alternating terms, the top 4 vote-getters will
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
serve 2 Fedora releases, the bottom 3 will have to run for re-election
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
after one release.
+
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>
  
More about the upcoming ambassadors elections to come later this week as
+
---
part of the general Fedora 18 elections announcement.  Please help us
 
getting a better, stronger and more active FAmSCo by casting your votes.
 
  
If you have feedback or questions, please don't hesitate to ask. We are
+
A new section on Macros has been added to the Packaging Guidelines,
looking for your input on the Fedora ambassadors mailing list<ref>https://admin.fedoraproject.org/mailman/listinfo/ambassadors</ref>."
+
covering Packaging of Additional RPM Macros.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
  
 +
---
 +
 +
A new section on the Documentation= field in systemd unit files (F17+)
 +
has been added.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
 +
 +
---
 +
 +
A short section on the Group tag in Fedora packages has been added.
 +
All current versions of Fedora (and their respective RPM versions) treat
 +
the Group tag as optional. Packages may include a Group: field for
 +
compatibility with EPEL, but are not required to do so.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>
 +
 +
---
 +
 +
The RHEL conditionalization has been removed from the Python3 example
 +
spec file, as it is no longer valid.
 +
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
 +
 +
---
 +
 +
These guidelines (and changes) were approved by the Fedora Packaging
 +
Committee (FPC).
 +
 +
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.'''
 +
 +
As a reminder: The Fedora Packaging Guidelines are living documents! If
 +
you find something missing, incorrect, or in need of revision, you can
 +
suggest a draft change. The procedure for this is documented here:
 +
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
 +
 +
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
 +
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>
 +
 +
<references/>
 +
 +
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 
 +
 +
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
 +
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
 +
 +
"Greetings! (...or perhaps I should say.... bonjour!)
 +
 +
I'd like to share a few reminders and announcements regarding the
 +
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
 +
 +
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
 +
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
 +
put an X in the $$$ column
 +
2: Read about the funding request process and place a funding request
 +
ticket in the FUDCon-planning ticket tracker here:
 +
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>
 +
 +
Additionally, a few notes regarding the hotel in Paris:
 +
 +
There are other events in Paris during this time period; most notably,
 +
our first day of FUDCon will be taking place at the Open World Forum
 +
conference, on the day in which the public is encouraged to participate
 +
in and learn about open source projects.  OWF had nearly 2000 attendees
 +
last year.  Accordingly, rooms might be in short supply as we approach
 +
FUDCon; please, book your hotel as soon as possible, not only for
 +
affordability purposes, but also so that you have a bed to sleep in. :)
 +
 +
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
 +
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
 +
However, this rate will expire at the end of August, and any remaining
 +
rooms in our block will expire.
 +
 +
For instructions on booking your hotel, please read the Lodging/Hotel
 +
section of the FUDCon: Paris wiki:
 +
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
 +
 
<references/>
 
<references/>
  
====Fedora Elections: General information, and questionnaire opening.====   
+
====Fedora Infrastructure announces status.fedoraproject.org====   
[[User:Rbergero|Robyn Bergeron]]-Fedora Project Leader<ref>rbergero at redhat.com</ref> on Fri Apr 27 11:52:50 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003065.html</ref>,
 
  
"It is once again time for election season to begin. As noted in the
+
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
elections schedule<ref>http://fedoraproject.org/wiki/Elections#Committee_Elections_Schedule</ref>, the elections questionnaire is now open to
+
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>
populate with questions for candidates, and will close on May 8th.  The
 
elections nomination period will begin AFTER the questionnaire period
 
has closed.
 
  
You may add your burning questions for candidates to answer here:
+
"I'm happy to announce the general availability of our
http://fedoraproject.org/wiki/F18_elections_questionnaire<ref>http://fedoraproject.org/wiki/F18_elections_questionnaire
+
status.fedoraproject.org site.  
</ref>
 
  
 +
This site provides an easy way for Fedora contributors and users to
 +
check on the status of services provided by Fedora Infrastructure.
  
The following seats are available in this election:
+
The site auto reloads every minute, and also provides a rss feed at
 +
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.
  
* '''Fedora Project Board: 3 seats'''
+
If you run into a problem or issue that is not reflected at
* '''FESCo (Fedora Engineering Steering Committee):  5 seats'''
+
status.fedoraproject.org, please do report it to us in #fedora-admin on
* '''FAmSCo (Fedora Ambassadors Steering Committee): 7 seats'''
+
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.
 +
 
 +
As with everything in Fedora Infrastructure, this application is open
 +
source. Source is available from:
 +
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
 +
and is released under a '''GPLv2+ license'''.
 +
 
 +
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
 +
issues with outages in our infrastructure affecting status reporting. "
 +
 
 +
<references/>
  
Please take note of the following changes for this election:
+
====Beats are open!====
  
* All questions for the questionnaire must be submitted by May 8th,
+
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
prior to the beginning of nominations. As seen in the schedule above,
+
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>
the nomination period does not start until May 9th.
 
* As noted on announce-list<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003063.html</ref>, FAmSCo is electing all 7 seats this
 
cycle, with the goal of having staggered elections similar to the Board
 
and FESCo. Additionally, voting eligibility has been widened to allow
 
anyone who has signed the FPCA AND is a member of at least one
 
additional non-FPCA/CLA group. (In other words: No longer just
 
ambassadors, but those part of other teams as well.)
 
  
Full election information may be seen here:
+
"The Release Notes beats for Fedora 18 are now open:
http://fedoraproject.org/wiki/Elections<ref>http://fedoraproject.org/wiki/Elections</ref>
+
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>
  
Participating in these bodies are one of many ways to contribute to
+
If you're looking for a way to dip your toes in the water, so to
Fedora; I encourage you to consider running, or to urge those you
+
speak, writing a beat is a great way to get started. If you're a
believe are excellent candidates to run.  Additionally, your  
+
regular, don't forget about the checkBeat program:
contributions are welcomed in helping to keep the elections running
+
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>
smoothly; volunteers are needed to help collect questionnaire answers
 
from candidates, as well as for scheduling and moderating town halls.
 
If you are interested in helping with those efforts, please contact [[User:Inode0|John
 
Rose]]<ref>http://fedoraproject.org/wiki/User:Inode0</ref>.
 
  
And a big thank you! to John for coordinating the elections thus far,
+
As a reminder, the wiki drafts of beats are due on 12 September."
your efforts are very much appreciated."
 
  
 
<references/>
 
<references/>
Line 128: Line 194:
 
<references/>
 
<references/>
  
====Fedora 17 for Power Alpha Announcement====  
+
====New bodhi release in production====
David Aquilina<ref>dwa at redhat.com</ref> on Tue Apr 10 19:51:42 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000913.html</ref>,
 
  
"Time flies like the wind...
+
* 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>
  
As it's already time again for another Fedora release on Power, this
+
"A new release of Bodhi has just been deployed to production.
time for Fedora 17 Alpha.
+
<ref>https://admin.fedoraproject.org/updates</ref>
  
We've hit a couple of bumps along the road to the Alpha, but at long
+
Bugs and enhancement requests can be filed here:
last we're finally at a state where we're ready to release it to the
+
<ref>http://bodhi.fedorahosted.org</ref>
public.
 
  
Due to lack of developer time and hardware, Apple hardware support is at
+
Major changes in bodhi 0.9.2
this point completely untested. Especially with the switch to grub2 we
+
---------------------------------
rely on community feedback and participation to make this work for this
 
release. So if you have the hardware and want it to work, patches
 
welcome! :)
 
  
The bits are available from your closest mirror:
+
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  
<ref>https://mirrors.fedoraproject.org/publiclist/Fedora/17-Alpha/ppc64/</ref>
+
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  
More details about this Alpha release can be found here:
+
* The submitter of an update can no longer effect the karma (Till Maas)
  
<ref>https://fedoraproject.org/wiki/Fedora_17_Alpha_PPC_release_notes</ref>
+
* Fix duplicate status change email notifications. (Till Maas)
  
One of our focuses in the lead up to the beta of Fedora 17 for Power
+
* Mention age of updates in testing digest mails (Till Maas)
will be addressing architecture-specific packaging issues in as many
 
packages as possible. If you own a package in Fedora which has
 
ExclusiveArch or ExcludeArch set, please take a moment to verify that
 
the architectures you've excluded or are exclusive to are still correct
 
and sane.
 
  
I want to thank everyone involved in making this happen once more. Many
+
* Support e-mail threading in notification e-mails (Till Maas)
Fedora packagers and contributors have again stepped up and helped fix
 
issues that only appeared on Power hardware. Moreover the whole Fedora
 
Secondary Arch team has been doing a fantastic job to get us to where we
 
are now, especially considering that we had a complete switch of
 
builders and hub hardware, mass rebuild and a hub failure along the way!
 
  
As usual, you can reach the whole team on the #fedora-ppc IRC channel on
+
* Add X-Bodhi mail headers (Till Maas)
FreeNode and via our email list:
 
  
<ref>https://admin.fedoraproject.org/mailman/listinfo/ppc</ref>
+
* Gracefully handle private bugs (Cole Robinson)
  
And we have our Secondary Arch wiki with (decently) updated information:
+
* Set the default request for new updates to 'testing' in the web form
  
<ref>http://fedoraproject.org/wiki/Architectures/PowerPC</ref>
+
* 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.
  
For Phil, Karsten, and the entire Fedora for Power team,
+
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
Thanks & regards,
 
David"
 
  
<references/>
 
  
====Fedora 17 Beta Go/No-Go Meeting, Round 3, Wednesday, April 11, @17:00 Eastern==== 
+
Full list of changes since 0.8.7
Fedora New Project Leader, [[User:Rbergero|Robyn Bergeron]]<ref>rbergero at redhat.com</ref> on Wed Apr 11 03:23:31 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000914.html</ref>,
+
--------------------------------
  
"Please join us on irc.freenode.net in #fedora-meeting-1 for this
+
Kalpa Welivitigoda (1):
important meeting. This will be Round 3 of this meeting for the Beta
+
      fixed input box alignment issue in login box #579
release of F17.
 
  
Wednesday, April 11, 2012 @21:00 UTC (17:00 EDT/14:00 PDT)
+
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'
  
"Before each public release Development, QA and Release Engineering meet
+
Mathieu Bridon (6):
to determine if the release criteria are met for a particular release.
+
      Have bodhi-init create all the tables
This meeting is called the Go/No-Go Meeting."
+
      masher: Fix the comparison
 +
      masher: Reuse variable
 +
      setup: Fix the Turbogears version requirement
 +
      Don't version control auto-generated files
 +
      setup: Add missing dependencies
  
"Verifying that the Release criteria are met is the responsibility of
+
Ralph Bean (19):
the QA Team."
+
      Sending messages with fedmsg.
 +
      No longer using fedmsg schema/validation.
 +
      fedmsg.ini -> fedmsg-config.py
 +
      More detail in the update.complete message.
 +
      More concise send_message calls.
 +
      Ignore dev db.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Updates for the latest fedmsg.  Getting tests passing.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Ignore mashing fedora file.
 +
      Fixed what I think is a regression in login template.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Update to test fedmsg config.  Work with both tests and under WSGI.
 +
      Version bump for fedmsg in staging.
 +
      Only send the comment with a comment is added, not the whole update.
 +
      Using a "bodhi" user/group for mod_wsgi.
 +
      fedmsg+ssl changes to bodhi.spec.
 +
      Use modern fedmsg config format.
 +
      Disable message signing for bodhi tests.
  
For more details about this meeting see:
+
Till Maas (8):
<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
+
      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"
  
In the meantime, keep an eye on the Fedora 17 Beta Blocker list:
+
<references/>
<ref>http://fedoraproject.org/wiki/Current_Release_Blockers</ref>
 
  
Ongoing Beta RC test results can be seen here:
+
====Build F-18 collection packages for all language translators====
<ref>https://fedoraproject.org/wiki/Category:Fedora_17_Beta_RC_Test_Results</ref>
 
  
See you there, Wednesday, in #fedora-meeting-1.
+
* 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>
  
-Robyn, fingers and toes crossed thoroughly"
+
"Hi Fedora package maintainers
  
<references/>
+
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.
  
====Fedora 17 Beta is declared GOLD==== 
+
noriko
[[User:Rbergero|Robyn Bergeron]] - Fedora Project Leader<ref>rbergero at redhat.com</ref> on Thu Apr 12 05:11:27 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000915.html</ref>,
+
Fedora Localization Project"
  
"At today's F17 Beta Go/No-Go meeting, the Fedora 17 Beta release was
+
<references/>
declared gold. F17 Beta will be released Tuesday, April 17, 2012.
 
  
Thanks to everyone involved for pulling this one together and
+
====Fedora 18 Alpha to slip by another one week====
participating in the meetings, things came together well this week. :)
 
  
For those interested in the details:
+
* 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>
  
Minutes:
+
"Today at Go/No-Go meeting it was decided to slip Fedora 18
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.html</ref>
+
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
Logs:
+
full log is at <ref>http://bit.ly/PC16PF</ref>.
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html</ref>
 
  
Full minutes follow below.
+
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).
  
=====Fedora-meeting-1: F17 Beta go no go meeting=====
+
If you have an accepted blocker bug, please try to fix it
Meeting started by rbergeron at 21:00:32 UTC. The full logs are
+
as soon as possible to help us with Fedora 18 Alpha release!"
available at
 
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html</ref>"
 
  
 
<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 (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>
  
====Upcoming Events (December 2011 - May 2012)====
+
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#FY13_Q1_.28March_2012_-_May_2012.29</ref>
 
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_2</ref>
 
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q4_.28December_2012_-_February_2013.29</ref>
 
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_3</ref>
 
  
 
<references/>
 
<references/>
Line 266: 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