From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
Line 8: Line 8:
<references/>
<references/>


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


====Fedora 18 release name by [[User:Rbergero|Robyn Bergeron]] published on Mon Apr 30 13:51:00 UTC 2012 ====
====[Guidelines Change] Changes to the Packaging Guidelines====  


News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-April/003067.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>


"Thank you to everyone who participated in voting for the Fedora 18
"A new section has been added to the SysV Initscripts section, discussing
release name. The name for Fedora 18, the follow-up to Beefy Miracle,
the proper use of subsys locking. Even though Fedora packages should no
is:
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>


'''Spherical Cow'''
---


Voting period:  Friday 2012-04-20 00:00:00 to Friday 2012-04-27 00:00:00
The review guidelines now reflect the use of sha256sum (instead of
Number of valid ballots cast: 429
md5sum) to confirm upstream source integrity.
<ref>https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Things_To_Check_On_Review</ref>


Using the range voting method, each candidate could attain a maximum
---
of (429*8) = 3,432


Results:
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>


Votes :: Name
---
-------------------------------
** 1359 :: Spherical Cow
** 1087 :: Halva
** 1072 :: Chamoy
** 1035 :: Pamukkale
** 964 :: Tandoori Chicken
** 930 :: Frankfurter
** 821 :: Pop Soda
** 536 :: Ketchy Ketchup"


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


---


====Formally announcing FUDCon: Paris and FUDCon: Lawrence by [[User:Rbergero|Robyn Bergeron]] published on Tue May 8 14:06:41 UTC 2012==== 
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>


News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003068.html</ref>,
---


"As many of you know, FUDCon is the abbreviation for Fedora Users and
The RHEL conditionalization has been removed from the Python3 example
Developers Conference, an event we typically hold 4 times per year in
spec file, as it is no longer valid.
various regions of the world. These events are proposed and arranged
<ref>https://fedoraproject.org/wiki/Packaging:Python#Example_spec_file</ref>
largely by Fedora contributors, and are designed to be events where
contributors and those new to Fedora can learn, share, hack, and
participate in various aspects of the Fedora Project.


It is with great pleasure that I am formally announcing two upcoming
---
FUDCons:


'''FUDCon for the EMEA region in 2012 will be held in Paris, France,
These guidelines (and changes) were approved by the Fedora Packaging
October 13-15, 2012 <ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012</ref>'''.  This particular event will be held over those days in two locations; the first day, Saturday the 13th, will be held at the Eurosites Georges V facility, in conjunction with the Open World Forum (OWF) <ref>http://www.openworldforum.org/</ref>, and on the 14th and 15th at Universcience. I'd like to
Committee (FPC).
thank Kevin Raymond and the rest of the FUDCon Paris team for putting
together this bid, and for working with OWF to procure space during that
event for the first day of FUDCon; I think that this will be an
interesting opportunity to showcase Fedora to a captive audience that is
passionate about open source.  I would also like to thank the other
teams who submitted bids for the EMEA region.


'''The next FUDCon for North America will be held in Lawrence, Kansas, on
'''Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart
the 18th through 20th of January, 2013 <ref>http://fedoraproject.org/wiki/FUDCon:Lawrence_2013</ref>, at the University of Kansas'''.  While you can peruse the bidding page <ref>http://fedoraproject.org/wiki/FUDCon:Bid_for_Lawrence_2013#About_Lawrence</ref> for details, I'd like
Poettering, Michael Scherer, Dave Sullivan, and all of the members of
to note that Lawrence is home to many awesome things: It is the birth
the FPC, for assisting in drafting, refining, and passing these guidelines.'''
place of the Django Project, was pinpointed as the "center of the earth"
in Google Earth, was the home of William Burroughs, is the location of
the awesomely-named Free State Brewing Company, has been named a top-ten
college town, and most importantly, is the collegiate location of our
resident Wiki Czar and Doer of Stuff, Ian Weller, who, as you may have
guessed, was also the author of this FUDCon bid. A big thank-you! to Ian
for volunteering to put this together.


FUDCon planning continues, in grand tradition, to be open to everyone
As a reminder: The Fedora Packaging Guidelines are living documents! If
for participation; if you are interested in contributing to the
you find something missing, incorrect, or in need of revision, you can
discussion or lending a helping hand, I encourage you to subscribe to
suggest a draft change. The procedure for this is documented here:
the FUDCon planning mailing list <ref>http://lists.fedoraproject.org/mailman/listinfo/fudcon-planning</ref>.
<ref>https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure</ref>"


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


<references/>
<references/>


====Appointment to the Fedora Board, and Elections Reminder by [[User:Rbergero|Robyn Bergeron]] published on Tue May 8 17:29:41 UTC 2012====
====FUDCon Paris Updates: Subsidy requests opening, hotel reminders====  


News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003069.html</ref>,
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>


"I'm pleased to announce the appointment of Garrett Holmstrom to the
"Greetings! (...or perhaps I should say.... bonjour!)
Fedora Board. In this election cycle, three Board seats are open for
election, and two Board appointee seats are open; the first appointee,
Garrett, is being appointed prior to nominations opening, and the second
will be appointed after elections are completed.


Garrett (aka: gholms) has been involved in the Cloud SIG since the
I'd like to share a few reminders and announcements regarding the  
"early days" (early 2010, to be more precise), as the maintainer of the  
upcoming '''FUDCon in Paris, France, on October 13-15, 2012'''.
euca2ools package.  As the group has progressed, he's taken on a number
of tasks, doled out much advice and opinion, and has shown himself to be
an excellent leader and communicator.  He's also a regular in the #fedora-devel channel, willing to help out and answer questions as he
can. I'm delighted that he has agreed to serve on the Board; I believe
that, as a community, we should constantly strive to nurture and grow
new leadership, and I think that Garrett's communication skills and
positive attitude will be a fantastic asset to the Board as Fedora
continues to evolve.


Garrett will be taking seat A3, previously held by Rudi Landmann. (And a  
If you are planning to attend FUDCon and need a travel subsidy to do so,
big thank you to Rudi for his contributions as a Fedora Board member --
the ticketing system is now open for those requests.  Requests will be  
your time and efforts are greatly valued!)
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.


I'd also like to remind everyone of the ongoing elections process;
To place a subsidy request, please follow these steps:
today, May 8th, is the last day to submit questions to the elections
questionnaire.  Beginning tomorrow, May 9th, nominations for the Board,
FESCo, and FAmSCo will be open, closing on May 15th.


Additional information about Elections can be seen here:
1: Pre-register at
<ref>http://fedoraproject.org/wiki/Elections</ref>
<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>


A complete history of Board Members is available here:
Additionally, a few notes regarding the hotel in Paris:
<ref>http://fedoraproject.org/wiki/Board/History</ref>


Cheers,"
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:
<ref>http://fedoraproject.org/wiki/FUDCon:Paris_2012#Lodging_.2F_Hotel</ref>"
<references/>
<references/>


====The Future of release names by [[User:Toshio|Toshio Kuratomi]] published on Wed May 9 08:39:18 UTC 2012 ====  
====Fedora Infrastructure announces status.fedoraproject.org====  


News on Announcement Desk<ref>http://lists.fedoraproject.org/pipermail/announce/2012-May/003070.html</ref>,
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>


"At the last Board Meeting, the Board looked at the poll results asking
"I'm happy to announce the general availability of our
whether people felt like continuing to name releases. The results seemed
status.fedoraproject.org site.  
to show that many people do like having a name associated with Fedora
releases. However, the discussion before and after has shown there is
a desire to improve upon the current method of selecting the names.


The Board decided that it would be worthwhile to come up with a new
This site provides an easy way for Fedora contributors and users to
procedure for selecting the name for the Fedora 19 release and beyond to
check on the status of services provided by Fedora Infrastructure.
attempt to solve some of the issues that have been brought up. The Board
is looking for volunteers who would like to do two things:


(1) Answer the following questions:
The site auto reloads every minute, and also provides a rss feed at
<ref>http://status.fedoraproject.org/changes.rss of any changes</ref>.


** What benefits does the Project get from the current release naming process?
If you run into a problem or issue that is not reflected at
** What changes do people want to see in a revised process?
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.


(2) Come up with at least one proposal and analyze it according to the answers to the previous questions.
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'''.  


If anyone is interested in coming to a weekly meeting to work on this,
This application is hosted at the link<ref>https://openshift.redhat.com</ref> to avoid any
please feel free to contact me. If anyone would like to champion this,
issues with outages in our infrastructure affecting status reporting. "
please contact me ASAP so I know whether there is someone else who's going
to champion this or if I need to lead the effort.
 
I've put up a wiki page that tries to summarize the answers to the first two
questions that I've seen circulated on the advisory-board mailing list and a
link to the only proposal I currently know of (mizmo's proposal to use
a single theme for all of the new Fedora releases)."


<references/>
<references/>


=== Fedora Development News ===
=== Fedora Development News ===
Line 177: Line 179:
<references/>
<references/>


====Fedora 17 Change Freeze by [[User:Ausil|Dennis Gilmore]] published on Tue May 1 18:30:02 UTC 2012====
Fedora development news desk<ref>http://lists.fedoraproject.org/pipermail/devel-announce/2012-May/000925.html</ref>,
"the fedora 17 schedule<ref>http://fedoraproject.org/wiki/Releases/17/Schedule</ref> lists the final
change freeze as 2012-05-07 this means that you need to make sure that
any changes you want in Fedora 17 final must be submited for stable in
Bodhi before 2012-05-07 there will be a small window on monday where
you can get your build in still but it is not assured. after this time
only blocker bugs will be accepted to be pushed for stable.  please
work on testing and ensuring anything you want in final has the
appropriate karma. '''If you have questions please drop by #fedora-releng
on freenode'''"


<references/>
<references/>

Revision as of 10:13, 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: Cite error: Closing </ref> missing for <ref> tag to avoid any issues with outages in our infrastructure affecting status reporting. "

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



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.