From Fedora Project Wiki

< FWN‎ | Beats

(Updating the announcement beat)
No edit summary
 
(203 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:Rashadul|Rashadul Islam]]  
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>


===Fedora Announcement News===
===Breaking News of the Week and Month===
====Package update notifications fixed==== 
Jared K. Smith on Fri Jul 30 19:56:24 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-July/002843.html</ref>,


"Recent updates to Fedora introduced two unexpected bugs, either of which results in users no longer seeing notifications of or being able to apply new updates.
====[Guidelines Change] Changes to the Packaging Guidelines==== 


Updates to the relevant packages have been shipped to fix these issues, but users will not receive notifications for them unless they first apply the pending fixed updates using the "yum" tool. (Please note that these issues should only affect Fedora 13. Fedora 12 does not appear to be affected.)  Packages fixing these issues were pushed to the Fedora software repositories around July 22, 2010. Users who have done a manual "yum update" since that push may have already
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
received these fixes.
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>


To fix the issue, please:
"A new section has been added to the SysV Initscripts section, discussing
the proper use of subsys locking. Even though Fedora packages should no
longer be using SysV Initscripts as a primary service mechanism, Red Hat
Enterprise Linux and EPEL do. Additionally,
Red Hat points partners to the Fedora Guidelines when they build for RHEL.
<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Careful_Handling_of_.2Fvar.2Flock.2Fsubsys.2F.3Cservice_name.3E_mechanism</ref>


1. Open a Terminal (Applications > System Tools > Terminal)
---


2. Type either of the following commands and enter the password for
The review guidelines now reflect the use of sha256sum (instead of
the root user when prompted.
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>


a. To choose to apply all pending updates now:
---
  su -c "yum -y --skip-broken update"


b. To choose to apply updates fixing only the specific issues mentioned above:
The PHP Packaging guidelines have been updated to include guidance about
  su -c "yum -y --skip-broken update gnome-packagekit selinux-policy"
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>


3. Log out and and then log back in, or reboot your computer.  Note that logout/login will complete the fix for the notification issue. However, if you applied all updates in the previous step, you may need to reboot for other updates that require it.
---


We apologize for the inconvenience, and we are working on further improvements to our testing and quality assurance processes to avoid this and similar problems in the future.
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>


If you have any further questions or require additional assistance, please refer to <ref>https://fedoraproject.org/wiki/Communicating_and_getting_help</ref> for ways to get additional help from the Fedora community.
---


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


====Outage: SSL Cert - 2010-07-31 12:00 UTC==== 
The RHEL conditionalization has been removed from the Python3 example
Mike McGrath on Sat Jul 31 12:59:07 UTC 2010 announced <ref>http://lists.fedoraproject.org/pipermail/announce/2010-July/002844.html</ref>,
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


"There will be an outage starting at 2010-07-31 12:00 UTC, which will last approximately 3 hours?
---


To convert UTC to your local time, take a look at <ref>http://fedoraproject.org/wiki/Infrastructure/UTCHowto<ref>
These guidelines (and changes) were approved by the Fedora Packaging
or run:
Committee (FPC).


date -d '2010-07-31 12:00 UTC'
'''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.'''


=====Reason for outage=====
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>"


Our wildcard cert expired. Yes we've monitored this in the past. No we don't know why we weren't alerted this time, researching. The new purchase is in the works but we've run into some logistical issues. Will have it replaced as soon as possible.
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>


=====Affected Services=====
<references/>


* Bodhi - <ref>https://admin.fedoraproject.org/updates/</ref>
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 
* Docs - <ref>http://docs.fedoraproject.org/</ref>
* Email system
* Fedora Account System - <ref>https://admin.fedoraproject.org/accounts/</ref>
* Fedora Community - <ref>https://admin.fedoraproject.org/community/</ref>
* Main Website - <ref>http://fedoraproject.org/</ref>
* Mirror List - <ref>https://mirrors.fedoraproject.org/</ref>
* Mirror Manager - <ref>https://admin.fedoraproject.org/mirrormanager/</ref>
* Package Database - <ref>https://admin.fedoraproject.org/pkgdb/</ref>
* Spins - <ref>http://spins.fedoraproject.org/</ref>
* Start - <ref>http://start.fedoraproject.org/</ref>
* Translation Services - <ref>http://translate.fedoraproject.org/</ref>
* Wiki - <ref>http://fedoraproject.org/wiki/</ref>


=====Unaffected Services=====
* 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>


* BFO - <ref>http://boot.fedoraproject.org/</ref>
"Greetings! (...or perhaps I should say.... bonjour!)
* Buildsystem - <ref>http://koji.fedoraproject.org/</ref>
* CVS / Source Control
* DNS - ns1.fedoraproject.org, ns2.fedoraproject.org</ref>
* Fedora Hosted - <ref>https://fedorahosted.org/</ref>
* Fedora People - <ref>http://fedorapeople.org/</ref>
* Fedora Talk - <ref>http://talk.fedoraproject.org/</ref>
* Smolt - <ref>http://smolts.org/</ref>
* Torrent - <ref>http://torrent.fedoraproject.org/</ref>


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


<ref>https://fedorahosted.org/fedora-infrastructure/ticket/2300</ref>
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.


=====Contact Information=====
To place a subsidy request, please follow these steps:


Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage.
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>


<references/>
Additionally, a few notes regarding the hotel in Paris:


====Announcing FUDCon Tempe 2011 -- Jan. 29-31, 2011==== 
There are other events in Paris during this time period; most notably,
Jared K. Smith
our first day of FUDCon will be taking place at the Open World Forum
<ref>http://lists.fedoraproject.org/pipermail/announce/2010-August/002845.html</ref>
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. :)


In the past, the planning and execution of FUDCon events was handled completely by a few Red Hat employees.  This seemed out of alignment with the principles of Fedora, so in late January of this year, we kicked off an effort to fix that issue.  We wanted to increase the effectiveness and transparency of FUDCon, and our other premier Fedora events.  So we assembled a Fedora Activity Day specifically to change the way that we plan FUDCon.
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.


In accordance with those changes, we opened a bid process for FUDCon events.  The process encourages Fedora contributors to propose locations for the FUDCon event in their region, pursuant to their commitment to help with the logistics of the event. The first event that went through this lightweight process is the upcoming FUDCon in Zurich, Switzerland, which happens September 17-19, and is being planned by long-time Fedora contributors including Sandro Mathys and Marcus Moeller.  In April of this year, we opened bids for the next North American FUDCon event.
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/>


As a result of that process, and thanks to the continuing work of Fedora contributors Robyn Bergeron and Ryan Rix, our next community-powered, North American FUDCon event will be held in Tempe, Arizona from January 29-31, 2011, on the Arizona State University campus. We'd also like to thank Adam McCullough from the ASU LUG and the faculty of the ASU School of Computing, Informatics, and Decision Systems Engineering (CIDSE) for their invaluable assistance thus far.
====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>


FUDCon events are held around the globe each year. Our most recent event was held just a couple weeks ago in Santiago, Chile, where contributors from around the Latin American region gathered to exchange information, share ideas, and collaborate on various aspects of Fedora. In the past we've held other FUDCons in diverse places like Berlin, Porto Alegre, Brno, and Boston.
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


Our last North American FUDCon was in Toronto, Canada.  The year previous it was in Boston, MA.  We always encourage feedback from the contributors, and the one answer that popped up more often than any other was, "Let's go somewhere warm this coming winter!"  So we're pleased our fellow community members in a warmer part of the USA took up that challenge, and stepped forward to work on organizing the next FUDCon.
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


With that warmer climate in winter, of course, comes higher demand for travel lodging where people vacation. So as with previous FUDCons, we'll once again provide travel subsidies for contributors. Furthermore, our sponsor Red Hat is making an even larger commitment to these subsidies than in previous years, to offset the higher lodging costs. We all want to do our part to help everyone stay together at the conference, for the best possible collaborative experience after hours -- because collaboration is what FUDCon is all about!
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  


* * *
If you run into a problem or issue that is not reflected at
status.fedoraproject.org, please do report it to us in #fedora-admin on
irc.freenode.net or via ticket at
<ref>https://fedorahosted.org/fedora-infrastructure/newticket</ref>
We update the site status information manually so we need to be aware
of the issue in order to keep the site accurate.


As in the past, we encourage our community members to get involved by offering talks and other sessions of interest. The content provided by the attendees is what makes FUDCon events so special and exciting. Over the next few days planners will be setting up more information at the event wiki page: <ref>http://fedoraproject.org/wiki/FUDCon:Tempe_2011</ref>
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'''.


We'll have more details appearing soon there, including but not limited to:
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
issues with outages in our infrastructure affecting status reporting. "


* A schedule that makes it easier to see more of the talks you enjoy and value
<references/>


* Lightning talks and hackfest pitches to get attendees excited and motivated to collaborate
====Beats are open!====


* The ever popular FUDPub event!
* 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>


We hope you'll join us for the best North American FUDCon yet.  If you want to get involved and help plan the details of the event, you're welcome to join our planning list:<ref>http://lists.fedoraproject.org/mailman/listinfo/fudcon-planning</ref>
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


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


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


====Red Hat Bugzilla 3.6 Upgrade Public Beta==== 
<references/>
[[User:Jlaska|James Laska]]<ref>James Laska</ref> on Thu Jul 22 11:55:49 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000639.html</ref>,
" I am sending this on behalf of Dave Lawrence and the bugzilla team at Red Hat.  Please forward this on to any appropriate lists that were missed.


> Greetings,
=== 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.


> The Red Hat Bugzilla team is happy to announce the first public beta release of the next version of Red Hat Bugzilla based on the upstream 3.6 code base.
'''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


> Please test drive at:
'''Unacceptable Types of Announcements'''
>
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


>      <ref>https://partner-bugzilla.redhat.com</ref>
<references/>
>  


> Over the years Red Hat has made substantial customizations to Bugzilla to fit into the Engineering tool chain. Over time the upstream has incorporated some of these customizations or solved them in different ways. Upgrading reduces our customization footprint (and thus maintenance) while bringing many bug fixes & enhancements.
====New bodhi release in production====
>


> The main area of focus for our public betas is stability. Functionality that currently works in our 3.4 code base should
* Contributor: [[User:Lmacken|Luke Macken ]<ref>lmacken at redhat.com</ref>
> continue to work as expected in the new 3.6 release. These include various ajax optimizations, needinfo actor support, frontpage.cgi, product
* Posted Date: Thu Aug 9 21:53:41 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000961.html</ref>
> browser, several various UI enhancements, and of course the XMLRPC API.
>  


> Please feel free to point your various scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly.
"A new release of Bodhi has just been deployed to production.
>  
<ref>https://admin.fedoraproject.org/updates</ref>


> There are numerous other changes behind the scenes that we haven't> listed. The goal is to make sure that functionality that people have come to expect in 3.4 is possible in the new system.
Bugs and enhancement requests can be filed here:
>  
<ref>http://bodhi.fedorahosted.org</ref>


> There are also numerous new features/fixes that are part of the upstream 3.6 release. For more detailed information on what has changed since the last release, check out the release notes page at <ref>https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html</ref> .
Major changes in bodhi 0.9.2
>
---------------------------------


> The database is a recent snapshot of the live database so should be useful for testing to make sure the information is displayed properly and changeable. Also with a full snapshot it is possible to test for any performance related issues. Email has been disabled so that unnecessary spam is not sent out. So feel free to make changes to bugs to verify proper working order.
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
>


> We are asking for everyone to get involved as much as possible with testing and feedback on the beta releases to help us make this the most robust and stable release possible.
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
>
> Please file any enhancement requests or bug reports in our current Bugzilla system at <ref>https://bugzilla.redhat.com</ref> . File them under the Bugzilla product and relevant component with the version 3.6. With everyone's help we can make this a great release.
>


> Thanks The Red Hat Bugzilla Team"
* The submitter of an update can no longer effect the karma (Till Maas)


<references/>
* Fix duplicate status change email notifications. (Till Maas)


====Fedora 14 branching and dist-git roll out==== 
* Mention age of updates in testing digest mails (Till Maas)
[[User:JesseKeating|Jesse Keating]]<ref>Jesse Keating</ref> on Sat Jul 24 06:54:53 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000640.html</ref>,"Hey all!  It's that time again, we're gearing up to branch for Fedora 14 this coming Tuesday!  There is a major twist this time around, we're going to attempt a roll out of dist-git!


Dist-git is our replacement for the CVS system we are currently using. This is a pretty big deal, but we're going to try to make it as smooth as possible.  In the next few days I'll be finalizing our git server setup and polishing up the user interface tool you all will be using to interact with the source control and build system.
* Support e-mail threading in notification e-mails (Till Maas)


The conversion will take a couple days, which means our normal short outage for branching will be a bit extended.  I wish there was another way, but converting over 9K cvs repos into git repos does take sometime.  I really feel that this move is worth the extended outage.
* Add X-Bodhi mail headers (Till Maas)


The tool you all will use to interact with git and the buildsystem is called "fedpkg".  It comes from the fedora-packager package.  There is a version of it available now in all active Fedora and EPEL releases, although it is built to work against our staging environment where we have been testing the setup for a while.  This setup is slightly different than the final version, but you can install it and poke around the help system to get a feel for what's going on.  Most of the make targets have made it over and are named the same; build, sources, srpm, etc...  Many of the targets can take arguments and options.  Where the make system used shell variables, fedpkg uses options and arguments.
* Gracefully handle private bugs (Cole Robinson)
Each target takes a --help argument that will show any available options.  Fedpkg does not yet have a man page, that may be coming soon.


We're also going to be working on wiki pages to document the new stuff and archive the old stuff.  We're going to need help on this too, so if you want to pitch in, by all means!
* Set the default request for new updates to 'testing' in the web form


As I mentioned above, this is an attempt.  We are trying this pretty early, which I wouldn't normally do.  However we have a good roll back plan.  We are going to keep the CVS server as is, although turned read-only during and after the dist-git rollout.  If something fails beyond reasonable repair with the dist-git attempt we will re-enable write access to the CVS server (after we branch it for Fedora 14). Otherwise we will keep it around, in some capacity, as a read-only reference point.
* 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.


I'm certain we will run into some bumps along the way, and some wrinkles to iron out.  I ask that you are patient with us as we work through these, and as we either get updates pushed out of fedpkg or make adjustments to the git repos on the git server.  This transition has been a long time coming, and I'm really happy to be the one to make it happen.  Keep in mind that this will be the first iteration of our transition, and it will operate mostly the same as dist-cvs did with a few improvements.  Later on we will start to explore more interesting advancements such as automatic patch management with exploded sources, linking to upstream source repositories, automatic %changelog generation from git changelogs, or things I haven't even thought about.  Most of all, we won't be using CVS any more and that feels really good to me.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


If you're curious about how the new system will work or have concerns, or want to help, you can reply to this email thread or find me on IRC as "Oxf13" (that's an o, not a zero).  If you run across bugs in fedpkg, you can file them in the fedora-packager hosted trac space <ref>https://fedorahosted.org/fedora-packager/</ref> or just find me on IRC as well.


Thanks again for your patience, both in waiting so long for us to make this move, and for bearing with us during the transition."
Full list of changes since 0.8.7
--------------------------------


<references/>
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


====Fedora 14 Feature Freeze is tomorrow (2010-07-27)==== 
Luke Macken (25):
[[User:Poelstra|John Poelstra]]<ref>John Poelstra</ref> on Mon Jul 26 20:59:07 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000641.html</ref>,"A friendly reminder that tomorrow, Tuesday, July 27, 2010, is Feature Freeze for Fedora 14.
      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'


Feature Freeze means that all accepted features for Fedora 14 must be *significantly* "feature complete", ready for testing, and have a current status.
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


<ref>https://fedoraproject.org/wiki/Feature_Freeze_Policy</ref>
Ralph Bean (19):
<ref>https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze</ref>
      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.


If you have a feature that will not be feature complete by tomorrow that is okay.  Simply change the wiki page category to Category:FeatureReadyForWrangler (edit text at the very bottom of the page) and include the reason and your plans in the commit comment.  I'll see that your feature is targeted for Fedora 15 instead."
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/>


====f14 boost-1.44.0 upgrade: pushed====  
====Build F-18 collection packages for all language translators====


Benjamin Kosnik<ref>Benjamin Kosnik(bkoz at redhat.com)</ref> on Tue Jul 27 17:19:25 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000642.html</ref>,"The boost maintainers have updated the boost package to the current release (1.44.0) in rawhide for F14. More info here:
* 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>


<ref>https://fedoraproject.org/wiki/Features/F14Boost144</ref>
"Hi Fedora package maintainers


Rebuilds for devel packages that require boost are mandatory, as SONAME was bumped. Help from package maintainers with rebuilding packages with
Please build and push your package with latest translation file (e.g.
boost dependencies is appreciated."
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.


<references/>
Thank you so much.


====Outage: Build System - 2010-07-28 07:15 UTC==== 
noriko
[[User:JesseKeating|Jesse Keating]]<ref>Jesse Keating</ref> on Wed Jul 28 07:05:27 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000643.html</ref>,"There will be an outage starting at 2010-07-28 07:15 UTC, which will last approximately 48 hours.
Fedora Localization Project"


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


date -d '2010-07-28 07:15 UTC'
====Fedora 18 Alpha to slip by another one week====


=====Reason for outage=====
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
dist-git migration and Fedora 14 branching
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>


=====Affected Services=====
"Today at Go/No-Go meeting it was decided to slip Fedora 18
Buildsystem - <ref>http://koji.fedoraproject.org/</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
CVS / Source Control
full log is at <ref>http://bit.ly/PC16PF</ref>.


=====Unaffected Services=====
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
All others
will be pushed out by one week.


=====Ticket Link=====
The next Go/No-Go meeting is on Thursday Sep 06, same place
N/A
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).


=====Contact Information=====
If you have an accepted blocker bug, please try to fix it
Jesse Keating <jkeating at redhat.com> or Oxf13 on IRC
as soon as possible to help us with Fedora 18 Alpha release!"


Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."
<references/>


<references/>


===Fedora User Announcements===
=== Fedora Events ===
The list<ref>http://lists.fedoraproject.org/pipermail/users/2010-July/thread.html</ref>,Fedora User Announcements, provides community assistance, encouragement, and advice for Fedora users.


<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 273: 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"