From Fedora Project Wiki

< FWN‎ | Beats
No edit summary
 
(71 intermediate revisions by 2 users not shown)
Line 2: Line 2:
==Announcements==
==Announcements==


In this section, we cover announcements from the Fedora Project, including general announcements<ref>
Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements<ref>http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Fedora Events<ref>http://fedoraproject.org/wiki/Events</ref>.
http://lists.fedoraproject.org/pipermail/announce/</ref>, development announcements<ref>http://lists.fedoraproject.org/pipermail/devel-announce/</ref> and Events<ref>http://fedoraproject.org/wiki/Events</ref>.


Contributing Writer: [[User:Pcalarco|Pascal Calarco]]
Contributing Writer: [[User:rashadul|Rashadul Islam]]


<references/>
<references/>


=== Fedora Announcements ===
===Breaking News of the Week and Month===


====Change in requirements for Board, FESCo, and FAmSCo candidates====
====[Guidelines Change] Changes to the Packaging Guidelines====  


Tom Callaway<ref>Tom Callaway tcallawa at redhat.com</ref>, from Fedora Legal, on Mon May 16 14:53:49 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-May/002959.html</ref>,
* Contributor: [[User:Spot|Tom Callaway]<ref>Tom Callaway tcallawa at redhat.com</ref>
* Posted Date: Wed Aug 1 19:28:57 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003098.html</ref>


"There has been an amendment to the requirements for candidates to
"A new section has been added to the SysV Initscripts section, discussing
elected (and appointed) roles in Fedora's Community, including (but not
the proper use of subsys locking. Even though Fedora packages should no
limited to) the Fedora Board, Fedora Engineering Steering Committee, and
longer be using SysV Initscripts as a primary service mechanism, Red Hat
the Fedora Ambassadors Steering Committee.
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>


Specifically, candidates must not be a citizen of an export-restricted
---
country (see<ref>https://fedoraproject.org/wiki/Legal/Export#Embargoed_Destinations|Legal/Export#Embargoed_Destinations</ref>
for the list of export restricted countries).


This requirement is applicable immediately, and will apply to candidates
The review guidelines now reflect the use of sha256sum (instead of
for this upcoming election as well.
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>


Unfortunately, the laws in the United States which Fedora and Red Hat
---
are subject to place very tight restrictions on the involvement of
citizens of certain countries. Fedora has made its position on this
issue known here:


<ref>https://fedoraproject.org/wiki/Embargoed_nations</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>


Thank you for your understanding"
---


<references/>  
A new section on Macros has been added to the Packaging Guidelines,
covering Packaging of Additional RPM Macros.
<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#Packaging_of_Additional_RPM_Macros</ref>


====IMPORTANT - Fedora Project Contributor Agreement Signing Window Is Open====
---


Tom Callaway<ref>Tom Callaway tcallawa at redhat.com</ref> on Tue May 17 20:05:56 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/announce/2011-May/002960.html</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>


"Please take a moment and read this brief email, as it is important.
---


Fedora is in the process of retiring our old "Individual Contributor
A short section on the Group tag in Fedora packages has been added.
License Agreement" (also known as the ICLA or CLA) and replacing it with
All current versions of Fedora (and their respective RPM versions) treat
the new Fedora Project Contributor Agreement (FPCA).
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>


All Fedora contributors with accounts in the Fedora Account System
---
(<ref>https://admin.fedoraproject.org/accounts</ref>) who have agreed to the old
CLA *MUST* agree to the new FPCA by June 17, 2011 to continue
contributing to Fedora.


Here is how you do this:
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>


1) Login to the Fedora Account System:
---
<ref>https://admin.fedoraproject.org/accounts</ref>


2) Once logged in, click on the "My Account" link in the blue box on the
These guidelines (and changes) were approved by the Fedora Packaging
left side of the window.
Committee (FPC).


3) On the page that loads, you will see a section labeled "Account
'''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.'''
Details". Look for the line that says "Contributor Agreement". On that
line, you should see a new section that says:


"New CLA Not Signed - We need contributors to sign the new Contributor
As a reminder: The Fedora Packaging Guidelines are living documents! If
Agreement(Complete it now!)"
you find something missing, incorrect, or in need of revision, you can
 
suggest a draft change. The procedure for this is documented here:
Click on "Complete it now!" and follow the prompts.
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"
 
*****
 
It is important that Fedora Account holders who have signed the old
Fedora CLA sign the new FPCA. We have allotted a window of one month for
Fedora contributors to agree to the FPCA. This means that after June 17,
2011, any Fedora Contributors who have not agreed to the FPCA will have
their "cla_done" flag set to False. This also means that any groups that
they are in which are dependent upon "cla_done", such as "packager",
"ambassador", and Fedora People access will be removed.
 
There are a few accounts which are exempt from this, specifically,
accounts which are members of the "cla_dell", "cla_intel", and
"cla_redhat" groups. If you do not know what these groups are, you are
probably not in them. :) Accounts in these groups will not see the "New
CLA Not Signed" line on their "My Account" page, and do not need to take
any action at this time.
 
Please take a minute and login to FAS to agree to the terms of the FPCA,
to avoid loss of access.
 
More information about the FPCA, including the final FPCA text, can be
found here:
<ref>https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement</ref>


If you have any additional questions about the FPCA or the re-signing
Enclosure: Here is one late change to the Fedora Packaging Guidelines:<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003100.html</ref>
process, please feel free to email me directly at legal at fedoraproject.org."
<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</ref>
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>


<references/>
<references/>


=== Fedora Development News ===
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  
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.


'''Acceptable Types of Announcements'''
* Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron]<ref>rbergero at redhat.com</ref>
* Policy or process changes that affect developers.
* Posted Date: Fri Aug 3 17:00:53 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003099.html</ref>
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders


'''Unacceptable Types of Announcements'''
"Greetings! (...or perhaps I should say.... bonjour!)
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


<references/>
I'd like to share a few reminders and announcements regarding the
 
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
====Outage: pkgs.fedoraproject.org - 2011-05-10 17:00 UTC==== 
Kevin Fenzi<ref>Kevin Fenzi kevin at scrye.com</ref> on Fri May 6 17:20:00 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000788.html<ref>,


"There will be an outage starting at 2011-05-10 17:00 UTC, which will last
If you are planning to attend FUDCon and need a travel subsidy to do so,
approximately 1 hour."
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.


The details of the report are available at http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000788.html
To place a subsidy request, please follow these steps:


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


====Outage: fedorapeople.org moving - 2011-05-09 15:00 UTC==== 
Additionally, a few notes regarding the hotel in Paris:
Kevin Fenzi<ref>Kevin Fenzi kevin at scrye.com</ref> on Fri May 6 19:50:47 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000789.html</ref>,


"There will be an outage starting at 2011-05-09 15:00 UTC, which will last
There are other events in Paris during this time period; most notably,
approximately 1hour."
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. :)


The details of the report are available at http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000789.html 
We currently have a rate of EUR81 per night at the ibis Paris La Vilette
Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. 
However, this rate will expire at the end of August, and any remaining
rooms in our block will expire.


For instructions on booking your hotel, please read the Lodging/Hotel
section of the FUDCon: Paris wiki:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>
<references/>


====Fedora 15 Final Change Deadline, and Outstanding Blocker Bugs====   
====Fedora Infrastructure announces status.fedoraproject.org====   
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Tue May 10 11:34:42 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000790.html</ref>,


"This is your friendly reminder that we have reached the Final Change
* Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ]<ref>kevin at scrye.com</ref>
Deadline for Fedora 15.
* Posted Date: Thu Aug 30 20:31:24 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/announce/2012-August/003101.html</ref>


<ref>https://fedoraproject.org/wiki/Change_deadlines</ref>
"I'm happy to announce the general availability of our
status.fedoraproject.org site.


"After the change deadlines for the Final release no more updates are
This site provides an easy way for Fedora contributors and users to
made to the branched development repository (e.g. /pub/fedora/linux/development/15).
check on the status of services provided by Fedora Infrastructure.


The only exceptions are accepted blocker and "nice to have" bugs:
The site auto reloads every minute, and also provides a rss feed at
<ref>https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process</ref>
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  
<ref>https://fedoraproject.org/wiki/QA:SOP_nth_bug_process</ref>


All updates after this time are considered zero day updates of the
If you run into a problem or issue that is not reflected at
release, and are pushed to the updates repository which is available on
status.fedoraproject.org, please do report it to us in #fedora-admin on
the public availability date. For example, the repository for Fedora 15
irc.freenode.net or via ticket at
is /pub/fedora/linux/updates/15."
<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.


The next step in the process is to create a final release candidate (RC)
As with everything in Fedora Infrastructure, this application is open
to pass on to QA for testing as soon as possible. However, we have a
source. Source is available from:
handful of bugs left that are blocking the creation of the RC. Delays
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
in resolving the bugs listed below will prevent the creation of the RC,
and is released under a '''GPLv2+ license'''.  
and CAN CAUSE A SLIP IN THE SCHEDULE.


<ref>https://bugzilla.redhat.com/show_bug.cgi?id=697834</ref>
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
697834 :: NEW :: gnome-menus :: rstrode
issues with outages in our infrastructure affecting status reporting. "
Other menu appears in default installation (any .desktop entry
with Category=Settings ends up here (even if there's also Category=System))
 
<ref>https://bugzilla.redhat.com/show_bug.cgi?id=693809</ref>
693809 :: ASSIGNED :: imsettings :: tagoh
Error message about missing input methods should be removed"


<references/>
<references/>


====REMINDER: Outage: pkgs.fedoraproject.org - 2011-05-10 17:00 UTC====  
====Beats are open!====
Kevin Fenzi<ref>Kevin Fenzi kevin at scrye.com</ref> on Tue May 10 16:47:10 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000791.html</ref>,


"A reminder that this outage will begin in about 15minutes.  
* 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>


Outage: pkgs.fedoraproject.org - 2011-05-10 17:00 UTC
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


There will be an outage starting at 2011-05-10 17:00 UTC, which will last
If you're looking for a way to dip your toes in the water, so to
approximately 1 hour."
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>


The details of the report can be found at http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000791.html
As a reminder, the wiki drafts of beats are due on 12 September."


'''On the separate outage notification, Kevin Fenzi announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000792.html</ref>'''
<references/>


"Sorry for not sending this sooner.  
=== 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 outage on pkgs.fedoraproject.org should be complete.  
'''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 report any issues or problems found. "
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


<references/>
<references/>


====Fedora 15 FINAL Go/No-Go Meeting, TUESDAY, May 17, 2011 @ 21:00 UTC (17:00 EDT/14:00 PDT)====
====New bodhi release in production====
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Mon May 16 15:51:41 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000794.html</ref>,
 
"Join us on irc.freenode.net in #fedora-meeting for this important meeting,
Tuesday, May 17, 2011, at 21:00 UTC (17:00 US-Eastern, 14:00 US-Pacific).
 
"Before each public release Development, QA, and Release Engineering
meet to determine if the release criteria are met for a particular
release. This meeting is called the: Go/No-Go Meeting."
 
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
 
For more details about this meeting see:
<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
 
And while you wait, keep an eye on the current F15 final blockers, and
help fill out the test result matrices:
 
<ref>https://fedoraproject.org/wiki/Current_Release_Blockers</ref>
<ref>http://fedoraproject.org/wiki/Category:Fedora_15_Final_RC_Test_Results</ref>


See you there!
* 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>


(And my apologies for sending this out in a less-than-timely manner -
"A new release of Bodhi has just been deployed to production.
I had it stuck in my head that this meeting was Wednesday.)"
<ref>https://admin.fedoraproject.org/updates</ref>


<references/>
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


====Fedora 15 Final Release is declared GOLD!====
Major changes in bodhi 0.9.2
Robyn Bergeron<ref>Robyn Bergeron rbergero at redhat.com</ref> on Tue May 17 22:25:59 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000796.html</ref>,
---------------------------------


"At the Fedora 15 Final Go/No-Go meeting today, '''the Fedora 15 Final
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
Release was declared GOLD and ready for release on May 24, 2011'''.


Please note that the Fedora 15 Release Wide Readiness Meeting will take
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines
place on Thursday at 19:00 UTC (3 PM Eastern/ 12 PM Pacific) on
irc.freenode.net in #fedora-meeting.


<ref>https://fedoraproject.org/wiki/Release_Readiness_Meetings</ref>
* The submitter of an update can no longer effect the karma (Till Maas)


Thanks to everyone for doing your part to get Fedora 15 out the door! :)
* Fix duplicate status change email notifications. (Till Maas)


#fedora-meeting: Fedora 15 Go or No go Meeting<ref>http://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
* Mention age of updates in testing digest mails (Till Maas)


Meeting started by rbergeron at 21:00:33 UTC. The full logs are
* Support e-mail threading in notification e-mails (Till Maas)
available at<ref>http://meetbot.fedoraproject.org/fedora-meeting/2011-05-17/fedora_15_go_or_no_go_meeting.2011-05-17-21.00.log.html</ref>


=====Meeting summary=====
* Add X-Bodhi mail headers (Till Maas)
* Who's here?  (rbergeron, 21:00:54)


* Why are we here?  (rbergeron, 21:02:11)
* Gracefully handle private bugs (Cole Robinson)
  * The purpose of this meeting is to decide whether the final release
    criteria have been met  (rbergeron, 21:02:30)
  * LINK:https://fedoraproject.org/wiki/Fedora_15_Final_Release_Criteria
rbergeron, 21:02:50)


* To Go, or Not to Go? That is the question.  (rbergeron, 21:03:51)
* Set the default request for new updates to 'testing' in the web form
  * LINK: https://fedoraproject.org/wiki/Current_Release_Blockers
    (rbergeron, 21:04:16)
  * the four proposed blockers are not blockers, per yesterday's QA
    meeting.  (rbergeron, 21:07:04)
  * AGREED: We are technically blocker free.  (rbergeron, 21:09:57)


* Test Matrices  (rbergeron, 21:10:13)
* 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.
  * LINK:https://fedoraproject.org/wiki/Test_Results:Fedora_15_Final_RC3_Desktop
rbergeron, 21:10:48)
  * LINK:https://fedoraproject.org/wiki/Test_Results:Fedora_15_Final_RC3_Install
rbergeron, 21:11:10)
  * We will be composing a sugar live image late with some
    sugar-specific fixes pulled in.  (rbergeron, 21:12:49)
  * Only desktop and KDE can block the release.  (rbergeron, 21:13:03)
  * AGREED: Test matrices are acceptable for a go. (rbergeron,
    21:13:45)


* Rel-eng  (rbergeron, 21:14:11)
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


* FESCo/Devel  (rbergeron, 21:15:14)


* GOLD?  (rbergeron, 21:16:31)
Full list of changes since 0.8.7
  * AGREED: Fedora 15 is declared gold. shipit!  (rbergeron, 21:18:09)
--------------------------------


* open floor  (rbergeron, 21:18:48)
Kalpa Welivitigoda (1):
  * Thanks to the systemd and gnome/desktop guys as both groups did a
      fixed input box alignment issue in login box #579
    lot of work to get those large features working well.  (rbergeron,
    21:19:30)
  * and Thanks! to everyone else as well!  (rbergeron, 21:19:36)
  * ACTION: rbergeron to send out GOLD email to the lists  (rbergeron,
    21:19:58)
  * Please note there is a readiness meeting on Thursday, email has been
    sent to logistics list as well as attendees needed to be present.
    (rbergeron, 21:20:21)


Meeting ended at 21:22:46 UTC.
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'


=====Action Items=====
Mathieu Bridon (6):
* rbergeron to send out GOLD email to the lists
      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


=====Action Items, by person=====
Ralph Bean (19):
* rbergeron
      Sending messages with fedmsg.
rbergeron to send out GOLD email to the lists
      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.


=====People Present (lines said)=====
Till Maas (8):
* rbergeron (58)
      Add X-Bodhi mail headers
* adamw (29)
      Support e-mail threading in notification e-mails
* dgilmore (8)
      Mention age of updates in testing digest mails
* cwickert (6)
      Use format string instead of string concatenation
* Viking-Ice_ (6)
      Import exceptions from sqlite3
* brunowolff (5)
      Remove files used by mercurial
* jsmith (4)
      model.py: Change karma from Submitter to 0
* zodbot (3)
      Fix notification on automatic status change"
* stickster (3)
* nirik99 (3)
* spot (3)
* fenrus02 (2)
* jlaska (2)
* red_alert (1)
* therefore (1)
* athmane (1)"


<references/>
<references/>


====[Guidelines Change] Changes to the Packaging Guidelines====
====Build F-18 collection packages for all language translators====
Tom Callaway<ref>Tom Callaway tcallawa at redhat.com</ref> on Wed May 18 17:49:05 UTC 2011 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2011-May/000797.html</ref>,


"Here are the latest changes to the Fedora Packaging Guidelines:
* 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>


A section has been added to the SysVInitScript guidelines covering the
"Hi Fedora package maintainers
optional situation where a package that uses systemd unit files as the
default also includes sysv initscripts in a subpackage:


<ref>https://fedoraproject.org/wiki/Packaging:SysVInitScript#Initscripts_in_addition_to_systemd_unit_files</ref>
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.


The GIO scriptlets have been changed to not conditionalize the %post
Thank you so much.
invocation. This works around a multilib issue.


<ref>https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#GIO_modules</ref>
noriko
Fedora Localization Project"


The guideline that prohibits Fedora packages from using /srv has been
<references/>
updated to better represent what the FHS has to say about /srv and to
clarify the expectations for Fedora packages which may be configured to
use /srv.


<ref>https://fedoraproject.org/wiki/Packaging:Guidelines#No_Files_or_Directories_under_.2Fsrv</ref>
====Fedora 18 Alpha to slip by another one week====


It was brought to the FPC's attention that while the new Guidelines
* Contributor: [[User:JaroslavReznik|Jaroslav Reznik]<ref>jreznik at redhat.com</ref>
covering MinGW packaging were technically correct, Fedora 16 did not yet
* Posted Date: Thu Aug 30 23:26:35 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000970.html</ref>
contain the necessary toolchain to support the new Guidelines, nor was
it clear that it would arrive in rawhide anytime soon.


Accordingly, the "old" MinGW guidelines were put back in place at:
"Today at Go/No-Go meeting it was decided to slip Fedora 18
<ref>https://fedoraproject.org/wiki/Packaging:MinGW</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>.


The "new" MinGW guidelines remain approved, but are not active and
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
packagers should not use them at this time. If/when the necessary
will be pushed out by one week.
toolchain components are packaged in Fedora, these guidelines will be
re-enabled.


In addition, the current MinGW guidelines were improved slightly to
The next Go/No-Go meeting is on Thursday Sep 06, same place
support the "new" SRPM naming standard. This is intended to prevent new
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
MinGW packages from having to be re-reviewed when the "new" MinGW
#fedora-meeting).
guidelines take effect.


These guidelines (and changes) were approved by the Fedora Packaging
If you have an accepted blocker bug, please try to fix it
Committee (FPC).
as soon as possible to help us with Fedora 18 Alpha release!"


Many thanks to Kalev Lember, Matthew Miller, Michael Schwendt, and all
<references/>
of the members of the FPC, for assisting in drafting, refining, and
passing these guidelines.


As a reminder: The Fedora Packaging Guidelines are living documents! If
you find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"


<references/>
=== Fedora Events ===


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


The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning.
====Upcoming Events (September 2012 - November 2012)====
Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding.  
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
* '''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 - May 2011)====
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#FY12_Q1_.28March_2011_-_May_2011.29</ref>
* Central & South America (LATAM): <ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4</ref>


<references/>
<references/>
Line 398: 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"