From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
 
(269 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===
====Wiki Freeze Reminder==== 
[[User:Jjmcd|John J. McDonough]]<ref>John J. McDonough</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002784.html</ref> on Thursday, April 8,2010 at 12:32:09 UTC, "'''In just over a week, on April 19, the wiki will freeze for Release Notes for Fedora 13'''.  If you have content you would like to see the the Release Notes go to:
<ref>https://fedoraproject.org/wiki/Documentation_Beats</ref>


and click on the most appropriate beat.  Add your content there.
====[Guidelines Change] Changes to the Packaging Guidelines==== 


'''Note that the content will be reviewed and edited so there is no need to
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
be concerned that your prose is exactly perfect. If you are pressed for
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>
time, a few words about what changed along with a link to more detail
would be fine. The Docs Project needs to know what you have provided
for F13 before it can write about it!'''"


<references/>
"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>
 
---
 
The review guidelines now reflect the use of sha256sum (instead of
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>
 
---
 
The PHP Packaging guidelines have been updated to include guidance about
when it is appropriate to have an explicit Requires on httpd & mod_php,
how to handle explicit Requires on PHP extensions, and how to handle a
Requires for a minimum PHP version.
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Apache_requirement</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Extensions_Requires</ref>
<ref>https://fedoraproject.org/wiki/Packaging:PHP#Requiring_a_Minimum_PHP_version</ref>
 
---
 
A new section on Macros has been added to the Packaging Guidelines,
covering Packaging of Additional RPM Macros.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>


====Students - You are invited to submit proposals for Fedora Summer Coding 2010==== 
---
[[User:Kwade|Karsten Wade]]<ref>Karsten Wade</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002785.html</ref> on Thursday, April 8,2010 at 20:29:00,"'''Students - You are invited to submit proposals for Fedora Summer Coding 2010'''". The announcement possessed, "
Start here –
<ref>https://fedoraproject.org/wiki/Summer_Coding_2010#You_are_a_student</ref>


But here is some more, in case you want to read it. (From <ref>http://iquaid.org/2010/04/08/students-you-are-invited-to-submit-proposals-for-fedora-summer-coding-2010/</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>


We are rapidly constructing this summer coding program.  We know what we are doing, but because of timing, we are building the infrastructure, process, and requirements as we go.  It’s like moving in to a house while the scaffolding is still outside.  The Fedora Project makes it easy to do stuff like this, since the plumbing and stuff are already in place.(Enough of that metaphor …)
---


Since mentors have another week, until 14 April, to finish the ideas page:
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>


<ref>http://fedoraproject.org/wiki/Summer_Coding_2010_ideas</ref>
---


The page is growing and changing until then. Check back often, put a watch on the page, and immediately begin communicating with the mentors of any ideas that you are interested in. The best place to talk with mentors is the discussion list:
The RHEL conditionalization has been removed from the Python3 example
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


<ref>http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss</ref>
---


If you can’t participate this year, such as the timing being off for your summer plans or you want more certainty, good luck to you for this summer.  Check back in; we intend to do this again (and again), and it is going be better after all this learning we’re doing:
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


<ref>http://iquaid.org/2009/02/28/failure-as-the-secret-of-success/</ref>
'''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.'''


If you celebrate summer at a different time of the year, such as if you are in the stunningly huge population of people in the Southern Hemisphere, do you think we should keep rolling this program to do a summer-for-the-south version?  Stay tuned, or help organize it:
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>"


<ref>https://fedoraproject.org/wiki/Summer_Coding_SIG#How_can_you_help.3F</ref>"
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>


<references/>
<references/>


====Fedora research survey: LAST CALL!====
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  
[[User:GregDeKoenigsberg|Greg DeKoenigsberg]]<ref>Greg DeKoenigsberg</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002786.html</ref> '''the last call of Fedora research survey''' on Monday, April 12,2010 at 16:21:16 UTC. He also mentioned, "As some of you may know, professors at the Fuqua School of Business at Duke University have been conducting a study of Fedora, and have put together an online survey based on interviews they conducted with several dozen folks from the community.
 
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
 
"Greetings! (...or perhaps I should say.... bonjour!)
 
I'd like to share a few reminders and announcements regarding the
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
 
If you are planning to attend FUDCon and need a travel subsidy to do so,
the ticketing system is now open for those requests.  Requests will be
accepted through August 15, 2012. Please note that funding requests
without a ticket will not be considered. Preference will be given to
attendees from the EMEA region who are actively contributing to Fedora,  
and have detailed their participation plans for FUDCon in their request.
 
To place a subsidy request, please follow these steps:
 
1: Pre-register at  
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Pre-registration</ref> - and
put an X in the $$$ column
2: Read about the funding request process and place a funding request
ticket in the FUDCon-planning ticket tracker here:
<ref>https://fedorahosted.org/fudcon-planning/wiki/FundingRequest</ref>
 
Additionally, a few notes regarding the hotel in Paris:
 
There are other events in Paris during this time period; most notably,  
our first day of FUDCon will be taking place at the Open World Forum
conference, on the day in which the public is encouraged to participate
in and learn about open source projects.  OWF had nearly 2000 attendees
last year.  Accordingly, rooms might be in short supply as we approach
FUDCon; please, book your hotel as soon as possible, not only for
affordability purposes, but also so that you have a bed to sleep in. :)
 
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
However, this rate will expire at the end of August, and any remaining
rooms in our block will expire.


We are now in the midst of our FINAL PUSH to get as many responses as we can.  This week is the last week for survey data. If you've been waiting around, wait no more: this is your last, best chance to help.  :)
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/>


You can access the survey here:
====Fedora Infrastructure announces status.fedoraproject.org==== 
<ref>http://www.projectassessment.org/fedora/</ref>


Their research goal is to focus more deeply on three primary themes that emerged from over 20 interviews they conducted with participants in the Fedora Project:
* 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>


* '''Values that are relevant to participants (e.g., to what extent is 'Open Source' a relevant value across the Fedora Project?)''',
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


* '''Activities that participants engage in to help sustain the community (e.g., to what extent is 'testing' a collaborative activity across the Fedora Project?)''', and
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


* '''Tools participants use for communication or workflow (e.g., to what extent is 'Planet' or 'Koji' used across the Fedora Project?)'''.
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  


The findings of this research will go a long way to helping us better understand what makes the Fedora community tick. I think it is a hallmark of our success as a community that academics are starting to study in detail the ins-and-outs of how our community works.  
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.


Please respond as soon as possible -- should take about 15 minutes of your
As with everything in Fedora Infrastructure, this application is open
time.  If you have any comments or concerns, please feel free to email me.
source. Source is available from:
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
and is released under a '''GPLv2+ license'''.  


Thanks again for taking the time to answer these 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. "


<references/>
<references/>


====Announcing the release of Fedora 13 Beta!!====
====Beats are open!====
[[User:Jkeating|Jesse Keating]]<ref>Jesse Keating</ref> announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-April/002787.html</ref> on Tuesday, April 13,2010 at 14:16:23 UTC, "'''The countdown is on: Fedora 13, "Goddard," is set to launch in mid-May. Fedora is the leading edge, free and open source operating system that continues to deliver innovative features to users worldwide, with a new release every six months'''.


But wait! What's that? You can't wait a whole month to try out the latest and greatest in Fedora's leading-edge technologies? You want to be the first to see what's new? '''Well, you're in luck. The Fedora 13 Beta release is available NOW'''. Hop on board and take a tour of the rocking new features.
* Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton]<ref>kevin at scrye.com</ref>
<ref>http://fedoraproject.org/get-prerelease?anF13b</ref>
* Posted Date: Tue Aug 28 15:35:59 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/docs/2012-August/014540.html</ref>


'''What is the Beta Release?'''
"The Release Notes beats for Fedora 18 are now open:
The beta release is the last important milestone of Fedora 13. Only critical bug fixes will be pushed as updates leading up to the general release of Fedora 13, scheduled to be released in the middle of May. We invite you to join us and participate in making Fedora 13 a solid release by downloading, testing, and providing your valuable feedback.
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


Of course, this is a beta release, some problems may still be lurking. A list of the problems we already know about is found at the Common F13
If you're looking for a way to dip your toes in the water, so to
bugs page:
speak, writing a beat is a great way to get started. If you're a
<ref>http://fedoraproject.org/wiki/Common_F13_bugs</ref>
regular, don't forget about the checkBeat program:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


'''If you find a bug that's not found on that page, be sure it gets fixed
As a reminder, the wiki drafts of beats are due on 12 September."
before release by reporting your discovery at <ref>https://bugzilla.redhat.com/</ref>. Thank you!'''


'''Features'''
<references/>


A universe of new features for end users:
=== 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.


* '''Automatic print driver installation'''. We're using RPM and PackageKit for automatic installation of printer drivers, so when you plug in a printer, Fedora will automatically offer to install drivers for it if needed.
'''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


* '''Desktop enhancements'''. The Shotwell photo manager, Deja-dup backup software, Pino Identi.ca/Twitter client, and Simple Scan scanning utility are all delivered by default to provide a enhanced desktop experience out of the box.
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


* '''NetworkManager improvements''' include better Mobile Broadband, Bluetooth, and new CLI abilities. NetworkManager is now a one-stop-shop for all of your networking needs in Fedora, be it dial-up, broadband, wifi, or even Bluetooth. Mobile broadband enhancements now show signal strength. Old-style dial-up networking (DUN) over Bluetooth has also been added. And now, you can even use NetworkManager from the command line in addition to the improved graphical user interface. Getting a connection when you need it has never been easier to figure out, whether you're at home, at work, at the local coffee shop, or riding your city's wi-fi enabled public transport.
<references/>


* '''Color management'''. Do you like your printouts to look the same as they do on screen - or your scanner output to look the same as what you just scanned? Color Management allows you to better set and control your colors for displays, printers, and scanners, through the gnome-color-manager package.
====New bodhi release in production====


* '''Enhanced iPod functionality'''. Newer Apple iPod, iPod Touch and iPhone models are supported by some of your favorite photo management software, and music library applications such as Rhythmbox. The devices are automatically attached using the libimobiledevice library, so you can work with your content more easily.
* 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>


* '''Experimental 3D graphics support extended to free Nouveau driver for NVidia cards'''. In this release we are one step closer to having 3D graphics supported on completely free and open source software (FOSS) drivers. Fedora 12 saw the enabling of a number of ATI cards; this time around, we've added a wide range of NVidia cards to our list of liberated video capabilities. You can install the mesa-dri-drivers-experimental package to try out the work in progress.
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>


* '''DisplayPort support improvements''' - Fedora 12 added initial support for the new DisplayPort display connector for Intel graphics chips. Support for Nvidia and ATI systems have now have added in this release.
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


* '''Experimental user management interface'''. The user account tool has been completely redesigned, and the accountsdialog and accountsservice test packages are available to make it easy to configure personal information, make a personal profile picture or icon, generate a strong passphrase, and set up login options for your Fedora system. Try out the work in progress.
Major changes in bodhi 0.9.2
---------------------------------


For developers there are all sorts of additional goodies:
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


* '''SystemTap static probes'''. SystemTap now has expanded capabilities to monitor higher-level language runtimes like Java, Python, and Tcl, and also user space applications, starting with PostgreSQL. In the future, Fedora will add support for even more user space applications, greatly increasing the scope and power of monitoring for application developers.
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines


* '''Easier Python debugging'''. We've added new support that allows developers working with mixed libraries (Python and C/C++) in Fedora to get more complete information when debugging with gdb, making Fedora an exceptional platform for powerful, rapid application development.
* The submitter of an update can no longer effect the karma (Till Maas)


* '''Parallel-installable Python 3 stack'''. The parallel-installable Python 3 stack will help programmers write and test code for use in both Python 2.6 and Python 3 environments, so you can future-proof your applications now using Fedora.
* Fix duplicate status change email notifications. (Till Maas)


* '''NetBeans Java EE 6 support'''. The NetBeans 6.8 integrated development environment is the first IDE to offer complete support for the entire Java EE 6 specification.
* Mention age of updates in testing digest mails (Till Maas)


And don't think we forgot the '''system administrators''':
* Support e-mail threading in notification e-mails (Till Maas)


* '''boot.fedoraproject.org (BFO)'''. BFO allows users to download a single, tiny image (could fit on a floppy) and install current and future versions of Fedora without having to download additional images.
* Add X-Bodhi mail headers (Till Maas)


* '''System Security Services Daemon (SSSD)'''. SSSD provides expanded features for logging into managed domains, including caching for offline authentication. How does this help the sysadmin? This means, for example, users on laptops can still login when disconnected from the company's managed network. The authentication configuration tool in Fedora has already been updated to support SSSD, and work is underway to make it even more attractive and functional.
* Gracefully handle private bugs (Cole Robinson)


* '''Pioneering NFS features'''. Fedora offers the latest version 4 of the NFS protocol for better performance, and, in conjunction with recent kernel modifications, includes IPv6 support for NFS as well.
* Set the default request for new updates to 'testing' in the web form


* '''Zarafa Groupware - Alternative to Microsoft Exchange'''. Zarafa now makes available a complete Open Source groupware suite that can be used as a drop-in Exchange replacement for Web-based mail, calendaring, collaboration, and tasks. Features include IMAP/POP and iCal/CalDAV capabilities, native mobile phone support, the ability to integrate with existing Linux mail servers, a full set of programming interfaces, and a comfortable look and feel using modern Ajax technologies.  
* 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.


* '''Btrfs snapshots integration'''. Btrfs is capable of creating lightweight filesystem snapshots that can be mounted (and booted into) selectively. The created snapshots are copy-on-write snapshots, so there is no file duplication overhead involved for files that do not change between snapshots. It allows developers to feel comfortable experimenting with new software without fear of an unusable install -- automated snapshots allow them to easily revert to the previous day's filesystem.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


* '''Dogtag Certificate System''' It is an enterprise-class open source Certificate Authority (CA) supporting all aspects of certificate lifecycle management including key archival, OCSP and smartcard management. Brought into the fold as part of the Red Hat acquisition of Netscape technologies, this certificate server is fully free and open source and now included in Fedora.


And that's only the beginning. '''A more complete list and details of all
Full list of changes since 0.8.7
the new features onboard Fedora 13 is available here:
--------------------------------
<ref>http://fedoraproject.org/wiki/Releases/13/FeatureList</ref>'''


We have nightly composes of alternate spins available here:
Kalpa Welivitigoda (1):
      fixed input box alignment issue in login box #579


<ref>http://alt.fedoraproject.org/pub/alt/nightly-composes/</ref>
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


'''Contributing'''
Ralph Bean (19):
   
      Sending messages with fedmsg.
For more information including common and known bugs, tips on how to report bugs, and the official release schedule, please refer to the release notes:
      No longer using fedmsg schema/validation.
<ref>http://docs.fedoraproject.org</ref>
      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.


There are many ways to contribute beyond bug reporting. You can help translate software and content, test and give feedback on software updates, write and edit documentation, help with all sorts of promotional activities, and package free software for use by millions of Fedora users worldwide. '''To get started, visit
Till Maas (8):
<ref>http://join.fedoraproject.org</ref> today!'''
      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/>


===Fedora Development News===
====Build F-18 collection packages for all language translators====
====Summer Coding 2010 ideas due 9 April==== 
 
[[User:Kwade|Karsten Wade]]<ref>Karsten Wade</ref> announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-April/000596.html</ref> on Tuesday, April 6,2010 at 15:20:50 UTC, "While we finish the Summer Coding 2010 page (<ref>http://bit.ly/FSC-2010</ref>),
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
it is past time for you all to let us know the problems you would like to see solved by summer coding/internship students.  By Friday 09 April.
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>
 
"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.


Idea page is here:
Thank you so much.
<ref>https://fedoraproject.org/wiki/Category:Summer_Coding_2010_ideas</ref>


How-to fill out an ideas page is here:
noriko
<ref>https://fedoraproject.org/wiki/How_to_create_an_idea_page_for_Summer_Coding</ref>
Fedora Localization Project"


Let’s get this filled with serious ideas you are willing to mentor for or help find the mentor.
<references/>


Join the discussion list and be prepared to talk about your ideas or proposals.
====Fedora 18 Alpha to slip by another one week====


<ref>http://lists.fedoraproject.org/mailman/listinfo/summer-coding-discuss</ref>
* 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>


If you were already a mentor and want to help with mentoring, such as proposal reviews, let us know and join the mentors list.
"Today at Go/No-Go meeting it was decided to slip Fedora 18
<ref>http://lists.fedoraproject.org/mailman/listinfo/summer-coding-mentors</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
full log is at <ref>http://bit.ly/PC16PF</ref>.


Tracking these ideas is a PITA and in fact the lack of an ideas page lead to us not getting in the Google Summer of Code this year.  This is all part of a larger issue around tracking smaller ideas for beginners and students, but for now this will have to do.
As a result, ALL MAJOR MILESTONES, and their dependent tasks,  
will be pushed out by one week.


Anyone want to hack on OpenHatch.org, please help.  We’re hoping some of the functionality we are handling manually may be included in upcoming versions of OpenHatch.  If that direction gets us fruit, we may use OpenHatch as an ongoing way to expose projects to students and other new contributors.
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).


(This email derived from my post at <ref>http://bit.ly/bofYla</ref>)
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/>


====Ideas for Summer Coding deadline moved to 14 April====
[[User:Kwade|Karsten Wade]]<ref>Karsten Wade</ref> announced <ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-April/000597.html</ref> on Wednesday, April 7,2010 at 20:06:41 UTC, "In today's SIG meeting we finalized the Summer Coding 2010 schedule, and that included adding more time for ideas to be listed for students.
The new deadline is next Wed. 14 April. We are inviting students to begin working on proposals starting today, with those due on 21 April.


<ref>https://fedoraproject.org/wiki/Summer_Coding_2010_schedule</ref>
=== Fedora Events ===
<ref>https://fedoraproject.org/wiki/Summer_Coding_2010_ideas</ref>
"


<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 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 (March 2010 to May 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_Q1_.28March_2010_-_May_2010.29</ref>
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY10_Q4_.28March_2010_-_May_2010.29</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_2</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q1_.28March_2010_-_May_2010.29_3</ref>


<references/>
<references/>
Line 213: Line 366:


====Additional information====
====Additional information====
* '''[[Reimbursements]] -- reimbursement guidelines.'''
* [[Reimbursements]] -- reimbursement guidelines.
* '''[[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).'''
* [[Ambassadors/SteeringCommittee/Budget| Budget]] -- budget for the current quarter (as distributed by FAMSCo).
* '''[[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.'''
* [[Sponsoring event attendees | Sponsorship]] -- how decisions are made to subsidize travel by community members.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[FedoraEvents/Organization| Organization]] -- event organization, budget information, and regional responsibility.
* [[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"