All open Fedora 11 bugs recently received a comment warning about the
upcoming end of life for Fedora 11. This email serves as correction to
part of that notification.
Due to an error on my part this warning was sent out earlier than it
should have been. The statement "Approximately 30 (thirty) days from
now Fedora will stop maintaining and issuing updates for Fedora 11..."
is incorrect. The end of life (EOL) for Fedora 11 will be June 18,
2010, which is thirty days after the release of Fedora 13, currently
scheduled for May 18, 2010. When Fedora 11 reaches EOL at that time,
bugs open for Fedora 11 will be closed as previously described.
For more information on Fedora's policy for maintenance of our releases,
please refer to:
My apologies for any inconvenience or confusion this error may have caused.
The Fedora IRC Classroom has been quiet of late, but thats about to
change! We have a number of great classes coming up:
Date and Time (UTC) Class topic and Instructor
27 April, 2010 at 19:00 UTC How to make life awesome for journalists - Joe Brockmeier
29 April, 2010 at 01:00 UTC How to test Fedora Updates - Kevin Fenzi
30 April, 2010 at 12:30 UTC (6:00 PM IST) A Short Tutorial On i18n Through gettext - Naveen Kumar
03 May, 2010 at 13:30 UTC (7:00 PM IST) Introductory workshop on GNU Autotools - Siddhesh Poyarekar
10 May, 2010 at 01:00 UTC Learn about exciting Fedora 13 Features - Kevin Fenzi
See the classroom page ( https://fedoraproject.org/wiki/Classroom ) for
more details and information on how to attend classes on IRC, or sign
up to teach one!
Hope to see everyone there.
-----BEGIN PGP SIGNED MESSAGE-----
Fedora 13 is just around the corner, so it's time for us to kick off
the naming process for the next Fedora release. You can make a
suggestion for the name for Fedora 14 here:
Remember that there are *instructions and guidelines* at the page that
you must follow if you want your name to be considered. For instance,
there must be an "is-a" link between the name Constantine and the name
you suggest. That link must be different than previous links for
Fedora release names. Please be sure to conduct the required searches
for brand and trademark names that might cause us problems.
Read the full guidelines at that page, where you can also find full
schedule details for the release naming process. Suggestions will be
collected until Tuesday, April 27, and voting will happen starting
Tuesday, May 4!
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
-----END PGP SIGNATURE-----
Hello Fedora! (Is this thing on?)
Sorry for the very wide net, but we wanted to make sure as many members
of our community could see this as possible.
For some time now, Fedora has been working with Red Hat Legal to come up
with a replacement for the Fedora Individual Contributor License
Agreement (aka, the Fedora ICLA). As a result, the Fedora Project
Contributor Agreement (FPCA) has been approved by Red Hat Legal, and is
now being presented to the Fedora Community for comments and discussion.
The full text of the FPCA, along with a FAQ, can be found here:
Please, take a moment and read the FPCA and the FAQ. It is not a long,
or overly complicated document, as legal documents go, but it is
important that all Fedora Contributors read it over and make sure they
understand it and like it (or can at least agree to it).
Fedora Legal wishes to give the Fedora community a window of time for
discussion and review of the FPCA. This window is open until May 18,
2010 (2010-05-18). After that point, either a revised FPCA will be
released for review, or we will begin the process of phasing in the FPCA
and phasing out the Fedora ICLA.
Thanks in advance,
Tom "spot" Callaway, Fedora Legal
P.S. Fedora Legal would like to give a huge thank you to the people
involved behind the scenes to make the FPCA possible. The primary author
was Richard Fontana, with feedback from Tom Callaway, Pamela Chestek,
Paul Frields, and Robert Tiller. Feel free to give them gifts (for
example, drinks or tasty snacks) as thank yous, although, this is not a
requirement (legal or otherwise). ;)
We have pushed back the first part of the Summer Coding 2010 schedule.
There wasn't enough time to find sponsors. Now there is more time for
mentors and students to generate ideas and write up good proposals,
while people like you and me look for more sponsors.
Highlights - note all due items now have an entire month more:
* Ideas page closes 13 May
* Proposals are due 20 May
* Sponsors must pledge by 21 May
Projects are set to start on 01 June, which is only a week after the
original start date. Our goal is to be as flexible as we can be after
that, contact us if you have any questions about how to make the
schedule work for you:
Here is the updated schedule, reprinted below:
For more details:
- Summer Coding SIG
 Full schedule
7 April - Students can begin submitting applications
Whole month - students, mentors, and sub-projects get to
know each other
13 May - Mentors need to finish idea pages
20 May - Students applications + proposals need to be in
21 May - Sponsors must pledge funding by this point
24 May - Organizers finalize how many applications will be
27 May - Mentors + admins finalize rank-ordered list
28 May - Students informed yes/no about application
Whole month - code, interact
01 June - Project begins (depending on proposal)
NOTE: Proposals may have a modified schedule included.
5 July - Midterm evaluations period begins
12 July - Midterm evaluations due
09 August - Project coding completes
16 August - Students final report, code snapshot, and
20 August - Mentor evaluations due for students
23 August - Final evaluations due back to students
25 August - Mentor, sub-project evaluations due
01 September - Sponsors receive report from organizers
06 September - Sponsors release and deliver funds (proposed
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture