From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
 
(159 intermediate revisions by 2 users not shown)
Line 2: Line 2:
==Announcements==
==Announcements==


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


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


<references/>
<references/>


===Fedora Announcement News===
===Breaking News of the Week and Month===
The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at<ref>http://lists.fedoraproject.org/pipermail/announce/2010-August/thread.html</ref>


<references/>
====[Guidelines Change] Changes to the Packaging Guidelines==== 


====Looking for a few great contributors to help out with Fedora Elections!====
* 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>


Robyn Bergeron put out a call<ref>http://lists.fedoraproject.org/pipermail/announce/2010-October/002873.html</ref> for volunteers to assist with the upcoming Fedora elections:
"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>


"Are you a Fedora community member or even a free software user who’d like to get more involved but aren’t sure where to start?
---


The Fedora Project is gearing up for our twice-annual elections process, for an election period in late November. During this election, we’ll be voting on positions in the following groups:
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>


* Fedora Board<ref>http://fedoraproject.org/wiki/Board</ref>
---


* Fedora Engineering Steering Committee (FESCo)<ref>http://www.fedoraproject.org/wiki/FESCO</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>


* Fedora Ambassadors Steering Committee (FAmSCo)<ref>http://fedoraproject.org/wiki/FAMSCo</ref>
---


Helping out with this elections process is a great opportunity to get started as a free software contributor, especially if you’re unable or prefer not to write code.
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>


We have a handful positions we need help with. We’ve outlined them below. If any of these sound like things you’d like to help us with, please send an email to the Fedora Board (advisory-board AT lists.fedoraproject.org).
---


Fedora Election Questionnaire Coordinator
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>


The Fedora Election Questionnaire Coordinator will make sure members of the Fedora Community are able to ask questions of the candidates, and will facilitate sending the questions to the candidates and compiling them into a wiki page that will be distributing during the election period.
---


Specifically, here’s what you’ll need to do as questionnaire coordinator:
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>


* Create a wiki page to list the candidate questions.
---


* Use the following link to create the page<ref>http://fedoraproject.org/wiki/F15_elections_questionnaire</ref>
The RHEL conditionalization has been removed from the Python3 example
spec file, as it is no longer valid.
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>


* REFERENCE: The questionnaire from the last election is here<ref>http://fedoraproject.org/wiki/F14_elections_questionnaire</ref> You may want to look at it for ideas.
---


* Send an message out to the Fedora community to collect questions for the candidates, allowing community members to email their questions to you directly or optionally adding them to a wiki page. The message should be sent to the following:
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).


* Fedora Advisory Board Mailing List (advisory-board AT lists.fedoraproject.org)
'''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.'''


* Community support for Fedora users Mailing List (users AT lists.fedoraproject.org)
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>"


* Fedora Announce List Mailing List  (announce AT lists.fedoraproject.org)
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>


* Development discussions related to Fedora Mailing List (devel AT lists.fedoraproject.org)
<references/>


* Planet Fedora (http://planet.fedoraproject.org) – if your blog is not on Planet Fedora, contact Máirín Duffy (duffy AT fedoraproject.org) to post your message to the Planet for you.
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders==== 


* On November 1, gather up all the questions that you collected from the Community, and post them all to the wiki page you created<ref>http://fedoraproject.org/wiki/F15_elections_questionnaire</ref>. Make sure the page is neat & orderly.
* 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>


* On November 1, send the questionnaire page to all candidates and ask them to send their answers to you by November 8.
"Greetings! (...or perhaps I should say.... bonjour!)


* For any candidates you haven’t heard from on November 7th, send them a reminder email.
I'd like to share a few reminders and announcements regarding the
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.


* Copy the candidates’ answers into the wiki page and advertise the answers to the same venues listed above (the mailing lists and Planet Fedora.
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.


* Helpful Tips:
To place a subsidy request, please follow these steps:


* Consider using your best judgement and selecting 6-8 good questions from the pool for the candidates. 20 questions is probably too much. If some are similar, feel free to merge and restate them.
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>


That’s it. Not too tough, to ask. right?
Additionally, a few notes regarding the hotel in Paris:


Fedora Election Town Hall Coordinator
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. :)


The Fedora Election Town Hall Coordinator will schedule IRC town hall sessions, one for each of the following groups:
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.


* Fedora Board
For instructions on booking your hotel, please read the Lodging/Hotel
* Fedora Engineering Steering Committee (FESCo)
section of the FUDCon: Paris wiki:
* Fedora Ambassadors’ Steering Committee (FAmSCo)
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>


Specifically, here’s what you’ll need to do as town hall coordinator:
====Fedora Infrastructure announces status.fedoraproject.org==== 


* Email all of the Fedora Board candidates between Nov. 1 and Nov. 3 and ask them to provide some 1-hour blocks of time they might be available to participate in an IRC town hall session, between November 13 and November 19th. You may wish to use a tool like whenasgood.net to organize this. Ask them to respond by Nov. 10.
* 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>


* Do the same as above for the Fedora Engineering Steering Committee (FESCo) candidates.
"I'm happy to announce the general availability of our
status.fedoraproject.org site.  


* Do the same as above for the Fedora Ambassadors’ Steering Committee (FAmSCo) candidates.
This site provides an easy way for Fedora contributors and users to
check on the status of services provided by Fedora Infrastructure.


* Select who the Town Hall moderators were be (see below for that job description).
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.  


* On November 10, determine the best date and time for each of the three town halls, and advertise this time & date and the irc channel (probably #fedora-meeting and #fedora-meeting-questions on irc.freenode.net) in the following venues:
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.


* Fedora Advisory Board Mailing List (advisory-board AT lists.fedoraproject.org)
As with everything in Fedora Infrastructure, this application is open
source. Source is available from:
<ref>http://git.fedorahosted.org/git/fedora-status.git</ref>
and is released under a '''GPLv2+ license'''.  


* Community support for Fedora users Mailing List (users AT lists.fedoraproject.org)
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. "


* Fedora Announce List Mailing List (announce AT lists.fedoraproject.org)
<references/>


* Development discussions related to Fedora Mailing List (devel AT lists.fedoraproject.org)
====Beats are open!====


* Planet Fedora (http://planet.fedoraproject.org) – if your blog is not on Planet Fedora, contact Máirín Duffy (duffy AT fedoraproject.org) to post your message to the Planet for you.
* 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>


* Helpful tips:
"The Release Notes beats for Fedora 18 are now open:
<ref>https://fedoraproject.org/wiki/Category:Documentation_beats</ref>


* When selecting people for town hall coordinators – remember that things like good IRC skills, even-temperedness, knowledge in the area of the town hall they are moderating, are very helpful.
If you're looking for a way to dip your toes in the water, so to
speak, writing a beat is a great way to get started. If you're a
regular, don't forget about the checkBeat program:
<ref>http://lists.fedoraproject.org/pipermail/docs/2012-March/014127.html</ref>


That’s it. Not too tough, right?
As a reminder, the wiki drafts of beats are due on 12 September."


Fedora Election Town Hall Moderator (3 needed!)
<references/>


The Fedora Election Town Hall Moderators will each run a 1-hour long IRC town hall sessions, one for each of the 3 groups being elected. This task requires some skill with IRC. This is an especially good position for someone who does not have a lot of time to devote as it only takes a little over an hour to do.
=== 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 date and time of each of these sessions will be published by the Fedora Election Town Hall Coordinator on November 10.
'''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


Specifically, here’s what you’ll need to do as town hall moderator:
'''Unacceptable Types of Announcements'''
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above


* Show up at least 5 minutes early to the town hall, make sure the IRC channel exists.
<references/>


* Start the meeting using the meeting bot command ‘#startmeeting’
====New bodhi release in production====


* Learn the IRC nicks of the candidates for your town hall. You can look them up on Fedora Community<ref>http://admin.fedoraproject.org/community</ref> or you can ask via email.
* 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>


* During the town hall, allow only candidates to have voice in #fedora-meeting.
"A new release of Bodhi has just been deployed to production.
<ref>https://admin.fedoraproject.org/updates</ref>


* During the town hall, take questions from Fedora Community members in #fedora-meeting-questions, and maintain a question queue. Ask the questions in order in #fedora-meeting, giving each candidate a chance to provide an answer to the question.
Bugs and enhancement requests can be filed here:
<ref>http://bodhi.fedorahosted.org</ref>


* Once the session is over, end the meeting with the meeting bot command ‘#endmeeting’
Major changes in bodhi 0.9.2
---------------------------------


* At the end of the meeting, the meeting bot will spit out a bunch of links to the minutes. Take these links and post them to the following venues as soon as possible:
* fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)


* Fedora Advisory Board Mailing List (advisory-board AT lists.fedoraproject.org)
* Re-organized the links on the front page, and link to the new Update Feedback Guidelines


* Community support for Fedora users Mailing List (users AT lists.fedoraproject.org)
* The submitter of an update can no longer effect the karma (Till Maas)


* Fedora Announce List Mailing List (announce AT lists.fedoraproject.org)
* Fix duplicate status change email notifications. (Till Maas)


* Development discussions related to Fedora Mailing List (devel AT lists.fedoraproject.org)
* Mention age of updates in testing digest mails (Till Maas)


* Planet Fedora<ref>http://planet.fedoraproject.org</ref> – if your blog is not on Planet Fedora, contact Máirín Duffy (duffy AT fedoraproject.org) to post your message to the Planet for you.
* Support e-mail threading in notification e-mails (Till Maas)


* Helpful tips:
* Add X-Bodhi mail headers (Till Maas)


* Have great IRC and meetbot skills. This will help you out a lot!
* Gracefully handle private bugs (Cole Robinson)
* Don’t be afraid to poke people in the public channel for questions if things get slow. And bring a question or two of your own, just in case things get *really* slow!
* Keep an eye on the clock and the question queue.
* Town halls are held in #fedora-townhall and #fedora-townhall public


That’s it!
* Set the default request for new updates to 'testing' in the web form


Like I said – if you’re interested in any of the above positions – please send a mail to the Fedora Board (advisory-board AT lists.fedoraproject.org) to let them know you are willing and available.
* 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.


Let election season begin! Don't forget to nominate yourself if you are interested<ref>http://fedoraproject.org/wiki/Elections</ref>, and don't forget to vote when voting time rolls around.
* Fixed the input box alignment in the login box (Kalpa Welivitigoda)


Cheers,


-Robyn"
Full list of changes since 0.8.7
--------------------------------


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


====Fedora 15 release name voting information====
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'


[[User:jsmith|Jared Smith]] announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-October/002872.html</ref>:
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


"The time has come to vote for the release name for Fedora 15. The Fedora community has submitted quite a few suggestions for the Fedora 15 release name, and that list has been narrowed down to the final five candidates. Now you can vote on these names and assist in the final selection for the successor of Fedora 14 "Laughlin".
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.


This vote begins 26 October 2010 and runs until 1 November 2010 at 23:59:59 UTC. Other important facts:
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"


* We are using the Range Voting method<ref>http://en.wikipedia.org/wiki/Range_voting</ref>
<references/>


* Ballots may be cast on the Fedora Elections System<ref>https://admin.fedoraproject.org/voting</ref>
====Build F-18 collection packages for all language translators====


* If this is the first time you've used the voting system, you might want to read the Fedora Elections Guide, currently located at<ref>http://pfrields.fedorapeople.org/documents/elections-guide/</ref>
* Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto]<ref>noriko.mizumoto at gmail.com</ref>
* Posted Date: Thu Aug 30 09:17:01 UTC 2012<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-August/000968.html</ref>


* To vote, you must have a valid Fedora Contributors License Agreement (CLA) and be a member of at least one non-CLA group
"Hi Fedora package maintainers


To vote, visit<ref>https://admin.fedoraproject.org/voting/about/relnamef15</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.


Thank you to everyone who helped by contributing names for consideration, and reviewing the names for the final ballot.
Thank you so much.


--
noriko
Jared Smith
Fedora Localization Project"
Fedora Project Leader"


<references/>
<references/>


====2011 Fedora Scholarship open to applications====
====Fedora 18 Alpha to slip by another one week====


Ian Weller announced<ref>http://lists.fedoraproject.org/pipermail/announce/2010-October/002871.html</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>


"The Fedora Scholarship program recognizes one high school senior per year for contributions to the Fedora Project and free software/content in general. The scholarship is a $2,000 USD reward per year over each of the four years the recipient is in college, which is funded by Red Hat's Community Architecture team, as well as travel and lodging to the nearest FUDCon for each year of the scholarship.
"Today at Go/No-Go meeting it was decided to slip Fedora 18
Alpha release by one week due to remaining open blocker bugs<ref>http://qa.fedoraproject.org/blockerbugs/current</ref> and incomplete test matrices for Alpha <ref>https://fedoraproject.org/wiki/Test_Results:Current_Base_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test</ref><ref>http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test</ref>. Meeting's
full log is at <ref>http://bit.ly/PC16PF</ref>.  


If you are a student who will be entering college in Fall 2011, you are eligible to apply! The application is extremely simple, and is described in length<ref> https://fedoraproject.org/wiki/Scholarship</ref>. Please be sure to read the terms and conditions before applying.
As a result, ALL MAJOR MILESTONES, and their dependent tasks,
will be pushed out by one week.


The application deadline for this scholarship is February 25, 2011. (Remember -- don't procrastinate just because the deadline is in four months!)
The next Go/No-Go meeting is on Thursday Sep 06, same place
but different time (19:00 UTC, 3 PM EDT, 21:00 CEST
#fedora-meeting).


--
If you have an accepted blocker bug, please try to fix it
Ian Weller <ian at ianweller.org>"
as soon as possible to help us with Fedora 18 Alpha release!"


<references/>
<references/>
===Fedora Development News===
The fedora development news list is intended to be a low traffic announce-only list for Fedora development.<ref>https://admin.fedoraproject.org/mailman/listinfo/devel-announce</ref>
* '''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
<references/>
====Fedora 14 Beta Declared GOLD====
John Poelstra <ref>poelstra at redhat.com</ref> on Wed Sep 22 22:31:39 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000690.html</ref>,
"'''At the Fedora 14 Beta Go/No-Go meeting today, the Fedora 14 Beta was declared GOLD and ready for release on September 28, 2010'''.
Thank you to everyone who made this on-time release possible!
'''#fedora-meeting: Fedora 14 Beta Go/No-Go Meeting Minutes and Logs'''
Meeting started by poelcat at 21:01:35 UTC. The full logs are available at <ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-09-22/fedora-meeting.2010-09-22-21.01.log.html</ref>
.
=====Meeting summary=====
* attendees rbergeron jsmith fenris02 SMParrish stickster jlaska adamw  brunowolff  (poelcat, 21:03:17)
* http://fedoraproject.org/wiki/Engineering_Readiness_Meetings  (poelcat, 21:03:42)
* review of release criteria and open bugs  (poelcat, 21:05:24)
* adamw and jlaska here for qa  (poelcat, 21:07:18)
* SMParrish here for devel/FESCo  (poelcat, 21:07:28)
* dgilmore representing releng  (poelcat, 21:07:38)
* brunowolff is here for Spins SIG  (brunowolff, 21:08:00)
* LINK:  <ref>https://fedoraproject.org/wiki/Test_Results:Fedora_14_Beta_RC3_Install</ref>
    <--- install test matrix  (adamw, 21:08:11)
* LINK:<ref>https://fedoraproject.org/wiki/Test_Results:Fedora_14_Beta_RC3_Desktop</ref>
    <--- desktop test matrix  (adamw, 21:08:25)
* LINK: <ref>https://bugzilla.redhat.com/showdependencytree.cgi?id=611991&hide_resolved=1</ref>
    <--- beta blocker list  (adamw, 21:08:49)
* AGREED: 627789 is not a beta blocker  (adamw, 21:12:54)
* IDEA: create release criteria asserting some level of functionality of livecd-tools  (jlaska, 21:13:03)
* AGREED: move https://bugzilla.redhat.com/show_bug.cgi?id=627789 to f14blocker  (poelcat, 21:15:00)
* LINK:<ref>https://fedoraproject.org/wiki/Test_Results:Fedora_13_Final_RC3_Install</ref>(adamw, 21:19:50)
* AGREED: publishing a documented updates.img with a fix for 635887 is an acceptable workaround, move 635887 to be a final blocker  (adamw,  21:25:48)
* AGREED: 542255 is not a regression, is of minor impact, and the question of non-default-spin bugs blocking releases requires further discussion and clarification, so we will not block the beta for this bug  (adamw, 21:45:26)
* ACTION: there being no unresolved blocking issues or unmet release criteria, Fedora 14 Beta is declared GOLD  (poelcat, 21:55:34)
* open discussion  (poelcat, 21:55:37)
Meeting ended at 21:58:31 UTC.
=====Action Items=====
* there being no unresolved blocking issues or unmet release criteria,Fedora 14 Beta is declared GOLD
=====Action Items, by person=====
* **UNASSIGNED**
* there being no unresolved blocking issues or unmet release criteria, '''Fedora 14 Beta is declared GOLD'''
=====People Present (lines said)=====
* adamw (106)
* poelcat (51)
* jlaska (45)
* dgilmore (27)
* jsmith (22)
* brunowolff (9)
* fenris02 (9)
* maxamillion (8)
* stickster (7)
* bcl (6)
* mjg59 (5)
* SMParrish (4)
* zodbot (4)
* rbergeron (4)
* kalev (3)
* mmcgrath (2)
* skvidal (1)
Generated by `MeetBot`_ 0.1.4"


<references/>


====libedataserverui soname bump in Fedora 14====  
=== Fedora Events ===


Milan Crha <ref>mcrha at redhat.com</ref> on Fri Sep 24 08:57:41 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000691.html</ref>,
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.


"I'm so sorry for a late notice, but there was a soname bump of libedataserverui library from evolution-data-server package in time for 2.31.91 update, but I didn't notice this change, and because this update didn't get it to the testing repo, then I realized just now, when I finished an update to 2.31.92 and pushed it to updates-testing.
====Upcoming Events (September 2012 - November 2012)====
* '''North America (NA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28Sept_2012_-_Nov_2012.29</ref>
* '''Central & South America (LATAM)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29</ref>
* '''Europe, Middle East, and Africa (EMEA)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_2</ref>
* '''India, Asia, Australia (India/APJ)'''<ref>http://fedoraproject.org/wiki/Events#FY13_Q3_.28September_2012_-_November_2012.29_3</ref>


Affected packages seems to be these:
Guideline to write Fedora Press Releases<ref>https://fedoraproject.org/wiki/How_to_write_a_Fedora_press_release</ref>
* almanah
* anjal
* gnome-panel
 
It should be enough to just rebuild these against evolution-data-server-2.31.92, which is still marked for a build system.
 
The update request url is here:<ref>https://admin.fedoraproject.org/updates/evolution-mapi-0.31.92-1.fc14,evolution-exchange-2.31.92-1.fc14,openchange-0.9-8.fc14,evolution-2.31.92-1.fc14,evolution-data-server-2.31.92-1.fc14,gtkhtml3-3.31.92-1.fc14</ref>"
 
<references/>
 
====poppler update to 0.15.0 (0.16 alpha)==== 
 
Marek Kasik <ref>mkasik at redhat.com</ref> on Mon Sep 27 08:07:02 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000692.html</ref>,
 
"I plan to update update poppler in rawhide (Fedora 15) to new development version 0.15 next week (at Monday, October 4th). Changes against 0.14.x are:
 
=====core:=====
* Remove exception support
* Improve creation of Annotations
* Fix failure to parse PDF with damaged internal structure.(Bugs #29189 #3870)
* Add a way to access the raw text of a page
* Speed improvements when reading multiple characters from a given Stream
* Speed improvements in the Splash backend
* Speed improvement in gray color space calculations
* Speed improvement in ICC color space calculations
* Speed improvement when reading some fonts
* Make GBool a bool instead of an int
 
=====glib:=====
* Add GObject introspection support
* Improve creation of Annotations
* Add a way to get the coordinates of each character of a page
* Add a way to get the page label
* Documentation improvements
* Support password protected documents in the demo
* Support for selection in the demo
* Support for adding annotationss in the demo
* Misc improvements in the internals
   
=====qt4:=====
* Add a way to access the raw text of a page
* Recognize "Print" as named action
* Documentation improvements
   
=====build system:=====
* Add option for autogen.sh to skip configure
* Nicer autogen.sh output
* Improvements when build the glib frontend with CMake
   
=====utils:=====
* pdftohtml: Use splash instead of external gs invocation to render the background
* pdftohtml: Let the user specify the resolution of the background. (Bug #29551)
   
=====cpp:=====
* Add a way to access the raw text of a page
 
+ 2 soname bumps in libpoppler.so.* and libpoppler.glib.so.*.
Please check whether your package builds against this new version of poppler correctly if you maintain a package which requires it. The new version has been pushed to git already but not built yet."
 
<references/>
 
====Fedora Updates Policy==== 
 
Kevin Fenzi <ref>kevin at tummy.com</ref> on Tue Sep 28 23:07:43 UTC 2010 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2010-September/000694.html</ref>,
"'''At today's FESCo meeting (2010-09-28) we approved an Updates Policy''':<ref>https://fedoraproject.org/wiki/Updates_Policy</ref>
https://fedoraproject.org/wiki/Updates_Policy
 
This policy is based on the Fedora Board's Stable Updates release vision(see <ref>https://fedoraproject.org/wiki/Stable_release_updates_vision</ref>) and expanded to cover other branches of Fedora. It's a superset of the
existing <ref>https://fedoraproject.org/wiki/Package_update_acceptance_criteria page</ref>.
 
All package maintainers and other interested parties are urged to read and follow the Policy.
 
When in doubt about some portion of the policy, Or when seeking an exception for an update or an adjustment to the policy, please open a discussion on the devel list or with FESCo directly (see <ref>https://fedorahosted.org/fesco/newtplticket</ref> ).
 
I would like to personally thank all the folks that helped work on or provide input to this document. I hope we can improve, clarify and adjust it as we go, leading to a better Fedora for our entire community."


<references/>
<references/>


===Fedora Events===
Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
====Upcoming Events (Sept 2010 - November 2010)====
* North America (NA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sept_2010_-_November_2010.29</ref>
* Central & South America (LATAM) <ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28September_2010_-_November_2010.29</ref>
* Europe, Middle East, and Africa (EMEA)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sep._2010_-_Nov._2010.29</ref>
* India, Asia, Australia (India/APJ)<ref>http://fedoraproject.org/wiki/Events#FY11_Q3_.28Sept_2010_-_November_2010.29_2</ref>
<references/>
====Past Events====
====Past Events====
Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
Archive of Past Fedora Events<ref>http://fedoraproject.org/wiki/FedoraEvents/PastEvents</ref>
Line 393: Line 372:
* [[Event reports]] -- guidelines and suggestions.
* [[Event reports]] -- guidelines and suggestions.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
* [[FedoraEvents/LinuxEvents| LinuxEvents]] -- a collection of calendars of Linux events.
===Fedora Press Releases===
Fedora press releases will be found at the link:
http://fedoraproject.org/wiki/Fedora_press_archive#Fedora_Press_Releases

Latest revision as of 11:18, 31 August 2012

Announcements

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

Contributing Writer: Rashadul Islam

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

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

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

---

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

---

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

---

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

---

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

---

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

---

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

---

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

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

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

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

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

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

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

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

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

To place a subsidy request, please follow these steps:

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

Additionally, a few notes regarding the hotel in Paris:

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

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

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

Fedora Infrastructure announces status.fedoraproject.org

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

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

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

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

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

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

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

Beats are open!

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

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

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

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

Fedora Development News

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

Acceptable Types of Announcements

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

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above

New bodhi release in production

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

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

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

Major changes in bodhi 0.9.2


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


Full list of changes since 0.8.7


Kalpa Welivitigoda (1):

     fixed input box alignment issue in login box #579

Luke Macken (25):

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

conflicts

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

Mathieu Bridon (6):

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

Ralph Bean (19):

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

Till Maas (8):

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial
     model.py: Change karma from Submitter to 0
     Fix notification on automatic status change"

Build F-18 collection packages for all language translators

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

"Hi Fedora package maintainers

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

Thank you so much.

noriko Fedora Localization Project"

Fedora 18 Alpha to slip by another one week

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

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

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

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

  1. fedora-meeting).

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


Fedora Events

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

Upcoming Events (September 2012 - November 2012)

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

Guideline to write Fedora Press Releases[5]

Past Events

Archive of Past Fedora Events[1]

Additional information

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

Fedora Press Releases

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