From Fedora Project Wiki

< FWN‎ | Beats

 
(15 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===
  
====Fedora 18 release name by [[User:Rbergero|Robyn Bergeron]] published on Mon Apr 30 13:51:00 UTC 2012 ====
+
====[Guidelines Change] Changes to the Packaging Guidelines====  
  
News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003067.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>
  
"Thank you to everyone who participated in voting for the Fedora 18
+
"A new section has been added to the SysV Initscripts section, discussing
release name. The name for Fedora 18, the follow-up to Beefy Miracle,
+
the proper use of subsys locking. Even though Fedora packages should no
is:
+
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>
  
      Spherical Cow
+
---
  
Voting period:  Friday 2012-04-20 00:00:00 to Friday 2012-04-27 00:00:00
+
The review guidelines now reflect the use of sha256sum (instead of
Number of valid ballots cast: 429
+
md5sum) to confirm upstream source integrity.
 +
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
  
Using the range voting method, each candidate could attain a maximum
+
---
of (429*8) = 3,432
 
  
Results:
+
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>
  
Votes :: Name
+
---
-------------------------------
 
** 1359 :: Spherical Cow
 
** 1087 :: Halva
 
** 1072 :: Chamoy
 
** 1035 :: Pamukkale
 
** 964 :: Tandoori Chicken
 
** 930 :: Frankfurter
 
** 821 :: Pop Soda
 
** 536 :: Ketchy Ketchup"
 
  
<references/>
+
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>
 +
 
 +
---
  
====Formally announcing FUDCon: Paris and FUDCon: Lawrence by [[User:Rbergero|Robyn Bergeron]] published on Tue May 8 14:06:41 UTC 2012==== 
+
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>
  
News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003068.html</ref>,
+
---
  
"As many of you know, FUDCon is the abbreviation for Fedora Users and
+
The RHEL conditionalization has been removed from the Python3 example
Developers Conference, an event we typically hold 4 times per year in
+
spec file, as it is no longer valid.
various regions of the world. These events are proposed and arranged
+
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
largely by Fedora contributors, and are designed to be events where
 
contributors and those new to Fedora can learn, share, hack, and
 
participate in various aspects of the Fedora Project.
 
  
It is with great pleasure that I am formally announcing two upcoming
+
---
FUDCons:
 
  
'''FUDCon for the EMEA region in 2012 will be held in Paris, France,
+
These guidelines (and changes) were approved by the Fedora Packaging
October 13-15, 2012 <ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012</ref>'''.  This particular event will be held over those
+
Committee (FPC).
days in two locations; the first day, Saturday the 13th, will be held at
 
the Eurosites Georges V facility, in conjunction with the Open World
 
Forum (OWF) <ref>http://www.openworldforum.org/</ref>, and on the 14th and 15th at Universcience. I'd like to
 
thank Kevin Raymond and the rest of the FUDCon Paris team for putting
 
together this bid, and for working with OWF to procure space during that
 
event for the first day of FUDCon; I think that this will be an
 
interesting opportunity to showcase Fedora to a captive audience that is
 
passionate about open source.  I would also like to thank the other
 
teams who submitted bids for the EMEA region.
 
  
'''The next FUDCon for North America will be held in Lawrence, Kansas, on
+
'''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.'''
the 18th through 20th of January, 2013 <ref>http://fedoraproject.org/wiki/FUDCon:Lawrence_2013</ref>, at the University of
 
Kansas'''.  While you can peruse the bidding page <ref>http://fedoraproject.org/wiki/FUDCon:Bid_for_Lawrence_2013#About_Lawrence</ref> for details, I'd like
 
to note that Lawrence is home to many awesome things: It is the birth
 
place of the Django Project, was pinpointed as the "center of the earth"
 
in Google Earth, was the home of William Burroughs, is the location of  
 
the awesomely-named Free State Brewing Company, has been named a top-ten
 
college town, and most importantly, is the collegiate location of our
 
resident Wiki Czar and Doer of Stuff, Ian Weller, who, as you may have
 
guessed, was also the author of this FUDCon bid. A big thank-you! to Ian
 
for volunteering to put this together.
 
  
FUDCon planning continues, in grand tradition, to be open to everyone
+
As a reminder: The Fedora Packaging Guidelines are living documents! If
for participation; if you are interested in contributing to the
+
you find something missing, incorrect, or in need of revision, you can
discussion or lending a helping hand, I encourage you to subscribe to
+
suggest a draft change. The procedure for this is documented here:
the FUDCon planning mailing list <ref>http://lists.fedoraproject.org/mailman/listinfo/fudcon-planning</ref>.
+
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
  
Cheers,"
+
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/>
  
====Appointment to the Fedora Board, and Elections Reminder by [[User:Rbergero|Robyn Bergeron]] published on Tue May 8 17:29:41 UTC 2012====
+
====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>
  
News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003069.html</ref>,
+
"Greetings! (...or perhaps I should say.... bonjour!)
  
"I'm pleased to announce the appointment of Garrett Holmstrom to the  
+
I'd like to share a few reminders and announcements regarding the  
Fedora Board.  In this election cycle, three Board seats are open for
+
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
election, and two Board appointee seats are open; the first appointee,  
 
Garrett, is being appointed prior to nominations opening, and the second
 
will be appointed after elections are completed.
 
  
Garrett (aka: gholms) has been involved in the Cloud SIG since the
+
If you are planning to attend FUDCon and need a travel subsidy to do so,  
"early days" (early 2010, to be more precise), as the maintainer of the
+
the ticketing system is now open for those requestsRequests will be  
euca2ools packageAs the group has progressed, he's taken on a number
+
accepted through August 15, 2012. Please note that funding requests
of tasks, doled out much advice and opinion, and has shown himself to be  
+
without a ticket will not be considered. Preference will be given to  
an excellent leader and communicator.  He's also a regular in the
+
attendees from the EMEA region who are actively contributing to Fedora,
#fedora-devel channel, willing to help out and answer questions as he
+
and have detailed their participation plans for FUDCon in their request.
can. I'm delighted that he has agreed to serve on the Board; I believe
 
that, as a community, we should constantly strive to nurture and grow
 
new leadership, and I think that Garrett's communication skills and
 
positive attitude will be a fantastic asset to the Board as Fedora  
 
continues to evolve.
 
  
Garrett will be taking seat A3, previously held by Rudi Landmann. (And a
+
To place a subsidy request, please follow these steps:
big thank you to Rudi for his contributions as a Fedora Board member --
 
your time and efforts are greatly valued!)
 
  
I'd also like to remind everyone of the ongoing elections process;
+
1: Pre-register at
today, May 8th, is the last day to submit questions to the elections
+
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
questionnaire.  Beginning tomorrow, May 9th, nominations for the Board,
+
put an X in the $$$ column
FESCo, and FAmSCo will be open, closing on May 15th.
+
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>
  
Additional information about Elections can be seen here:
+
Additionally, a few notes regarding the hotel in Paris:
<ref>http://fedoraproject.org/wiki/Elections</ref>
 
  
A complete history of Board Members is available here:
+
There are other events in Paris during this time period; most notably,
<ref>http://fedoraproject.org/wiki/Board/History</ref>
+
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. :)
  
Cheers,"
+
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/>
  
====The Future of release names by [[User:Toshio|Toshio Kuratomi]] published on Wed May 9 08:39:18 UTC 2012 ====   
+
====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>
  
News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003070.html</ref>,
+
"I'm happy to announce the general availability of our
 +
status.fedoraproject.org site.  
  
"At the last Board Meeting, the Board looked at the poll results asking
+
This site provides an easy way for Fedora contributors and users to
whether people felt like continuing to name releases.  The results seemed
+
check on the status of services provided by Fedora Infrastructure.
to show that many people do like having a name associated with Fedora
 
releases.  However, the discussion before and after has shown there is
 
a desire to improve upon the current method of selecting the names.
 
  
The Board decided that it would be worthwhile to come up with a new
+
The site auto reloads every minute, and also provides a rss feed at
procedure for selecting the name for the Fedora 19 release and beyond to
+
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  
attempt to solve some of the issues that have been brought up. The Board
 
is looking for volunteers who would like to do two things:
 
  
(1) Answer the following questions:
+
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.
  
** What benefits does the Project get from the current release naming process?
+
As with everything in Fedora Infrastructure, this application is open
** What changes do people want to see in a revised process?
+
source. Source is available from:
 +
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
 +
and is released under a '''GPLv2+ license'''.
  
(2) Come up with at least one proposal and analyze it according to the answers to the previous questions.
+
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. "
  
If anyone is interested in coming to a weekly meeting to work on this,
+
<references/>
please feel free to contact me.  If anyone would like to champion this,
 
please contact me ASAP so I know whether there is someone else who's going
 
to champion this or if I need to lead the effort.
 
  
I've put up a wiki page that tries to summarize the answers to the first two
+
====Beats are open!====
questions that I've seen circulated on the advisory-board mailing list and a
+
 
link to the only proposal I currently know of (mizmo's proposal to use
+
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
a single theme for all of the new Fedora releases)."
+
* 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."
  
 
<references/>
 
<references/>
Line 180: Line 194:
 
<references/>
 
<references/>
  
====exiv2-0.23 coming soon====  
+
====New bodhi release in production====
 +
 
 +
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
 +
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
 +
 
 +
"A new release of Bodhi has just been deployed to production.
 +
<ref>https://admin.fedoraproject.org/updates</ref>
 +
 
 +
Bugs and enhancement requests can be filed here:
 +
<ref>http://bodhi.fedorahosted.org</ref>
 +
 
 +
Major changes in bodhi 0.9.2
 +
---------------------------------
 +
 
 +
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
 +
 
 +
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
 +
 
 +
* The submitter of an update can no longer effect the karma (Till Maas)
 +
 
 +
* Fix duplicate status change email notifications. (Till Maas)
 +
 
 +
* Mention age of updates in testing digest mails (Till Maas)
 +
 
 +
* Support e-mail threading in notification e-mails (Till Maas)
 +
 
 +
* Add X-Bodhi mail headers (Till Maas)
 +
 
 +
* Gracefully handle private bugs (Cole Robinson)
 +
 
 +
* Set the default request for new updates to 'testing' in the web form
 +
 
 +
* Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  
[[User:Rdieter|Rex Dieter]]<ref>rdieter at math.unl.edu</ref> on Wed Apr 25 13:07:31 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000921.html</ref>,
+
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)
  
"I plan on importing exiv2-0.23 into rawhide soon'ish.  It includes an
 
ABI bump, so dependent packages will require rebuilding, including:
 
* calligra
 
* darktable
 
* entangle
 
* geeqie
 
* gipfel
 
* gnome-color-manager
 
* gnome-commander
 
* gpscorrelate
 
* gthumb
 
* gwenview
 
* hugin
 
* immix
 
* kde-runtime
 
* krename
 
* libextractor
 
* libgexiv2
 
* libkexiv2
 
* luminance-hdr
 
* merkaartor
 
* oyranos
 
* pyexiv2
 
* rawstudio
 
* strigi
 
* ufraw
 
  
I'll take care of kicking off a round of rebuilds for these."
+
Full list of changes since 0.8.7
 +
--------------------------------
 +
 
 +
Kalpa Welivitigoda (1):
 +
      fixed input box alignment issue in login box #579
 +
 
 +
Luke Macken (25):
 +
      Convert our tags_url to a byte string before passing it to urlgrabber.
 +
      Add a script to detect when older builds become the 'latest' in stable
 +
      Update our test suite to reproduce ticket [ticket:683]
 +
      Fix a bug in our critpath policy ([ticket:683]).
 +
      Set the default request for new updates to 'testing'
 +
      Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
 +
      Fix a busted unit test (test_push_EPEL_critpath_before_tested)
 +
      Add pkg_resources __requires__ hacks to bodhi tools to mitigate version
 +
conflicts
 +
      Handle the case where a release doesn't have any overrides
 +
      Change our X-Bodhi-Update-Release header to use the short name
 +
      Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
 +
      Update our unit tests to assume submitters cannot alter karma
 +
      Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
 +
      Merge branch 'feature/bodhi1-fedmsg' into develop
 +
      Fix a typo in the metrics tool
 +
      Fix a typo in the new mail headers
 +
      Re-organize our links, and add one to the new update feedback guidelines
 +
      Clean up stray buildroot overrides
 +
      Version bump for 0.9.2
 +
      Our build script uses bz2
 +
      Merge branch 'release/0.9.2'
 +
 
 +
Mathieu Bridon (6):
 +
      Have bodhi-init create all the tables
 +
      masher: Fix the comparison
 +
      masher: Reuse variable
 +
      setup: Fix the Turbogears version requirement
 +
      Don't version control auto-generated files
 +
      setup: Add missing dependencies
 +
 
 +
Ralph Bean (19):
 +
      Sending messages with fedmsg.
 +
      No longer using fedmsg schema/validation.
 +
      fedmsg.ini -> fedmsg-config.py
 +
      More detail in the update.complete message.
 +
      More concise send_message calls.
 +
      Ignore dev db.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Updates for the latest fedmsg.  Getting tests passing.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Ignore mashing fedora file.
 +
      Fixed what I think is a regression in login template.
 +
      Merge branch 'master' into bodhi1-fedmsg
 +
      Update to test fedmsg config.  Work with both tests and under WSGI.
 +
      Version bump for fedmsg in staging.
 +
      Only send the comment with a comment is added, not the whole update.
 +
      Using a "bodhi" user/group for mod_wsgi.
 +
      fedmsg+ssl changes to bodhi.spec.
 +
      Use modern fedmsg config format.
 +
      Disable message signing for bodhi tests.
 +
 
 +
Till Maas (8):
 +
      Add X-Bodhi mail headers
 +
      Support e-mail threading in notification e-mails
 +
      Mention age of updates in testing digest mails
 +
      Use format string instead of string concatenation
 +
      Import exceptions from sqlite3
 +
      Remove files used by mercurial
 +
      model.py: Change karma from Submitter to 0
 +
      Fix notification on automatic status change"
  
 
<references/>
 
<references/>
  
====Announcing easyfix====  
+
====Build F-18 collection packages for all language translators====
  
[[User:Pingou|Pierre-Yves Chibon]]<ref>pingou at pingoured.fr</ref> on Thu Apr 26 09:12:28 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000922.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>
  
"Good news everyone (© Farnsworth),
+
"Hi Fedora package maintainers
  
The easyfix project is now live:
+
Please build and push your package with latest translation file (e.g.
<ref>http://fedoraproject.org/easyfix/</ref>
+
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.
  
As a new-comers, you will be able to find a list of projects which have
+
noriko
bugs/requests considered to be easy to work on (ie: you do not need a
+
Fedora Localization Project"
deep understanding of the project to fix/implement it).
 
The projects are divers and the tickets broad : from fixing typo, add a
 
link in a template (dev) to add a node to nagios monitoring (sysadmin)
 
via making the fedoraproject.org page w3c valid (websites).
 
So everyone should be able to find for his taste.
 
  
 +
<references/>
  
As upstream, you will have a way to attract new-comers to your project
+
====Fedora 18 Alpha to slip by another one week====
and fixing easier tasks while you focus on the harder/more complex
 
one ;-)
 
  
 +
* 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>
  
Easyfix gathers the tickets from fedorahosted and bugzilla.
+
"Today at Go/No-Go meeting it was decided to slip Fedora 18
If your project hosted on fedorahosted.org and you would like to have it
+
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
included, the instruction are on the wiki:
+
full log is at <ref>http://bit.ly/PC16PF</ref>.
<ref>https://fedoraproject.org/wiki/Easyfix</ref>
+
 
If you have bugzilla ticket which you consider easy to fix (remember,
+
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
easy for a new-comer != easy for you!), feel free to add the 'EasyFix'
+
will be pushed out by one week.
keyword to the bugzilla ticket.
+
 
Hope this helps..."
+
The next Go/No-Go meeting is on Thursday Sep 06, same place
 +
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
 +
#fedora-meeting).
 +
 
 +
If you have an accepted blocker bug, please try to fix it
 +
as soon as possible to help us with Fedora 18 Alpha release!"
  
 
<references/>
 
<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 (March 2012 - 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#FY13_Q1_.28March_2012_-_May_2012.29_3</ref>
 
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY13_Q1_.28March_2012_-_May_2012.29_3</ref>
 
  
 
<references/>
 
<references/>
Line 276: 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