From Fedora Project Wiki

< FWN‎ | Beats
No edit summary
 
(221 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 Announcement News ===
===Breaking News of the Week and Month===
====Fedora Board IRC Meeting 1800 UTC 2010-07-02====
[[User:Pfrields|Paul W. Frields]], Fedora Project Leader, announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-July/002835.html</ref>:


"The Board is holding a public IRC meeting on Friday, July 2, 2010 at 1800 UTC on IRC Freenode.  For this meeting, the public is invited to
====[Guidelines Change] Changes to the Packaging Guidelines==== 
do the following:


* Join #fedora-board-meeting to see the Board's conversation.
* 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>


* Join #fedora-board-questions to discuss topics and post
"A new section has been added to the SysV Initscripts section, discussing
  questions. This channel is read/write for everyone.
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>


This meeting will last approximately 60 minutes.  The Board has reserved some time at the top of the hour to cover agenda items as
---
appropriate.  Following that we'll take questions from the community.


The moderator will voice people from the queue, one at a time, in the #fedora-board-meeting channel. We'll limit time per voice as needed
The review guidelines now reflect the use of sha256sum (instead of
to give everyone in the queue a chance to be heard. We look forwardto seeing you at the meeting!"
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
 
---
 
The PHP Packaging guidelines have been updated to include guidance about
when it is appropriate to have an explicit Requires on httpd & mod_php,
how to handle explicit Requires on PHP extensions, and how to handle a
Requires for a minimum PHP version.
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>
 
---
 
A new section on Macros has been added to the Packaging Guidelines,
covering Packaging of Additional RPM Macros.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>
 
---
 
A new section on the Documentation= field in systemd unit files (F17+)
has been added.
<ref>https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field</ref>
 
---
 
A short section on the Group tag in Fedora packages has been added.
All current versions of Fedora (and their respective RPM versions) treat
the Group tag as optional. Packages may include a Group: field for
compatibility with EPEL, but are not required to do so.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag</ref>
 
---
 
The RHEL conditionalization has been removed from the Python3 example
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
 
---
 
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
 
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.'''
 
As a reminder: The Fedora Packaging Guidelines are living documents! If
you find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
 
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>


<references/>
<references/>


===Fedora Development News===
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  
====Outage: PHX2 outage - 2010-07-05 01:00 UTC====


Mike McGrath announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000629.html</ref>:
* 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>


"There is an ongoing outage at this time in PHX2. The exact start time is not yet known and the ETA to be fixed is not yet known.
"Greetings! (...or perhaps I should say.... bonjour!)


To convert UTC to your local time, take a look at<ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto</ref> or run:
I'd like to share a few reminders and announcements regarding the
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


date -d '2010-07-05 01:00'
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.


=====Reason for outage:=====
To place a subsidy request, please follow these steps:


Several people are experiencing issues connecting to various Fedora
1: Pre-register at
services (see below). The cause for these issues seems to be network
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
related and it is impacting different people differently.  Some see packet
put an X in the $$$ column
loss, other see complete connectivity loss and other still aren't having
2: Read about the funding request process and place a funding request
any issues at all.
ticket in the FUDCon-planning ticket tracker here:
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>


Some services listed as unaffected would have been impacted previously to
Additionally, a few notes regarding the hotel in Paris:
this announcement but as we became aware of the issue have made some
changes to bring those services back online.  Those services include
bodhi, the account system, pkgdb, main website/wiki, community and
mirrormanager.


=====Affected Services:=====
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. :)


Bodhi - https://admin.fedoraproject.org/updates/
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
Buildsystem - http://koji.fedoraproject.org/
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October.
CVS / Source Control
However, this rate will expire at the end of August, and any remaining
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
rooms in our block will expire.
Email system


=====Unaffected Services:=====
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/>


Fedora Account System - https://admin.fedoraproject.org/accounts/
====Fedora Infrastructure announces status.fedoraproject.org==== 
Fedora Community - https://admin.fedoraproject.org/community/
BFO - http://boot.fedoraproject.org/
Docs - http://docs.fedoraproject.org/
Fedora Hosted - https://fedorahosted.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/
Translation Services - http://translate.fedoraproject.org/
Wiki - http://fedoraproject.org/wiki/


Ticket Link<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2255</ref>
* 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>


Contact Information:
"I'm happy to announce the general availability of our
status.fedoraproject.org site.


Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


<references/>
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 14 Feature Submission Deadline is One Week Away (2010-07-13)====
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.


John Poelstra reminded<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000630.html</ref> the community of the upcoming Fedora 14 feature submission deadline:
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 email serves as the last reminder for the Fedora 14 Feature Submission Deadline--Tuesday, July 13, 2010. After this date newly
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo.
issues with outages in our infrastructure affecting status reporting. "


Accepted Fedora 14 features so far<ref>https://fedoraproject.org/wiki/Releases/14/FeatureList</ref>
<references/>


If you are a current feature page owner, thank you for submitting your feature for Fedora 14 and contributing to the next release of Fedora. If you haven't updated your feature page in the last month it would be a great help to every one if you would do so now.
====Beats are open!====


As we start to reach deadlines and test releases for Fedora 14, more and more people will query the feature pages. We'd love to know that what they find is current and correct.
* 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>


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


More information:
If you're looking for a way to dip your toes in the water, so to
  Fedora 14 Schedule<ref>https://fedoraproject.org/wiki/Releases/14/Schedule</ref>
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>


  Fedora Feature Process<ref>https://fedoraproject.org/wiki/Features/Policy</ref>
As a reminder, the wiki drafts of beats are due on 12 September."


<references/>
<references/>


====Licensing Guidelines Update - Please Read====
=== 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.


[[User:spot|Tom "spot" Callaway]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631.html</ref> a revised Red Hat licensing guidelines:
'''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


"Hello Fedora!
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


Please take a moment and read this email. There's cake in it for you.
<references/>


Upon the advice of Red Hat Legal, we have slightly amended the Fedora Licensing Guidelines<ref>https://fedoraproject.org/wiki/Packaging:LicensingGuidelines</ref>. The following section has been added:
====New bodhi release in production====


  Subpackage Licensing
* 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>


  If a subpackage is dependent (either implicitly or explicitly) upon a
"A new release of Bodhi has just been deployed to production.
  base package (where a base package is defined as a resulting binary
<ref>https://admin.fedoraproject.org/updates</ref>
  package from the same source RPM which contains the appropriate
  license texts as %doc), it is not necessary for that subpackage to
  also include those license texts as %doc.


  However, if a subpackage is independent of any base package (it does
Bugs and enhancement requests can be filed here:
  not require it, either implicitly or explicitly), it must include
<ref>http://bodhi.fedorahosted.org</ref>
  copies of any license texts (as present in the source) which are
  applicable to the files contained within the subpackage.


*****
Major changes in bodhi 0.9.2
---------------------------------


Basically, what this means is this: If you maintain a package, and that package generates subpackages, then each subpackage must either include a copy of the appropriate licensing texts (as available in the source), or it must Require (either implicitly or explicitly) another subpackage which does include the appropriate licensing texts.
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


Unfortunately, there is no good way for us to determine which packages are out of compliance with this new guideline and will need to be fixed. (If http://rpm.org/ticket/116 was ever implemented, it would be possible...) However, we can identify packages which are likely
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
candidates to be affected by this change. Thanks to Seth Vidal, I was able to generate a list of packages and subpackages, sorted by
maintainer. The list was generated by querying rawhide for a list of source packages where:


* At least one subpackage was generated that did not have an exact name match to the source package name AND
* The submitter of an update can no longer effect the karma (Till Maas)


* That subpackage did not depend on any other source packages.
* Fix duplicate status change email notifications. (Till Maas)


Maintainers should look at the bottom of this email for the list.
* Mention age of updates in testing digest mails (Till Maas)


=====FAQ=====
* Support e-mail threading in notification e-mails (Till Maas)


Q. Why are we doing this?
* Add X-Bodhi mail headers (Till Maas)
A. The intent is to ensure that the appropriate license texts (as available in the source) are installed on the running system for all
binary packages.


Q. Should I add explicit Requires: to another subpackage for the sole reason of complying with this new guideline?
* Gracefully handle private bugs (Cole Robinson)
A. No. You should not add Requires simply for this licensing requirement. Instead, you should include duplicate copies of the
relevant license texts (as available in the source).


Q. I thought duplicating files in a spec was forbidden?
* Set the default request for new updates to 'testing' in the web form
A. This is a permitted exception to that.


Q. You keep saying "as available in the source", what does that mean?
* 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.
A. It means you do not need to manually add license texts if they are not included by the upstream in the source tarball. However, if they are missing, you should ask upstream to add them.


Q. My package generates a -docs (or -javadocs) subpackage, which doesn't depend on any of the other subpackages, but the docs are under a
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
different license from the code in the other subpackage(s), what should I do?
A. You should make sure that the -docs/-javadocs subpackage has the correct License: tag, matching the files included, and be sure that the
appropriate license texts are included as %doc in the -docs/-javadocs.


Q. My package generates a foo and foo-libs package. foo has the license files, and foo depends on foo-libs, but foo-libs doesn't have any
license files in it. What should I do?
A. You have two options here. You can either move the license texts from foo to foo-libs or duplicate the license texts in both packages. Moving the license texts is an acceptable option in this case because it ensures that if foo-libs is installed, the license texts are present, and if foo is installed, it will pull in foo-libs, thus, the license texts are present.


Q. What is the capital of the Republic of Ghana?
Full list of changes since 0.8.7
A. Accra.
--------------------------------


Q. What happens if I don't do this?
Kalpa Welivitigoda (1):
A. Well, eventually, I'll go through and make the change myself. You will also suffer a horrible horrible curse.
      fixed input box alignment issue in login box #579


Q. Do I need to make this change in stable branches?
Luke Macken (25):
A. No, but you can if you want to. Rawhide is the only place that is a MUST fix.
      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'


Q. Do I need to push an update for this change?
Mathieu Bridon (6):
A. No, please don't. If you're already working on an update for other reasons and you want to do this (say, to keep the spec in sync with
      Have bodhi-init create all the tables
rawhide), you can.
      masher: Fix the comparison
      masher: Reuse variable
      setup: Fix the Turbogears version requirement
      Don't version control auto-generated files
      setup: Add missing dependencies


Q. Do I need to build (not just commit) this change in rawhide?
Ralph Bean (19):
A. Please do. Don't forget to bump the release and add a changelog entry.
      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.


Q. Why can't we just have a "fedora-licenses" package which has copies of all the licenses in Fedora and just always install it?
Till Maas (8):
A. Maintaining that package would be a huge pain. We have a LOT of licenses in Fedora and they change all the time, often without notice.
      Add X-Bodhi mail headers
However, if you'd like to write some code to help us minimize duplicate license files on the filesystem with a "common-licenses" package, then you should look at<re>http://rpm.org/ticket/116</ref>. Have I mentioned that I'd like that functionality added to rpm?
      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"


Q. Why don't you add that functionality to rpm?
<references/>
A. Everytime I look at the rpm source code, blood starts dripping from my eyes, and it scares my newborn son, Jimmy. It also makes it hard to see the code.


Q. Some of the packages on your list don't need any changes to meet this guideline, what should I do?
====Build F-18 collection packages for all language translators====
A. I'm sure there are some false positives here. Heck, _most_ of my packages which were flagged by this script did not need any changes, but
some of them did. The only way to be sure was to have an informed human check. Just let me know that you checked them and they're okay. Please do this by sending me email, either by replying to this email on the list or emailing me directly. Telling me via
IRC/AIM/Twitter/Facebook/Identi.ca/LinkedIn/MySpace/ICQ/CarrierPigeon just means I will forget about it.


Q. Hey, one of my packages didn't end up on your list, but it needed to be fixed to meet this guideline, why wasn't it on the list?
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
A. There are plenty of other situations that we couldn't account for where a package would need to be changed to meet this guideline. If you
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>
think about it for a while, I'm sure you can come up with some. The case that Seth scripted was simply the most common one I could think of.


Q. I fixed my packages! Now what?
"Hi Fedora package maintainers
A. Please email me (either in reply to this email on the mailing list, or in private) and let me know which packages you fixed.


Q. What about the packages owned by "orphan"?
Please build and push your package with latest translation file (e.g.
A. Well, it sure would be nice if a provenpackager could check these packages and fix them as appropriate, then let me know (via email).
pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31.
Thats the sort of thing that makes me feel like buying you a drink the next time our paths cross. But hey, if no one does it, I'll get to it eventually.
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.


Q. What about new packages?
Thank you so much.
A. All packages from this moment onward must meet this requirement. New packages, old packages, red packages, blue packages.


Q. I have another question which you did not answer here?
noriko
A. Ask me, I'll do my best to answer.
Fedora Localization Project"


Q. I'm confused by all of this?
<references/>
A. Sorry. Let me know what you don't understand and I'll try to make it clearer.


Q. Why are you always making me do things?
====Fedora 18 Alpha to slip by another one week====
A. Because I can! No, really, this is one of those "things we should have been doing all along", so we need to just bite the bullet and get
it done.


Q. Hey you promised me cake, I read all this way! Where is my cake?
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
A.
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
          )
        (.)
        .|.
        l7J
        | |
    _.--| |--._
  .-';  ;`-'& ; `&.
& &  ;  &  ; ;  \
\      ;    &  &_/
  F"""---...---"""J
  | | | | | | | | |
  J | | | | | | | F
  `---.|.|.|.---'


What? You thought the cake was a lie?
"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.


Okay. Here's the list of packages that I think might be affected by this. Reminder: You need to check these packages and fix any which need
The next Go/No-Go meeting is on Thursday Sep 06, same place
fixing, then email me and let me know which ones you checked/fixed. Thanks!
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).


=====Editor===== please see the original posting<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631.html</ref> for the list of packages, as it is quite long. 
If you have an accepted blocker bug, please try to fix it
as soon as possible to help us with Fedora 18 Alpha release!"


~spot"
<references/>
 
 
=== Fedora Events ===


<references/>
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.


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


<references/>
<references/>
Line 278: Line 372:
* [[Event reports]] -- guidelines and suggestions.
* [[Event reports]] -- guidelines and suggestions.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
===Fedora Press Releases===
Fedora press releases will be found at the link:
http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Latest revision as of 11:18, 31 August 2012

Announcements

Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

  1. ↑ http://lists.fedoraproject.org/pipermail/announce/
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
  3. ↑ http://fedoraproject.org/wiki/Events

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

  • Contributor: [[User:Spot|Tom Callaway][1]
  • Posted Date: Wed Aug 1 19:28:57 UTC 2012[2]

"A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. [3]

---

The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. [4]

---

The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. [5] [6] [7]

---

A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. [8]

---

A new section on the Documentation= field in systemd unit files (F17+) has been added. [9]

---

A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. [10]

---

The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. [11]

---

These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).

Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.

As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: [12]"

Enclosure: Here is one late change to the Fedora Packaging Guidelines:[13] [14] [15]

  1. ↑ Tom Callaway tcallawa at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html
  3. ↑ https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism
  4. ↑ https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review
  5. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement
  6. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires
  7. ↑ https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version
  8. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros
  9. ↑ https://fedoraproject.org/wiki/Packaging:Systemd#Documentation_field
  10. ↑ https://fedoraproject.org/wiki/Packaging:Guidelines#Group_tag
  11. ↑ https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file
  12. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
  13. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html
  14. ↑ https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
  15. ↑ https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

  • Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron][1]
  • Posted Date: Fri Aug 3 17:00:53 UTC 2012[2]

"Greetings! (...or perhaps I should say.... bonjour!)

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

If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request.

To place a subsidy request, please follow these steps:

1: Pre-register at [3] - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: [4]

Additionally, a few notes regarding the hotel in Paris:

There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :)

We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire.

For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: [5]"

  1. ↑ rbergero at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html
  3. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration
  4. ↑ https://fedorahosted.org/fudcon-planning/wiki/FundingRequest
  5. ↑ http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel

Fedora Infrastructure announces status.fedoraproject.org

  • Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ][1]
  • Posted Date: Thu Aug 30 20:31:24 UTC 2012[2]

"I'm happy to announce the general availability of our status.fedoraproject.org site.

This site provides an easy way for Fedora contributors and users to check on the status of services provided by Fedora Infrastructure.

The site auto reloads every minute, and also provides a rss feed at [3].

If you run into a problem or issue that is not reflected at status.fedoraproject.org, please do report it to us in #fedora-admin on irc.freenode.net or via ticket at [4] We update the site status information manually so we need to be aware of the issue in order to keep the site accurate.

As with everything in Fedora Infrastructure, this application is open source. Source is available from: [5] and is released under a GPLv2+ license.

This application is hosted at the link[6] to avoid any issues with outages in our infrastructure affecting status reporting. "

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html
  3. ↑ http://status.fedoraproject.org/changes.rss of any changes
  4. ↑ https://fedorahosted.org/fedora-infrastructure/newticket
  5. ↑ http://git.fedorahosted.org/git/fedora-status.git
  6. ↑ https://openshift.redhat.com

Beats are open!

  • Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton][1]
  • Posted Date: Tue Aug 28 15:35:59 UTC 2012[2]

"The Release Notes beats for Fedora 18 are now open: [3]

If you're looking for a way to dip your toes in the water, so to speak, writing a beat is a great way to get started. If you're a regular, don't forget about the checkBeat program: [4]

As a reminder, the wiki drafts of beats are due on 12 September."

  1. ↑ kevin at scrye.com
  2. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html
  3. ↑ https://fedoraproject.org/wiki/Category:Documentation_beats
  4. ↑ http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above
  1. ↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce

New bodhi release in production

  • Contributor: [[User:Lmacken|Luke Macken ][1]
  • Posted Date: Thu Aug 9 21:53:41 UTC 2012[2]

"A new release of Bodhi has just been deployed to production. [3]

Bugs and enhancement requests can be filed here: [4]

Major changes in bodhi 0.9.2

  • fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  • Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  • The submitter of an update can no longer effect the karma (Till Maas)
  • Fix duplicate status change email notifications. (Till Maas)
  • Mention age of updates in testing digest mails (Till Maas)
  • Support e-mail threading in notification e-mails (Till Maas)
  • Add X-Bodhi mail headers (Till Maas)
  • Gracefully handle private bugs (Cole Robinson)
  • Set the default request for new updates to 'testing' in the web form
  • Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  • Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Full list of changes since 0.8.7

Kalpa Welivitigoda (1): 

     fixed input box alignment issue in login box #579

Luke Macken (25): 

     Convert our tags_url to a byte string before passing it to urlgrabber.
     Add a script to detect when older builds become the 'latest' in stable
     Update our test suite to reproduce ticket [ticket:683]
     Fix a bug in our critpath policy ([ticket:683]).
     Set the default request for new updates to 'testing'
     Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
     Fix a busted unit test (test_push_EPEL_critpath_before_tested)
     Add pkg_resources __requires__ hacks to bodhi tools to mitigate version

conflicts 

     Handle the case where a release doesn't have any overrides
     Change our X-Bodhi-Update-Release header to use the short name
     Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
     Update our unit tests to assume submitters cannot alter karma
     Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
     Merge branch 'feature/bodhi1-fedmsg' into develop
     Fix a typo in the metrics tool
     Fix a typo in the new mail headers
     Re-organize our links, and add one to the new update feedback guidelines
     Clean up stray buildroot overrides
     Version bump for 0.9.2
     Our build script uses bz2
     Merge branch 'release/0.9.2'

Mathieu Bridon (6): 

     Have bodhi-init create all the tables
     masher: Fix the comparison
     masher: Reuse variable
     setup: Fix the Turbogears version requirement
     Don't version control auto-generated files
     setup: Add missing dependencies

Ralph Bean (19): 

     Sending messages with fedmsg.
     No longer using fedmsg schema/validation.
     fedmsg.ini -> fedmsg-config.py
     More detail in the update.complete message.
     More concise send_message calls.
     Ignore dev db.
     Merge branch 'master' into bodhi1-fedmsg
     Updates for the latest fedmsg.  Getting tests passing.
     Merge branch 'master' into bodhi1-fedmsg
     Ignore mashing fedora file.
     Fixed what I think is a regression in login template.
     Merge branch 'master' into bodhi1-fedmsg
     Update to test fedmsg config.  Work with both tests and under WSGI.
     Version bump for fedmsg in staging.
     Only send the comment with a comment is added, not the whole update.
     Using a "bodhi" user/group for mod_wsgi.
     fedmsg+ssl changes to bodhi.spec.
     Use modern fedmsg config format.
     Disable message signing for bodhi tests.

Till Maas (8): 

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial
     model.py: Change karma from Submitter to 0
     Fix notification on automatic status change"
  1. ↑ lmacken at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html
  3. ↑ https://admin.fedoraproject.org/updates
  4. ↑ http://bodhi.fedorahosted.org

Build F-18 collection packages for all language translators

  • Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto][1]
  • Posted Date: Thu Aug 30 09:17:01 UTC 2012[2]

"Hi Fedora package maintainers

Please build and push your package with latest translation file (e.g. pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. Your packages with latest translation will be composed into test live image on 3-Sep Monday. Then various language translators worldwide will test the image in their own languages. Any issue will be filed as bug. This is only one chance for translators to check and modify Localization quality of your packages by checking UI, and we need your help.

Thank you so much.

noriko Fedora Localization Project"

  1. ↑ noriko.mizumoto at gmail.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html

Fedora 18 Alpha to slip by another one week

  • Contributor: [[User:JaroslavReznik|Jaroslav Reznik][1]
  • Posted Date: Thu Aug 30 23:26:35 UTC 2012[2]

"Today at Go/No-Go meeting it was decided to slip Fedora 18 Alpha release by one week due to remaining open blocker bugs[3] and incomplete test matrices for Alpha [4][5][6]. Meeting's full log is at [7].

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

The next Go/No-Go meeting is on Thursday Sep 06, same place but different time (19:00 UTC, 3 PM EDT, 21:00 CEST

  1. fedora-meeting).

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

  1. ↑ jreznik at redhat.com
  2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html
  3. ↑ http://qa.fedoraproject.org/blockerbugs/current
  4. ↑ https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
  5. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
  6. ↑ http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
  7. ↑ http://bit.ly/PC16PF


Fedora Events

The purpose of Fedora Event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning and press releases.

Upcoming Events (September 2012 - November 2012)

  • North America (NA)[1]
  • Central & South America (LATAM)[2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Guideline to write Fedora Press Releases[5]

  1. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29
  2. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29
  3. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2
  4. ↑ http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3
  5. ↑ https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release

Past Events

Archive of Past Fedora Events[1]

  1. ↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.

Fedora Press Releases

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

Retrieved from "https://fedoraproject.org/w/index.php?title=FWN/Beats/Announcements&oldid=300097"