From Fedora Project Wiki

< FWN‎ | Beats

(Upcoming Events (December 2011 - May 2012))
(Fedora Development News)
Line 128: Line 128:
 
<references/>
 
<references/>
  
====Fedora 17 for Power Alpha Announcement====   
+
====exiv2-0.23 coming soon====   
David Aquilina<ref>dwa at redhat.com</ref> on Tue Apr 10 19:51:42 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000913.html</ref>,
 
  
"Time flies like the wind...
+
[[User:Rdieter|Rex Dieter]]<ref>rdieter at math.unl.edu</ref> on Wed Apr 25 13:07:31 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000921.html</ref>,
  
As it's already time again for another Fedora release on Power, this
+
"I plan on importing exiv2-0.23 into rawhide soon'ish.  It includes an
time for Fedora 17 Alpha.
+
ABI bump, so dependent packages will require rebuilding, including:
 +
* calligra
 +
* darktable
 +
* entangle
 +
* geeqie
 +
* gipfel
 +
* gnome-color-manager
 +
* gnome-commander
 +
* gpscorrelate
 +
* gthumb
 +
* gwenview
 +
* hugin
 +
* immix
 +
* kde-runtime
 +
* krename
 +
* libextractor
 +
* libgexiv2
 +
* libkexiv2
 +
* luminance-hdr
 +
* merkaartor
 +
* oyranos
 +
* pyexiv2
 +
* rawstudio
 +
* strigi
 +
* ufraw
  
We've hit a couple of bumps along the road to the Alpha, but at long
+
I'll take care of kicking off a round of rebuilds for these."
last we're finally at a state where we're ready to release it to the
 
public.
 
 
 
Due to lack of developer time and hardware, Apple hardware support is at
 
this point completely untested. Especially with the switch to grub2 we
 
rely on community feedback and participation to make this work for this
 
release. So if you have the hardware and want it to work, patches
 
welcome! :)
 
 
 
The bits are available from your closest mirror:
 
 
 
<ref>https://mirrors.fedoraproject.org/publiclist/Fedora/17-Alpha/ppc64/</ref>
 
 
 
More details about this Alpha release can be found here:
 
 
 
<ref>https://fedoraproject.org/wiki/Fedora_17_Alpha_PPC_release_notes</ref>
 
 
 
One of our focuses in the lead up to the beta of Fedora 17 for Power
 
will be addressing architecture-specific packaging issues in as many
 
packages as possible. If you own a package in Fedora which has
 
ExclusiveArch or ExcludeArch set, please take a moment to verify that
 
the architectures you've excluded or are exclusive to are still correct
 
and sane.
 
 
 
I want to thank everyone involved in making this happen once more. Many
 
Fedora packagers and contributors have again stepped up and helped fix
 
issues that only appeared on Power hardware. Moreover the whole Fedora
 
Secondary Arch team has been doing a fantastic job to get us to where we
 
are now, especially considering that we had a complete switch of
 
builders and hub hardware, mass rebuild and a hub failure along the way!
 
 
 
As usual, you can reach the whole team on the #fedora-ppc IRC channel on
 
FreeNode and via our email list:
 
 
 
<ref>https://admin.fedoraproject.org/mailman/listinfo/ppc</ref>
 
 
 
And we have our Secondary Arch wiki with (decently) updated information:
 
 
 
<ref>http://fedoraproject.org/wiki/Architectures/PowerPC</ref>
 
 
 
For Phil, Karsten, and the entire Fedora for Power team,
 
Thanks & regards,
 
David"
 
  
 
<references/>
 
<references/>
  
====Fedora 17 Beta Go/No-Go Meeting, Round 3, Wednesday, April 11, @17:00 Eastern====   
+
====Announcing easyfix====   
Fedora New Project Leader, [[User:Rbergero|Robyn Bergeron]]<ref>rbergero at redhat.com</ref> on Wed Apr 11 03:23:31 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000914.html</ref>,
 
 
 
"Please join us on irc.freenode.net in #fedora-meeting-1 for this
 
important meeting. This will be Round 3 of this meeting for the Beta
 
release of F17.
 
 
 
Wednesday, April 11, 2012 @21:00 UTC (17:00 EDT/14:00 PDT)
 
 
 
"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
+
[[User:Pingou|Pierre-Yves Chibon]]<ref>pingou at pingoured.fr</ref> on Thu Apr 26 09:12:28 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000922.html</ref>
the QA Team."
 
 
 
For more details about this meeting see:
 
<ref>https://fedoraproject.org/wiki/Go_No_Go_Meeting</ref>
 
 
 
In the meantime, keep an eye on the Fedora 17 Beta Blocker list:
 
<ref>http://fedoraproject.org/wiki/Current_Release_Blockers</ref>
 
 
 
Ongoing Beta RC test results can be seen here:
 
<ref>https://fedoraproject.org/wiki/Category:Fedora_17_Beta_RC_Test_Results</ref>
 
 
 
See you there, Wednesday, in #fedora-meeting-1.
 
 
 
-Robyn, fingers and toes crossed thoroughly"
 
 
 
<references/>
 
  
====Fedora 17 Beta is declared GOLD==== 
+
"Good news everyone (© Farnsworth),
[[User:Rbergero|Robyn Bergeron]] - Fedora Project Leader<ref>rbergero at redhat.com</ref> on Thu Apr 12 05:11:27 UTC 2012 announced<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-April/000915.html</ref>,
 
  
"At today's F17 Beta Go/No-Go meeting, the Fedora 17 Beta release was
+
The easyfix project is now live:
declared gold. F17 Beta will be released Tuesday, April 17, 2012.
+
<ref>http://fedoraproject.org/easyfix/</ref>
  
Thanks to everyone involved for pulling this one together and
 
participating in the meetings, things came together well this week. :)
 
  
For those interested in the details:
+
As a new-comers, you will be able to find a list of projects which have
 +
bugs/requests considered to be easy to work on (ie: you do not need a
 +
deep understanding of the project to fix/implement it).
 +
The projects are divers and the tickets broad : from fixing typo, add a
 +
link in a template (dev) to add a node to nagios monitoring (sysadmin)
 +
via making the fedoraproject.org page w3c valid (websites).
 +
So everyone should be able to find for his taste.
  
Minutes:
 
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.html</ref>
 
Logs:
 
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html</ref>
 
  
Full minutes follow below.
+
As upstream, you will have a way to attract new-comers to your project
 +
and fixing easier tasks while you focus on the harder/more complex
 +
one ;-)
  
  
=====Fedora-meeting-1: F17 Beta go no go meeting=====
+
Easyfix gathers the tickets from fedorahosted and bugzilla.
Meeting started by rbergeron at 21:00:32 UTC. The full logs are
+
If your project hosted on fedorahosted.org and you would like to have it
available at
+
included, the instruction are on the wiki:
<ref>http://meetbot.fedoraproject.org/fedora-meeting-1/2012-04-11/f17_beta_go_no_go_meeting.2012-04-11-21.00.log.html</ref>"
+
<ref>https://fedoraproject.org/wiki/Easyfix</ref>
 +
If you have bugzilla ticket which you consider easy to fix (remember,
 +
easy for a new-comer != easy for you!), feel free to add the 'EasyFix'
 +
keyword to the bugzilla ticket.
 +
Hope this helps..."
  
 
<references/>
 
<references/>

Revision as of 12:01, 29 April 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

New FAmSCo election guidelines

Christoph Wickert[1] on Thu Apr 26 11:19:10 UTC 2012 announced[2],

"after months of - sometimes controversial - discussion I am am happy to announce the new FAmSCo election guidelines [3]. For those of you, who did not follow the discussion, here is a brief summary of the three most important changes:

More continuity

Instead of electing all seats once a year, we follow the example of the Fedora Board and FESCo and elect half of the committee every 6 months or with every release of Fedora. FAmSCo will not change over sudden and new members can easily catch up with their new duties by learning from others.

Easier filling of vacant seats

Every committee is in danger of members becoming inactive. This can happen to all of us for various reasons such as our dayjobs or personal problems. Under the old guidelines [4], we had to wait until only 3 members left - even with 2 left the committee is hardly operational - and then call a supplementary election - which never happened even though we had only 4 active members. Now we are filling vacant seat when necessary, either with runner-up candidates from the previous elections or by appointing new members.

Wider electorate

The ambassadors represent the whole Fedora Project, this is why now not only ambassadors are eligible to vote for FAmSCo, but everybody who has signed the Contributors License Agreement and is member of (at least) one other group in the Fedora Account System (FAS) is allowed to vote. This will not only strengthen FAmSCo's position but also help candidates who are active in other groups of the Fedora project.

Last but not least the guidelines have been massively cleaned up.

We think that the new guidelines are a big improvement and want them to come into effect as soon as possible. Therefor we will have a special election for Fedora 18 (the next regular elections were scheduled for F19). All 7 seats in FAmSCo are open for election. In order to make the transition to the new alternating terms, the top 4 vote-getters will serve 2 Fedora releases, the bottom 3 will have to run for re-election after one release.

More about the upcoming ambassadors elections to come later this week as part of the general Fedora 18 elections announcement. Please help us getting a better, stronger and more active FAmSCo by casting your votes.

If you have feedback or questions, please don't hesitate to ask. We are looking for your input on the Fedora ambassadors mailing list[5]."

Fedora Elections: General information, and questionnaire opening.

Robyn Bergeron-Fedora Project Leader[1] on Fri Apr 27 11:52:50 UTC 2012 announced[2],

"It is once again time for election season to begin. As noted in the elections schedule[3], the elections questionnaire is now open to populate with questions for candidates, and will close on May 8th. The elections nomination period will begin AFTER the questionnaire period has closed.

You may add your burning questions for candidates to answer here: http://fedoraproject.org/wiki/F18_elections_questionnaire[4]


The following seats are available in this election:

  • Fedora Project Board: 3 seats
  • FESCo (Fedora Engineering Steering Committee): 5 seats
  • FAmSCo (Fedora Ambassadors Steering Committee): 7 seats

Please take note of the following changes for this election:

  • All questions for the questionnaire must be submitted by May 8th,

prior to the beginning of nominations. As seen in the schedule above, the nomination period does not start until May 9th.

  • As noted on announce-list[5], FAmSCo is electing all 7 seats this

cycle, with the goal of having staggered elections similar to the Board and FESCo. Additionally, voting eligibility has been widened to allow anyone who has signed the FPCA AND is a member of at least one additional non-FPCA/CLA group. (In other words: No longer just ambassadors, but those part of other teams as well.)

Full election information may be seen here: http://fedoraproject.org/wiki/Elections[6]

Participating in these bodies are one of many ways to contribute to Fedora; I encourage you to consider running, or to urge those you believe are excellent candidates to run. Additionally, your contributions are welcomed in helping to keep the elections running smoothly; volunteers are needed to help collect questionnaire answers from candidates, as well as for scheduling and moderating town halls. If you are interested in helping with those efforts, please contact John Rose[7].

And a big thank you! to John for coordinating the elections thus far, your efforts are very much appreciated."

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

exiv2-0.23 coming soon

Rex Dieter[1] on Wed Apr 25 13:07:31 UTC 2012 announced[2],

"I plan on importing exiv2-0.23 into rawhide soon'ish. It includes an ABI bump, so dependent packages will require rebuilding, including:

  • calligra
  • darktable
  • entangle
  • geeqie
  • gipfel
  • gnome-color-manager
  • gnome-commander
  • gpscorrelate
  • gthumb
  • gwenview
  • hugin
  • immix
  • kde-runtime
  • krename
  • libextractor
  • libgexiv2
  • libkexiv2
  • luminance-hdr
  • merkaartor
  • oyranos
  • pyexiv2
  • rawstudio
  • strigi
  • ufraw

I'll take care of kicking off a round of rebuilds for these."

Announcing easyfix

Pierre-Yves Chibon[1] on Thu Apr 26 09:12:28 UTC 2012 announced[2]

"Good news everyone (© Farnsworth),

The easyfix project is now live: [3]


As a new-comers, you will be able to find a list of projects which have bugs/requests considered to be easy to work on (ie: you do not need a deep understanding of the project to fix/implement it). The projects are divers and the tickets broad : from fixing typo, add a link in a template (dev) to add a node to nagios monitoring (sysadmin) via making the fedoraproject.org page w3c valid (websites). So everyone should be able to find for his taste.


As upstream, you will have a way to attract new-comers to your project and fixing easier tasks while you focus on the harder/more complex one ;-)


Easyfix gathers the tickets from fedorahosted and bugzilla. If your project hosted on fedorahosted.org and you would like to have it included, the instruction are on the wiki: [4] If you have bugzilla ticket which you consider easy to fix (remember, easy for a new-comer != easy for you!), feel free to add the 'EasyFix' keyword to the bugzilla ticket. Hope this helps..."

Fedora Events

The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (March 2012 - May 2012)

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

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.